Well, so you came to this site and thought to yourself, “what is this all about?” or maybe you didn’t. Either way, let me clear things up regarding what this site is and what it isn’t. Or at least what I want it to be. Bored already? Then check out the interesting stuff at the projects and blog pages. Not yet bored? Then on you may read.

warning
If you want to see some substantial content, Nim code or library documentation, this page might bore you. Really, take a look at my projects and blog instead. If you want to know about the dude who set up this page with the new year's resolution of blogging about his work, instead of being productive and writing some code or working in the lab, this is also the wrong page to be looking at. Take a look at my bio instead. Still want to read this? Fine. Go on then ...

what is this site?

An all-round blog on what I do, also a way for me to better organize my project documentation. A new year’s resolution and a frame for my upcoming thesis code-dump. After that, it’s my somewhat rushed and shabby semi-official presence on the internet and also something of a personal log to store some weird programming ideas in the shape of blogposts so they are not forgotten. Beyond that, it is a way for me to motivate myself to keep working on projects outside of my work and education, its current emptiness being a reminder for myself to open up as much of my work and thesis code as possible.

That being said, it is a work in progress, site and projects together. I hope I will find as much time as possible to bring about a librarification of my thesis code dump and other things lying around on my hard drive as well as the time to actually blog about stuff. That being said, I know this is a hard thing to ask of the internet, but please do not judge me too harshly, there will be more content and projects as time go on.

what’s up with the name?

So, what’s up with all this “compiler internal error” stuff? Well, I work on stuff that involves embedded domain specific languages. This means I have to do a lot of code generation, implementing small-ish compiler-like programs and sometimes wrestling with the host language’s compiler. So one of the things I see on a day to day basis are internal compiler errors, and those messages à la ‘internal error: …’ and ‘compiler error …’ somehow stuck in my head. This being the case, I decided those would sum up the things I do pretty well and decided to name my blog after those.