3 ms·
In my experience it is useful to have such people on the team, but if they make up most of the team then the codebase becomes a gigantic mess over time, and it
by enraged_camel 4y ago
In my experience it is useful to have such people on the team, but if they make up most of the team then the codebase becomes a gigantic mess over time, and it negatively impacts everyone else.
- mmmpop 4y agoPerhaps but having "that programmer that management likes" is worth 10x more than whatever mess is generally being made.
- skrtskrt 4y agoYep I tend to be more on the spectrum of focusing on code & architecture quality over raw productivity, and I find the "plow through it and get it done" engineer to be the perfect foil to have on my team. Ultimately it gets done faster than it would if the whole team was my personality, but with higher quality than if the whole team was their personality.
- pablok2 4y agoIf you're lucky enough to have someone buy into a centralized code/arch strategy then this is idea, the issues arrive when the code/arch strategy isn't a hard sell for the plow engineers.
- bick_nyers 4y agoI consider myself a plow engineer, and I definitely agree with you, a team full of people like me would descend a codebase too deep into chaos. A dance between balance of order and chaos is ideal, as too much of the other has significant negative side-effects.