3 ms·

> As for me, I've been a developer for 25 years and never wanted to go into management. I love my job because I love to code and I love learning new things. I'm

by WWLink 3y ago

> As for me, I've been a developer for 25 years and never wanted to go into management. I love my job because I love to code and I love learning new things. I'm 100% not the target audience for this book. I feel like you can still gain a lot of respect by loving to code. For one, if you're impactful enough your name will be all over your company's git repositories in commits. You'll have your name in documentation. A lot of newer employees will remember your mentoring. That in itself all earns you valuable respect. Perhaps it's not the same as making sure the CEO knows that you made this piece of software, and did this thing, and that thing... but it does make its way there in a healthy organization.

reactordev 3y ago
“For one, if you're impactful enough your name will be all over your company's git repositories in commits” Or… you’re a busy body that likes to move files around and pretty things up leaving your name on the blame and making it look like you did a ton of work. All you did was open it/save it in VIM. Let’s not praise false indicators. Lines of code isn’t a good measurement of quality, nor is lines committed.
- MiguelX413 3y ago
  Not necessarily.
- evantbyrne 3y ago
  The dude who probably had the most commits at our org was just chosen as the sacrificial lamb of the development team's share of cost cutting. Now I have no opinion of his work personally due to working separately and I generally thought highly of him as a person, but he was considered by some to be responsible for one of the most significant engineering f-ups in the history of the org. It is generally true that traumatic events resonate more deeply with people than positive ones. So you can quietly commit code all day everyday, but if your mistakes are more visible than your successes then you won't go far.
  - Jensson 3y ago
    If you do 10x the work and fuck up at the same rate as everyone else, you will do 10x the fuck ups and they will just remember you as the guy who fucked up things all the time even though you didn't fuck up proportionally more than anyone else.
    - WWLink 3y ago
      I think this is the real reason some people hop companies every other year. They never have to be confronted by the result of past poor decisions.
      - reactordev 3y ago
        That’s one reason. Another reason is they’re struggling at home and need to earn more. Or that they think they were worthy of that promotion they were passed up for. Or perhaps is was because they got stiffed a Christmas bonus. Don’t assume you know someone’s motives.
- WWLink 3y ago
  You zeroed in on one of the things I mentioned. You didn't consider the mentorship, writing documentation, or just general product ownership over time. Of course, if your organization considers a firm handshake and constant eye contact more important than being a competent engineer, so be it.
  - reactordev 3y ago
    Often those things happens outside of git src tree. Confluence or readthedocs in another process that gets completely overlooked by management’s “velocity calculator”.
AdieuToLogic 3y ago
> I feel like you can still gain a lot of respect by loving to code. For one, if you're impactful enough your name will be all over your company's git repositories in commits. You'll have your name in documentation. None of these things garner respect, as respect is earned from people. > A lot of newer employees will remember your mentoring. That is where respect resides. > That in itself all earns you valuable respect. How one interacts with, helps, and/or mentors people is what alone earns "valuable respect." An informal conversation with someone wanting to learn, resulting in a book recommendation, is far more impactful than a few commits.

by WWLink 3y ago

reactordev 3y ago

“For one, if you're impactful enough your name will be all over your company's git repositories in commits” Or… you’re a busy body that likes to move files around and pretty things up leaving your name on the blame and making it look like you did a ton of work. All you did was open it/save it in VIM. Let’s not praise false indicators. Lines of code isn’t a good measurement of quality, nor is lines committed.

MiguelX413 3y ago
Not necessarily.
evantbyrne 3y ago
The dude who probably had the most commits at our org was just chosen as the sacrificial lamb of the development team's share of cost cutting. Now I have no opinion of his work personally due to working separately and I generally thought highly of him as a person, but he was considered by some to be responsible for one of the most significant engineering f-ups in the history of the org. It is generally true that traumatic events resonate more deeply with people than positive ones. So you can quietly commit code all day everyday, but if your mistakes are more visible than your successes then you won't go far.
- Jensson 3y ago
  If you do 10x the work and fuck up at the same rate as everyone else, you will do 10x the fuck ups and they will just remember you as the guy who fucked up things all the time even though you didn't fuck up proportionally more than anyone else.
  - WWLink 3y ago
    I think this is the real reason some people hop companies every other year. They never have to be confronted by the result of past poor decisions.
    - reactordev 3y ago
      That’s one reason. Another reason is they’re struggling at home and need to earn more. Or that they think they were worthy of that promotion they were passed up for. Or perhaps is was because they got stiffed a Christmas bonus. Don’t assume you know someone’s motives.
WWLink 3y ago
You zeroed in on one of the things I mentioned. You didn't consider the mentorship, writing documentation, or just general product ownership over time. Of course, if your organization considers a firm handshake and constant eye contact more important than being a competent engineer, so be it.
- reactordev 3y ago
  Often those things happens outside of git src tree. Confluence or readthedocs in another process that gets completely overlooked by management’s “velocity calculator”.

AdieuToLogic 3y ago

> I feel like you can still gain a lot of respect by loving to code. For one, if you're impactful enough your name will be all over your company's git repositories in commits. You'll have your name in documentation. None of these things garner respect, as respect is earned from people. > A lot of newer employees will remember your mentoring. That is where respect resides. > That in itself all earns you valuable respect. How one interacts with, helps, and/or mentors people is what alone earns "valuable respect." An informal conversation with someone wanting to learn, resulting in a book recommendation, is far more impactful than a few commits.