What I learned working with a senior engineer as a new grad

Re:What I learned working with a senior engineer as a new grad by enraged_camel on Friday August 19, 2022 @10:45AM (#32521634)

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.

[ Parent | on HN ]

Re:What I learned working with a senior engineer as a new grad by skrtskrt on Friday August 19, 2022 @12:10PM (#32522814)

Yep 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.

[ Parent | on HN ]

Re:What I learned working with a senior engineer as a new grad by pablok2 on Friday August 19, 2022 @01:25PM (#32523785)

If 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.

[ Parent | on HN ]

Re:What I learned working with a senior engineer as a new grad by mmmpop on Friday August 19, 2022 @11:16AM (#32522042)

Perhaps but having "that programmer that management likes" is worth 10x more than whatever mess is generally being made.

[ Parent | on HN ]

Re:What I learned working with a senior engineer as a new grad by bick_nyers on Saturday August 20, 2022 @02:06PM (#32533987)

I 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.

[ Parent | on HN ]