Technical debt is more than just bad decisions. It's an entire ecosystem based on multiple factors. It's the complexity of a codebase contains the relevance of parts of the code and individual developers' knowledge. The latter is the hardest one to tackle and the most expensive one to fix.

Deciding to go freelance is never easy, but after careful consideration and reflection, I have decided to take the plunge and transition to freelance work in 2023. This is the right choice for me, and I am excited about the opportunities and challenges it will bring.

Throughout the years, I've worked with all sorts of tooling to keep track of progress and issues within a team. I've used simple tools like Trello boards, Github issues and post-its. I've also used more extensive tools like JIRA, ClickUp, custom software and many more.

Staying up-to-date with what happens in the web dev world is a challenge. So let me share how I try to do it, and maybe it will inspire you to find your way.

Commit messages come in all forms and sizes. In many code bases, a clean git history is not a priority, but don't be mistaken. It is essential. Writing conventional commit messages is a way to keep your commit messages uniform and easy to read.

Remix.run is the (or not, to be confirmed) hot new Full Stack React framework around the block. A few knowledgeable engineers hype it at the moment.