One of the questions I am asked most often when it comes to programming languages is something that boils down to “should I use X over Y to achieve programming nirvana”. If you believe language evangelists, you would think so. You can make lots of good points to use X over Y or X in general. And maybe even the downsides are mentioned at some point to make it look like an not so opinionated comparison. The question remains - when should you pick which language for your next project?
I receive a few questions via email or Twitter over and over again - looks like people take my footer seriously. Stephanie advocates helping newbies in the industry or who want to join by offering mentoring, which is something I fully support. As a lazy engineer I thought writing answers to the most common questions down saves time in the long run but also helps transfer knowledge to people who do not directly want to ask for mentoring.
I think by now it is not a secret anymore that I am a strong advocate of static site generators. Especially combined with some CDN making all your security and scalability concerns go away. When asked which one I recommend I usually throw out the two most used ones, Jekyll and Hugo and also sneak in my own, drupan, with the disclaimer that it is opinionated, but still proved to work quite well for different projects. Last year I did not really blog much, but I wrote a few posts. I did not really work that much on drupan, but there are new commits and a 2.4 release pending. What happened?
For the first 4 months this year I was in a constant crunch mode. At FlightCar we usually tried to avoid this, but we had to ship a redesign of the website, a redesign of the iOS app and finally release a customer app on Android. As for most other seasoned developers this is not the first time I experienced such a time and it will likely not be the last. Over the years I developed quite a few strategies to handle crunch time (and stay sane and productive at the same time) I want to share with you today.
So there is this thing were @revenant333 and I watch the Apple Keynote and after the keynote is over we send each other a quick shopping list. When the Apple Watch was released the reactions were quite different - he had one on his list, I did not see the point in it. I like mechanical watches and I did not really see the point in having another display telling me what my phone already shows. My take on the Apple Watch was pretty straight forward - "buy one if you need it for work". Now I got an Apple Watch and I have to admit I was a bit wrong about the usefulness of it.
For more posts visit the archive.