Archive

Technical debt is a term used a lot whenever a codebase is not to our liking, and there's never enough time to fix all of it. What actually is technical debt, how do you quickly prioritize what to work on - and what are these GitHub Blocks that people are talking about?

If you are interested in more articles and news about web product development and entrepreneurship, please feel free to subscribe to new articles via email, via RSS, or to follow me on Twitter.

What is technical debt?

"Technical debt" is often used as a term for basically any kind of code we don't like, be it difficult to understand or just written by someone who since left the company. And often, it is considered as something to avoid at all cost.

"Writing a blog" is usually taken as "writing articles for a blog". I did this for a while, using Ghost to host the blog. And it mostly worked, but there were multiple reasons for me to change it: - Have an actually running open-source application, both for experimenting, and for my CV - Try out NextJS, rush, and other technologies - Be able to automate whatever I want around the blog

What I thought would be a project of maybe a month, turned out to take me almost a full year. Here's what I did and what I learned on the way.

If you are interested in more articles and news about web product development and entrepreneurship, please feel free to subscribe to new articles via email, via RSS, or to follow me on Twitter.

Overview