Geek, agilista, blogger, codefella, serial reader. In the daylight - I navigate & lead software engineering. #lean #design #aws #elixir #analytics. I speak here for myself only.
I've spotted a nice meme today. The pic itself is meaningless, but the text comment was a true killer: > We will continue having lots of meetings until we find out why no work is getting done. Nail'd it. Don't you think? It may...
In general, the larger the company is, the more it aims for covering the software-related risks by paying for external support services. And it makes sense, at least in theory: * the bigger the company, the more complex its business is * the more complex the business is, the more software...
Quite recently I've had an interesting discussion about the differences between developing applications in various IT ecosystems (OS + platform + language + IDE + libs + ...) - why do some of them suck (always suck / usually suck / sometimes suck) and why some suck more than other. Obviously, these questions are not easy to...
No-Kill-Switch is about tech. Well, various aspects of tech: these related to software engineering and those related to project management (agile project management, to be precise) as well. But the key point is, that as it's related to tech and my professional life is all around...
Dealing with technical configuration of your apps may be tricky. In a simple case you just slap a text file or two and there's no harm done, but once your solution gets more & more complex, all those pesky files get really cumbersone: * keeping the content of them...
Shortening delivery cycle and improving the overall delivery pipeline gets more & more love nowadays. Delivering value more frequently, in a more predictable manner, while remaining truly transparent - who could resist that? That's why 'DevOps' & 'Continuous Delivery' are trending that high in 2014....