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.
Disclaimer: sorry, but this ain't a post about architecture, leadership, software development, neither any other usual topics you can find here. But I believe its content is more needed today, in the situation we're facing. COVID-19 didn't just disrupt our lives. Its influence seems...
Ironically speaking, COVID-19 [https://en.wikipedia.org/wiki/Coronavirus_disease_2019] has sped up digital transformation in many organisations across the whole globe ;P Remote work is the new standard, even if some were far from ready (that's why I call it remote "leap of faith"...
This article is about how finance-related decisions can lock your career development down if you don't understand what you're really paid for ... Reader, meet X X starts his software development career. X doesn't know much about the job market, local companies, their specifics -...
Without any lengthy introductions - COVID-19 [https://en.wikipedia.org/wiki/Coronavirus_disease_2019] has sent plenty of people to work remotely. Companies that would never (or at least unlikely) consider such a scenario, have jumped (somehow reluctantly) straight onto remoteness bandwagon to secure their daily operations in the times...
I tend to "spend" a lot of keystrokes on various aspects of technical debt and/or poor engineering practices. The list seems endless: component coupling, shallow modeling, leaky boundaries, inconsistent conventions, not-sufficiently-expressive design, incapacitated development agility, unnecessary layers of indirection, overzealous pattern usage, lava flow effect - naming...
I've always been praising the value of maintaining a stable rhythm (cadence) of the software delivery - frequent, regular, habitual, nearly continuous. That's why as a Kanban aficionado I've never minded the concept of a sprint - and in particular the specific idea of...
