The Tales of a Blog

About a year ago I had heard enough ATP episodes to convince myself I should become a full-time programmer - and become a programmer I did. Specifically I was hired as a web developer for a consulting company. Thus, as a web developer does, I started looking at my blog and considering it would be a sign of weakness if I didn't code it myself.

This blog started its life as a site, because that was all I knew at the time. Eventually I started to listen to podcasts a little bit more regularly, which caused the move of all my sites from to Squarespace (as expected). However, once I became a professional developer, I couldn't bear to spend more time writing more blog articles than coding the actual blog. here it is: the all-new Controlled Flame blog. Aside from the fairy-tale story (yet not so distant from reality) I wrote above, the move to writing my own blog engine was done also due to necessity. Not only I am no longer bound to pick a style/page structure out of a list1, but I also have a home where to host websites for small projects. It can become quite expensive to pay for yet another subscription in a SaaS platform; now I can just create a new page and point a domain to it2 (provided I figure out the correct DNS settings). Also, to reiterate a point I've made earlier, given that I'm now deep into software development, I will also have a lot of fun doing so!

For the other tech enthusiasts: this website is now powered by Django. This may sound as overkill for a blogging engine - considering that this is problem that many people wisely solved by just creating a static website served by a CDN. Indeed this may have been my answer if I wanted to just stick with the blog. However I didn't want to restrict myself to a static or blog-oriented solution. Instead I wanted to have the freedom to easily implement such complex actions as providing translations for part of the application. Using Django makes it very easy to solve many problems by rapidly coding some lines of Python, or harnessing the power of the community and install a third-party Django app.

In order to serve the site, I have deployed it in Heroku. Although at work I do deploy Django apps in self-managed servers, sys admin tasks always tend to bring pains which I don't want to deal with for now. As for DNS (and speaking of podcast sponsors), I'm keeping all my domains in Hover - why wouldn't I, they're great!

  1. Only to my somewhat weak ability/willingness to write CSS... 

  2. Take a look, as an example, to the records section of this site. 

< older newer >