4 ms·

IMO the best you can do: - Ship often to prod (don’t do theoretical work). - Ship wins (as defined by generally acceptable metrics.) - Have someone in manage

IMO the best you can do: - Ship often to prod (don’t do theoretical work). - Ship wins (as defined by generally acceptable metrics.) - Have someone in management or a PM who is good at selling your wins Even here, though, you will run into problems. There is always a new VP or leader looking to make an impact. Because you maintain the current systems your team is engaging in WrongThink and new VP has shiny new RightThink (AI, etc). As soon as your code hits prod you have “legacy” code. New VP can make promises of future, theoretical riches that you can’t compete with, as you maintain the boring, current reality. Reality is not sexy or interesting. You’re in the old guard now. A lot simply boils down to patronage. Making your higher up VP look successful and being in a position to move with them to their new company.

gjgtcbkj 1y ago
This could not be more true, however the id like to add the patronage goes farther up the chain. They are all just saying want they need to to clear the checks. It an executive has ever actually invented a successful business model I have yet to meet one.
- jakeydus 1y ago
  Oh they have invented a successful business model, it's just that it's successful for those in executive positions. The whole C-suite mentality is as successful for execs as it is cancerous for everyone else.
Aurornis 1y ago
> - Have someone in management or a PM who is good at selling your wins Looking back on my career, one of the single biggest changes I could have made to improve my success was escaping teams with bad PMs as fast as possible. Great PMs improve everything, but they're hard to find. I spent too much time sticking around on teams where bad PMs were driving us in the wrong direction and failing to interface effectively with the rest of the management team. As soon as something changed that removed those PMs from the situation, everything improved.
- awesome_dude 1y ago
  This is why I almost gave up SWE. My skills, abilities, and output had little to nothing to do with my career trajectory, it's only about getting higher ups to sing praises about things that I might not have even done. Add to that when a new/junior manager comes along, they're too busy trying to show everyone that they're the centre of the universe for any actual progress to be made. Edits: typos and spellchecker being too smart so words injected that didn't make sense
  - Aurornis 1y ago
    > it's only about getting higher ups to sing praises about things that I might not have even done. If a company is so broken that promotions are decided based on factually incorrect information, there's nothing to do other than escape to a different company. I'm talking about companies that are functioning okay, but they let the PMs drive what the team works on. A bad PM will send the entire team in the wrong direction and waste your time. In the most extreme example, our PM would get distracted from the goals set by management and want us to do side quests all the time, so the entire team was constantly producing things that management didn't want while missing all of the things they wanted us to do. If your PM is the link between management and the team's directions, a bad PM will sink the team.
    - awesome_dude 1y ago
      I'm in Australia, and I've yet to find a company that isn't broken.
      - idiotsecant 1y ago
        All companies are broken. Many companies are broken in ways that are tolerable or even decent.
        awesome_dude 1y ago
        Look, if everyone could just run their companies how I think that they should be run we'd all be happy :)
halper 1y ago
I liked how you phrased that: "promises of future … you can't compete with". That happens so often, and strangely the argument that those promises have never become real the previous 26 times never works. The glorious future sure is amazing!
atomicnumber3 1y ago
I think you're absolutely correct and I think it goes one step higher level too. As a staff engineer, it's very important to make sure people know you are not the code. The code is just a liability - as you said, it's legacy the second it hits prod. I've found its best to position yourself not as on the side of the "code" but as a EQUAL PARTNER to leadership/product/whoever has power. It's often just a framing problem, too! You can do nearly the exact same things as if you were the BOFH. But just positioning yourself so that leaders see you as an ally in shipping product and impact, vs someone they have to bully to get approvals from on "just building the damn product." Makes it night and day.
- leptons 1y ago
  >its best to position yourself not as on the side of the "code" but as a EQUAL PARTNER to leadership/product/whoever has power. That sounds so utopian to me that it's practically ridiculous. Never in my 40+ years working in tech has any higher-up treated me or thought of me as anywhere near equal. I try to treat the people on my team that I manage as close to equal as I can, but the higher ups would really have zero compunction about "letting me go" in favor of the new hot whoever that someone introduced them to recently, or whatever. They very rarely listen to reason about any issue and it's rare that I'd even get to talk to them. It's been like this at every startup and company I've ever worked for.
cactusplant7374 1y ago
I have never heard of theoretical work but I have heard of shipping every day. I don’t know how often you think is often. But in other places I know people are shipping every day. It’s not ideal to ship often IMO. How could someone ship something substantial in one day? I work on projects that generate the company additional revenue and if those projects took one day to complete they would fire me because they would really only need a software engineer for four days of the year. It’s a vanity metric.
thaumasiotes 1y ago
> Ship often to prod (don’t do theoretical work). > New VP can make promises of future, theoretical riches that you can’t compete with Why is theoretical work advantageous to the VP when he does it but disadvantageous to you when you do it?
- apwell23 1y ago
  because thats their job description and not yours
  - thaumasiotes 1y ago
    What would it look like if you were a staff software engineer whose job description didn't include theoretical work, but whose output consisted almost entirely of theoretical work? That's not an issue of losing political battles, that's an issue of you getting fired very rapidly. This advice is entirely premised on the idea that you can choose to do theoretical work if you want to, but that it will be a bad idea.
- softwaredoug 1y ago
  The VP is likely to get political backing to do a “big change” and leverage resources to make it not theoretical.

gjgtcbkj 1y ago

This could not be more true, however the id like to add the patronage goes farther up the chain. They are all just saying want they need to to clear the checks. It an executive has ever actually invented a successful business model I have yet to meet one.

jakeydus 1y ago
Oh they have invented a successful business model, it's just that it's successful for those in executive positions. The whole C-suite mentality is as successful for execs as it is cancerous for everyone else.

Aurornis 1y ago

> - Have someone in management or a PM who is good at selling your wins Looking back on my career, one of the single biggest changes I could have made to improve my success was escaping teams with bad PMs as fast as possible. Great PMs improve everything, but they're hard to find. I spent too much time sticking around on teams where bad PMs were driving us in the wrong direction and failing to interface effectively with the rest of the management team. As soon as something changed that removed those PMs from the situation, everything improved.

awesome_dude 1y ago
This is why I almost gave up SWE. My skills, abilities, and output had little to nothing to do with my career trajectory, it's only about getting higher ups to sing praises about things that I might not have even done. Add to that when a new/junior manager comes along, they're too busy trying to show everyone that they're the centre of the universe for any actual progress to be made. Edits: typos and spellchecker being too smart so words injected that didn't make sense
- Aurornis 1y ago
  > it's only about getting higher ups to sing praises about things that I might not have even done. If a company is so broken that promotions are decided based on factually incorrect information, there's nothing to do other than escape to a different company. I'm talking about companies that are functioning okay, but they let the PMs drive what the team works on. A bad PM will send the entire team in the wrong direction and waste your time. In the most extreme example, our PM would get distracted from the goals set by management and want us to do side quests all the time, so the entire team was constantly producing things that management didn't want while missing all of the things they wanted us to do. If your PM is the link between management and the team's directions, a bad PM will sink the team.
  - awesome_dude 1y ago
    I'm in Australia, and I've yet to find a company that isn't broken.
    - idiotsecant 1y ago
      All companies are broken. Many companies are broken in ways that are tolerable or even decent.
      - awesome_dude 1y ago
        Look, if everyone could just run their companies how I think that they should be run we'd all be happy :)

halper 1y ago

I liked how you phrased that: "promises of future … you can't compete with". That happens so often, and strangely the argument that those promises have never become real the previous 26 times never works. The glorious future sure is amazing!

atomicnumber3 1y ago

I think you're absolutely correct and I think it goes one step higher level too. As a staff engineer, it's very important to make sure people know you are not the code. The code is just a liability - as you said, it's legacy the second it hits prod. I've found its best to position yourself not as on the side of the "code" but as a EQUAL PARTNER to leadership/product/whoever has power. It's often just a framing problem, too! You can do nearly the exact same things as if you were the BOFH. But just positioning yourself so that leaders see you as an ally in shipping product and impact, vs someone they have to bully to get approvals from on "just building the damn product." Makes it night and day.

leptons 1y ago
>its best to position yourself not as on the side of the "code" but as a EQUAL PARTNER to leadership/product/whoever has power. That sounds so utopian to me that it's practically ridiculous. Never in my 40+ years working in tech has any higher-up treated me or thought of me as anywhere near equal. I try to treat the people on my team that I manage as close to equal as I can, but the higher ups would really have zero compunction about "letting me go" in favor of the new hot whoever that someone introduced them to recently, or whatever. They very rarely listen to reason about any issue and it's rare that I'd even get to talk to them. It's been like this at every startup and company I've ever worked for.

cactusplant7374 1y ago

I have never heard of theoretical work but I have heard of shipping every day. I don’t know how often you think is often. But in other places I know people are shipping every day. It’s not ideal to ship often IMO. How could someone ship something substantial in one day? I work on projects that generate the company additional revenue and if those projects took one day to complete they would fire me because they would really only need a software engineer for four days of the year. It’s a vanity metric.

thaumasiotes 1y ago

> Ship often to prod (don’t do theoretical work). > New VP can make promises of future, theoretical riches that you can’t compete with Why is theoretical work advantageous to the VP when he does it but disadvantageous to you when you do it?

apwell23 1y ago
because thats their job description and not yours
- thaumasiotes 1y ago
  What would it look like if you were a staff software engineer whose job description didn't include theoretical work, but whose output consisted almost entirely of theoretical work? That's not an issue of losing political battles, that's an issue of you getting fired very rapidly. This advice is entirely premised on the idea that you can choose to do theoretical work if you want to, but that it will be a bad idea.
softwaredoug 1y ago
The VP is likely to get political backing to do a “big change” and leverage resources to make it not theoretical.