371–374 of 374 posts
Earlier quoted context omitted.
I've seen a lot of red flags in my career where managers put people on PIPs -- when in reality it's not a PIP but a personality conflict. And from what I understand at Amazon, it's kind of the same thing, but PIPs have been aggressively weaponized.
Isn’t that what a PIP is? A Personality Improvement Plan?
Earlier quoted context omitted.
Who hurt you? Do you even like software engineering? Quit, and go make sourdough bread, shit.
I like building things with code. I don’t like group bikeshedding about processes, tools and “best practices.” Do I even like software engineering?
But it's the difference between an individual carpenter making a rocking chair for himself and his family, or maybe making a couple to sell to his friends, and being a structural engineer.
Bikeshedding is not a necessary antipattern to the process, but large software projects absolutely need group collaboration, and a discussion of processes, tools, and best practices.
Earlier quoted context omitted.
I like building things with code. I don’t like group bikeshedding about processes, tools and “best practices.” Do I even like software engineering?
No, you like coding. Which is okay! But it's the difference between an individual carpenter making a rocking chair for himself and his family, or maybe making a couple to sell to his friends, and being a structural engineer. Bikeshedding is not a necessary antipattern to the process, but large software projects absolutely need group collaboration, and a discussion of processes, tools, and best practices.
Earlier quoted context omitted.
I like building things with code. I don’t like group bikeshedding about processes, tools and “best practices.” Do I even like software engineering?
No, you like coding. Which is okay! But it's the difference between an individual carpenter making a rocking chair for himself and his family, or maybe making a couple to sell to his friends, and being a structural engineer. Bikeshedding is not a necessary antipattern to the process, but large software projects absolutely need group collaboration, and a discussion of processes, tools, and best practices.
Based on your comment history (which is consists of about 0% technically interesting topics, and about 100% pro-amazon 'tales from a super-senior principal engineer guyyyss') tells me you don't like engineering, you like politics and beuracracy. Which is okay!