Practical Blog
Knowledge Platform
Object Oriented Paradigm The paradigm’s roots started in the 1960s and became dominant during the 1990s. Although it is not exactly an architectural paradigm, it
Let me start with a code sample (in java) that will demonstrate what I am going to talk about: … private IMAPService _mapService; public
Often I hear people doubting the effectiveness of unit tests, they usually say “most bugs we encounter with are ‘integration bugs’”, “they usually happen due to
Understand the Requirements The first step for a productive code review is to understand what the task was all about and think about possible solutions.
Imagine a cool startup place. It has top notch working stations, huge monitors, the latest keyboards. Programmers have open cheques to choose their workstations: Mac Pro, Symphonia,
Have you ever stopped to think about how Legacy Code impacts your time & money? How it impacts your products’ quality, hence, your customers? How it
“Look, it’s critical that we meet our deadline, and I know that we are already running behind. So please, we need you to push faster
Writing tests for legacy code may seem risky, even daunting: will we break our code? Will we need to rewrite extensive parts of our code
Back in 2013 I published the following post, but since I know, no one actually read these links I’ve chosen to quote that post in full.
Object Oriented Paradigm The paradigm’s roots started in the 1960s and became dominant during the 1990s. Although it is not exactly an architectural paradigm, it
Let me start with a code sample (in java) that will demonstrate what I am going to talk about: … private IMAPService _mapService; public
Often I hear people doubting the effectiveness of unit tests, they usually say “most bugs we encounter with are ‘integration bugs’”, “they usually happen due to
Understand the Requirements The first step for a productive code review is to understand what the task was all about and think about possible solutions.
Imagine a cool startup place. It has top notch working stations, huge monitors, the latest keyboards. Programmers have open cheques to choose their workstations: Mac Pro, Symphonia,
Have you ever stopped to think about how Legacy Code impacts your time & money? How it impacts your products’ quality, hence, your customers? How it
“Look, it’s critical that we meet our deadline, and I know that we are already running behind. So please, we need you to push faster
Writing tests for legacy code may seem risky, even daunting: will we break our code? Will we need to rewrite extensive parts of our code
Back in 2013 I published the following post, but since I know, no one actually read these links I’ve chosen to quote that post in full.
