You're not a senior engineer until you've worked on a legacy project (2023)

Post by HumblyTossed » Mon, Feb 17, 2025, 5:26 PM UTC

seanalltogether wrote: post #31

You're also not a senior engineer until you've been forced to adopt the coding style and practices of that legacy project. A lot of younger developers like to come into a new project and slap on the latest frameworks or coding practices that they've picked up recently, without acknowledging that breaking the standards of the project lead to higher mental load to maintain that code over the long term.

Post by [deleted] » Mon, Feb 17, 2025, 5:26 PM UTC

no_wizard wrote: post #101

powerhugs wrote: post #45

Earlier quoted context omitted.

Engineering isn't about working on the most interesting problems. It's about getting stuff done and management happy. Here, parent explained in detail how to get stuff done, management very happy and secure their position for years to come.

> Engineering isn't about working on the most interesting problems. It's about getting stuff done and management happy Truth is harsh, however this seems to be 100% accurate for nearly all cases of employment. Rarely do you get to focus on simply interesting problems and good engineering as a primary concern

Post by philipov » Mon, Feb 17, 2025, 5:28 PM UTC

no_wizard wrote: post #101

powerhugs wrote: post #45

Earlier quoted context omitted.

Engineering isn't about working on the most interesting problems. It's about getting stuff done and management happy. Here, parent explained in detail how to get stuff done, management very happy and secure their position for years to come.

> Engineering isn't about working on the most interesting problems. It's about getting stuff done and management happy Truth is harsh, however this seems to be 100% accurate for nearly all cases of employment. Rarely do you get to focus on simply interesting problems and good engineering as a primary concern

Post by iwontberude » Mon, Feb 17, 2025, 5:29 PM UTC

pmarreck wrote: post #98

kerkeslager wrote: post #88

Earlier quoted context omitted.

I have hobbies. The most interesting work is going to be 10% interesting and 90% not interesting. In most cases it will be less interesting than that. Prioritizing "interesting" work means you'll always be exploited by the companies that can sell you on less pay, less benefits, less time off, less respect in exchange for some pittance of perceived novelty. Don't fall for this trap.

tell me you don't have ADHD without telling me you don't have ADHD

Post by quickslowdown » Mon, Feb 17, 2025, 5:33 PM UTC

ninetyninenine wrote: post #110

petsfed wrote: post #93

Earlier quoted context omitted.

You've found a way to correctly anticipate new user needs and new technologies years, even decades, in advance? And you've found a way to completely forestall the non-technical demands that force non-ideal design choices? You're sitting on a gold mine friend.

I should say not prevent it. But minimize it in the maximum possible way. I am sitting on a gold mine. But I can’t prove it. That’s the problem with this stuff. The industry moves horizontally with each design such that nobody knows if say the current design trend was better than the last. We go better or we go worse and nobody knows if it actually was. Maybe I am sitting on a gold mine. The problem is you’d never kn…