As developers, we produce tons of code each day. We test our code, beautify it with code style scripts and finally verify using continuous integration commands, which control the integrity and cohesion of our solutions. Nevertheless, the true value of used code solution can be checked only by another developer, who knows the business domain, best practices, clean code principles and who may also have a different point of view from yours. In this article, I want to show you how code review can help you keep codebase in order and get more advantages for your team.
Viewing entries in
The software is eating up the world and we all have to face it. This fact drives more and more companies to outsource the IT work. However, finding a right tech-partner or a software house may turn out to be a path dotted with potholes and traps. Why is it so hard to track down a reliable IT partner to build an application? What do we need to consider? Let’s find out!
Project estimates are extremely difficult and important. Clients need ones they can rely on. They put them on their roadmaps. They make promises to their stakeholders based on the estimates. They budget according to them. There's always a pressure for the estimates to be low (cheap), yet accurate. At the same time we never have enough information about the project. This is the crux of every project. That's the intersection of plans, expectations, priorities, assumptions and uncertainties. How do you handle all that?
Have you heard about Scrum, but…? This means “we do scrum, but…” we don’t do retrospectives, don’t do daily standups, etc. Well, there’s a deep wisdom behind all the Scrum practices we give up. Be aware of the risks you create and know how to counteract them. This is a first post in a series that aims to show how you can keep the benefits of Scrum in real life.