Programming posts

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
Top 5 hacks to fix slow web applications

Top 5 hacks to fix slow web applications

A growing customer base is usually a good sign. But also it can cause you a lot of pain and suffering, i.e. when you hit limits of the application, and it will become too slow to keep the customers interested, or even goes down. In this article I will cover 5 hacks to overcome the most popular scalability issues within hours.

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

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