19
Habits of great software engineers | vadim kravcenko
(vadimkravcenko.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 21 Nov 2023
19 points (85.2% liked)
Programming
17225 readers
253 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
Doesn't sound like a great software engineer to me
I'm not sure about the exact percentage but I don't think it's necessarily that far off. I spend a lot of time reviewing code, designing, documenting, reading documentation. Actually writing code is a cherry on top.
Yeah. As a manager of developers, I don't want my team to spend their time producing code.. I want them to spend their time solving problems.
If anything 20% is on the high side, for experts working in difficult (profitable) domains.
When we pointy-haired-bosses are doing our job right, producing new code is a much lower priority in the software engineer's day, behind understanding and maintaining the important code that is critical to the objectives of the organization.