Jekyll
After much, much deliberation and thinking I’ve decided to go with Jekyll to host this blog. My initial idea was to write my own Blog app using either Django or Ruby on Rails and host it on Google App Engine with Cloud SQL for the database. But if you really think about it, that’s a lot of work. None of it is particularly difficult, but the amount of time, energy and resources put into doing a thing so simple as to create a Blog on your website is just not worth it, in my opinion.
True, it would have been cool to write on a Blog app that was created by me. Think of the customization I could do, it would give me insane control over everything. But the very idea of doing all this just wasn’t exciting to me. Would I learn something new? Yes, I guess. The nitty gritties of creating s3 or Cloud Storage buckets for handling statics or maybe the small details of using Django Google OAuth, etc. I guess. But would that really be worth it? It’s not like I’m a beginner programmer who has vast amounts to learn from creating a CRUD application! Plus I kinda sorta do these things at work already.
Using Jekyll got me to write the first post, with auto generated SEO and Ruby like tags and all. What more could I want? A comment section maybe? I guess I could maybe use Disqus or something along those lines.
a3y3.dev
The .dev
domain should probably tell you that the blog will focus mostly on software development related posts. It’s uncountable how many times a privately hosted blog has helped me solve a challenge, and apart from giving back to the developer community it also helps me keep track of and better understand how I solved my own challenges.
As for what a3y3 is, well…you don’t really want to know (but if you really do, feel free to send me an email!)
Also, to end this post - this is how code blocks look like. Pretty happy with the result!