A junior colleague comes to you with an idea on how to refactor/improve the existing functionality in the system you are developing together. You're very happy that he's trying to think about things, and you definitely commend him for it, and give the possibility a try.
During the analysis, you discover that the proposed solution is not better than the existing one, and even contains design problems. Unfortunately, though, these are such tricky problems that you can't directly point them out, and they are based more on gut feeling and experience based on running other systems. For example, a newly proposed solution could with some probability increase operating costs by about 30% and you would have to partially retrain the existing team.
How do you decide?
Jan Barášek Více o autorovi
Autor článku pracuje jako seniorní vývojář a software architekt v Praze. Navrhuje a spravuje velké webové aplikace, které znáte a používáte. Od roku 2009 nabral bohaté zkušenosti, které tímto webem předává dál.
Rád vám pomůžu: