Have you ever proudly released an API only to realise months or years later that it had design flaws which made it a pain to work with? Here are some API design principles that help you design better APIs based on nature.
It’s entirely possible to design APIs that are a joy to work with. But you have to change the way you think about your API. Don’t treat it like a machine, treat it like a living organism instead. Continue reading
The more time passes and the less you actively invest in maintenance the more legacy code you will face. In that sense legacy code is the entropy of software engineering. As a business you need to understand the inevitability and harm of legacy code and fight it continuously.
As an engineer you can build a habit of maintaining and refactoring and learning how to write better tests. However, you can’t beat legacy code on your own so both your organisation and you need to work together to really overcome legacy code. Continue reading
I love how you can connect a few APIs and build something completely new. The thought of computers talking to computers is amazing and APIs are a big part of the open web.
To build great APIs design them for humans, not computers. When you talk about a programming interface it’s best to think about a programmer interface because there’s a human on the other side discovering, integrating and eventually falling in love with your API. Continue reading
We have vast options for monitoring and alerting. But there’s a simple rule to decide if your monitoring setup and alerts make sense.
If you’re deciding which alerts you want to establish, ask yourself: Does this help me sleep at night? Continue reading
Prioritise technical debt by translating it into the language of business. By framing technical debt as cost we have an easily understandable metric we can use to rally for support.
After all, if technical debt does not hurt the business in any way, why should anyone care? Continue reading
How can your early stage startup use technical debt to survive and thrive? How does technical debt in young startups look and where does it come from?
It’s hard to avoid technical debt completely but you can manage it and use it to your advantage. Let us have a look how technical debt is created in startups and how you can keep it in check even when your company is in hyper growth. Continue reading
Looking back over the last 8 years I almost exclusively worked on legacy code and technical debt.
The difference between technical debt and clean software is a difference in degree, not in kind. Only when circumstances change does our interpretation of the code flip from good enough to technical debt. Continue reading
In my years as a software engineer I was always drawn to the shiny new things. But time and time again I got confronted with code ridden with technical debt. If you are working in tech you probably heard of technical debt.
For product managers it is the sword of Damocles alluding delayed projects and rejected feature requests. For engineers it can be a tremendous source of frustration and reason to quit jobs and move on. Why is technical debt so widespread and why is it so hard to beat? Continue reading