/blog

This article is part of a larger series that will lay out the truth behind technology migration and decoupling projects. I’ve taken part in a couple of BIG REWRITE™️ and DECOUPLING™️ and SCALABILITY™️ projects in the past 3 years, so I decided to share the whole truth behind why many such projects fail. I hope this article and the other five sitting in the editing pipeline will help you spot bad trends and do course correction early on.

I published a similar article in 2015. Back then, I was using GTD, Evernote and a lot of tools that have since disappeared from my stack. This is not an update to that article, it is a competitor. I will update it in the days to come as it currently serves only as a placeholder. Stay tuned…

For some time I’ve been thinking of ways to better organise my article ideas. I want to get my content out there, to you, as fast and as often as possible. I usually keep my ideas in an application such as Apple Notes or Google Keep. I’ve been going back and forth between the two for the past 2 years, and they’re both great tools. The problem is that many ideas die at the idea stage.

Whether you’re a developer, designer or any type of professional in the tech industry, there’s one disease we all fear: change. Technologies, tools, languages, techniques … all of them change literally overnight, sometimes leaving behind disappointed, frustrated people. In this article I plan on describing the actions I take when dealing with the ever changing tech world. What?! It’s already outdated? Technology changes, you can’t keep up, deal with it! The end?

So today I didn’t feel like ranting on anything so I thought I’d actually give people some useful stuff. This article is about the unsung heroes tucked away in my Chrome menu or sitting near the address bar, doing their thing. I have a list of extensions that I’ve carried with me over the years, and in this article I am going to share them, with a brief description. Productivity This is a category of extensions whose use spans across all my activities.

Last week while working on a client project, I hit some serious dead end. A memory leak! It’s been a while since I saw one of those. After 10 minutes of chewing on the code, Webpack decided to throw up and leave me with nothing more than this V8 heap dump. See the dump in this GitHub gist. It hit me like a hammer in the head. What the hell was I doing wrong?

Backing up is like investing The quote above is from this article on the Backblaze blog. It stuck with me because I’ve been a very poor investor. Not anymore! I need a backup solution and I’m looking to learn more about the process. While working on this, I caught myself thinking about the process I have been using for the past 5 years. I realized I never wrote about it and I would love to share it with the world.

Someone commented on my previous article but deleted the comment before I could approve it and give a reply. So, it’s apples fault you don’t do backups? The author was right. It’s not Apple’s fault I didn’t back up my data. But it’s Apple’s fault for sending crappy updates on 2000+ EUR computers with 1-month old OSes installed and totally mess them up. Glad we got that out of the way.

Long story short: Thanks to a stupid update pushed by Apple to my computer I was not able in any way, shape or form to access my laptop and save my work, yesterday evening. The problem is that I have to do some client work tomorrow. So I had to choose between deleting my work and re-installing the system, or waste tomorrow, trying to figure out how to save my work (an entire week’s worth of work).

If you’re working with almost any AGILE methodology you probably know what a Spike is. For those of you that don’t know, here’s a definition straight out of THE AGILE DICTIONARY: A task aimed at answering a question or gathering information, rather than at producing shippable product. Sometimes a user story is generated that cannot be well estimated until the development team does some actual work to resolve a technical question or a design problem.