News for hackers. Stuff that matters.
Re:What I learned working with a senior engineer as a new grad by ChrisMarshallNY on Friday August 19, 2022 @10:37AM (#32521523)
Depends on where you are.

In the company I used to work at, code quality was a huge deal. I think, destructively so.

Nevertheless, I exercise pretty extreme code quality in my work (see for yourself[0]). It's long reached the state of "muscle memory," and I work very quickly.

As I am the person that most frequently has to go back and fix the code I write (I eat my own dog food), I write code that is what I want to see, when revisiting, six months later.

On another note, this industry considers six years to be "senior." I find that interesting.

[0] https://github.com/ChrisMarshallNY#browse-away

Re:What I learned working with a senior engineer as a new grad by yodsanklai on Friday August 19, 2022 @02:25PM (#32524464)
> I exercise pretty extreme code quality in my work

I'd say maintain good code quality on your own project is much easier than within a team. It's like living in a house with different people: not everybody has the same standard regarding keeping the place tidy and clean, and compromises have to be made.

This was one of the biggest pain point for me, moving from my own personal projects to working with other people.

Re:What I learned working with a senior engineer as a new grad by ChrisMarshallNY on Friday August 19, 2022 @03:54PM (#32525329)
This is true. Many things suddenly become much more difficult, when even one other person is involved.

Managers often neglect to take team overhead seriously.