I think there are no technical teams that do not have a technical debt. Good teams have a limited amount planned for refactoring in the nearest future. Not-so-good teams may have a dept that will take a couple of years to get rid of. Let us see how to live with the second situation and turn it into the first one.
Read MoreMany developers think that the code they are writing is perfect or close to it. It follows architectural best practices, properly structured and commented, and serves its purpose. All these things may be accurate; however, it is not enough to call this code perfect. Where is the catch?
Read MoreMany software developers like writing code, considering this process as an act of creation of something beautiful. However, reviewing a code is better and more efficient from a personal development point of view. The following article explains how code review helps the developer write good code and why it is better than writing a code.
Read MoreThere is an interesting practice in writing good code — do it in such a way so any beginner developer can support the code. It is a common scenario in many companies, making sense to think ahead and prepare for it from the very beginning. Let us see what traits (positive and negative) such an approach has, and how to utilize it in real life.
Read MoreCode review is one of the best practices commonly used in software development. Many developers include it in their development workflows. However, code review has some traits which many consider as disadvantages. Let us see these traits and find a way to deal with them.
Read MoreEvery developer faced a situation when he wrote a piece of code that works inexplicably. It is magic! — he says. But why a developer think that this is magic and not a consequence of some internal processes execution? And what should he do with this magic?
Read MoreDevelopers often complain about the complexity of the software they have to develop or support. They mention application architecture, amount of supported code, code complexity, business requirements, and the way customers use an application (user experience). Let us have a look at the most prevalent complaints, underlying issues, and ways to deal with them.
Read More
