Stuck at Sr. Any Advice to get to staff?

Dec 23, 2021 15 Comments

TC 300k at signing, πŸ₯œ after docucrash.
YOE 12

Feeling like I'm a loser, would appreciate any advice.

Spent many years caring very strongly about code quality, modularity, component design, api design and that knowledge seems to have just put me at odds with folks on my team, prolonging code reviews for seemingly little benefit. Almost every codebase I've been in has been a rats nest and trying to untangle it doesn't seem to lead to any kind of career advancement. Trying to figure out how to stop focusing on the code and instead figure out the best ways to generate impact. Especially when tasking is mostly set by my manager and collaboration while remote is tricky.

#staffeng
#losersclub

comments

Want to comment? LOG IN or SIGN UP
TOP 15 Comments
  • Snap / Eng
    πŸ‘» Smooth

    Go to company page Snap Eng

    πŸ‘» Smooth
    Instead of fixing broken codebases, focus on starting new ones right. Be the one setting the rules by example and that codebase will probably evolve much better. Then brag about the dev productivity you created by leading when it mattered.
    Dec 23, 2021 3
    • Snap / Eng
      πŸ‘» Smooth

      Go to company page Snap Eng

      πŸ‘» Smooth
      Make sure you know the medium and long term plans, and when there’s something new to build to support a new feature, own it.

      Just get yourself in the loop. Read, talk to people, just be informed somehow.
      Dec 23, 2021
    • OP
      Yeah this is clearly one of my biggest skill gaps. I collaborate across teams to get my tasks done, problem solve together but just popping on a zoom with a rando colleague to gain info for what they are working on, what they want to work on and inserting myself seems like an awkward meeting invite. We've got a labyrinth of confluence wikis, how to identify when it's appropriate for me to jump in and offer help. Assuming I can find something how to bring up my desire with manager who has his own plans for my 60hr work week.
      Dec 23, 2021
  • My opinion is a little jaded. Trust your team-mates. Once i got to a level where i was leading multiple org level projects, I stopped looking at the code with a fine tooth comb but instead looked at it from a design, maintenance and security perspective. Build better relationships and nudge developers to do the right thing. think of ways to improve developer productivity and improve growth of the end product as a whole. Also contribute in discussions from a 10000ft level instead of the nitty gritty stuff. Show optimism and always be motivating.
    Dec 23, 2021 3
    • Please take this with only good intentions from my side. Our roles are very demanding and after being jaded by the people around us, it’s difficult not to be pessimistic. a therapist helped me out a lot during covid times. I would recommend atleast a couple of sessions with someone. I had to have medication for a 6 month period but its helped me.
      Dec 23, 2021
    • OP
      Thanks dude, I've been to therapy before but nobody has recommended medication. Still probably couldn't hurt to give it another try.
      Dec 23, 2021
  • New
    Zealand

    New

    Zealand
    Speaking of docucrash, how's the vibe in the company? Are people addressing the root cause for the crash in company meetings?
    Dec 23, 2021 3
    • Google
      πŸ₯œ TC

      Go to company page Google

      πŸ₯œ TC
      Isn't it pretty clear the stock pumped a bit too hard from the pandemic, and is returning to reality now that things are reopening?

      Valuations were pretty far-detached from (prospective) company performance, so pointing fingers at any particular employees is an odd concept.
      Dec 23, 2021
    • OP
      Humans gonna human I guess. I'm not pointing fingers at anyone, expect myself for joining before the correction.
      Dec 23, 2021
  • You have to be able to communicate effectively and show leadership ability. I think your outlook on code is off. At the end of the day the business dgaf about code modularity. They want problems solved. Tech debt sucks but you have to see the big picture. Here is an example. A sr dev complains about tech debt and wants to dedicate multiple sprints to fix it immediately. A staff engineer is able to tell the business that we will deliver xyz within the next month but if we want to be able to adjust to market changes effectively we need a month to pay down some of the tech debt we have.
    Dec 23, 2021 1
  • New
    hugh jarse

    New

    hugh jarse
    i’d say that given your description it’s not possible at your current job. you have good understanding that staff is not about writing the best perfect code or being the smartest person. use that during discussion with your future employer
    Dec 23, 2021 0