Posts tagged "software-development"

Technical Debt - the silent villain of web development

Technical Debt - the silent villain of web development

Over 4 years ago our CTO wrote a blog post claiming that technical debt is the number one reason why software development projects get derailed. Years have passed since, and I can say that he couldn't be more right. Although I see that business owners get more familiar with the term technical debt, it quite often plays the role of an elephant in the room. And in the long run, such stories rarely have happy endings. So if you don’t know what the technical debt is, or you do but you don’t think you should worry about this villain - better read further.

Read More
Boy scout rule in 6 examples - the basic principle of web development

Boy scout rule in 6 examples - the basic principle of web development

Not everyone was a scout in his youth. Most of programmers, however, have probably heard of the Boy Scout Rule in software development. But can you name a few of the activities that are part of that rule? When I started to explore this topic, looking for what exactly needs to be done to say "I just applied the boy scout rule", I only found one thing: "Leave your code better than you found it" - everyone quotes Uncle Bob. But what does it mean? What am I supposed to do exactly?

Read More
How to delete… not to delete yourself?

How to delete… not to delete yourself?

I want to present you a real story that happened in a project we took over. On this day, Sentry revealed a strange error. The short analysis showed that the error occurred when a user was removed. But wait, there is no such feature as removing a user! What happened?!? I analyzed the logs and found out that someone wanted to delete his/her profile picture and instead... removed himself!

Read More
Effective task reporting - 6 rules that will speed up your development process

Effective task reporting - 6 rules that will speed up your development process

Task completion reporting may not be the most interesting part of the software development process, but when it’s done right it can be both effective and effortless, significantly speeding up internal testing and customer acceptance. Good reporting ensures that everyone is on the same page, minimizes guesswork, and allows you to identify potential misunderstandings. It also helps to make sure that work reported as finished is actually done. In the end, it contributes to speeding up the development process and shortening time to market for new features. To make it happen, I suggest introducing 6 simple rules of good task completion reporting.

Read More
5 reasons why rewriting an application from scratch is a bad idea

5 reasons why rewriting an application from scratch is a bad idea

When building an application, you will for sure reach a moment when someone suggests you do a full rewrite. This could be your developer or anyone else (including yourself). This scenario might be tempting as, in most cases, the software you have is not ideal. It has bugs, breaks from time to time, doesn’t scale well, the code is ugly, the framework you use is not maintained anymore, etc. It might feel a bit like wading through a vat of molasses. You feel like this is the best solution to all your problems, maybe you can already see the shiny new application that you are going to build and the money it will earn, happy customers, no bugs, etc.

Read More

This website uses cookies to guarantee the best experience for the user. If you continue browsing, we consider that you agree to their use.