Re:Ask HN: What does mastery look like in software engineering?
by k3liutZu on Thursday January 07, 2021 @03:03AM
(#25668510)
Enabling the org to accomplish more with less (or keep it from falling into different pitfalls) is sexy.
I feel it's a core part of my job to keep the rest of the eng team happy and producing value. A lot of times this comes down to seeing problems as they arise (ideally before them, but it gets harder to convince management of future issues if they haven't manifested yet).
Re:Ask HN: What does mastery look like in software engineering?
by m463 on Thursday January 07, 2021 @04:10PM
(#25677520)
> it gets harder to convince management of future issues
that's a tough one, maybe the tough one.
It's hard to prioritize "trivialities" over features, especially when you haven't even given thought to defending the obvious.
Thankfully some of these things are being codified somewhere externally, say:
https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-s...
For instance, having an easy build process, or understanding version numbers, or preventing an upgrade to this year's compiler.