this post was submitted on 21 Jun 2023
37 points (93.0% liked)

Experienced Devs

3978 readers
3 users here now

A community for discussion amongst professional software developers.

Posts should be relevant to those well into their careers.

For those looking to break into the industry, are hustling for their first job, or have just started their career and are looking for advice, check out:

founded 1 year ago
MODERATORS
 

I generally don't like "listicles", especially ones that try to make you feel bad by suggesting that you "need" these skills as a senior engineer.

However, I do find this list valuable because it serves as a self-reflection tool.

Here are some areas I am pretty weak in:

  • How to write a design doc, take feedback, and drive it to resolution, in a reasonable period of time
  • How to convince management that they need to invest in a non-trivial technical project
  • How to repeat yourself enough that people start to listen

Anything here resonate with y'all?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] HairHeel 6 points 1 year ago (1 children)

How to convince management that they need to invest in a non-trivial technical project

How to convince management to stop throwing money at a dead end plan

[โ€“] valence_engineer 4 points 1 year ago

In my sad experience, you don't but simply try to avoid getting caught in the blast radius of it failing. Someone approved/supported the project and someone approved/supported the sunk cost that already went into it. Those people have more power than you and they will not like looking bad due to you.