I think there's a really fine line between being efficient and being bad. I try to toe that line by writing high quality code without focusing on the small details that could improve my code but would take hours of extra work to implement. It's cutting corners where it's possible and where it doesn't inhibit future development.
The way I see it, to be a specific type of developer (e.g. product or really technical), you have to learn multiple factions within the whole development.
A really technical developer can be a tech lead or CTO and help other developers grow with complex material.
Product developers may find it a bit more difficult when helping mid/sen developers with complex technical solutions, but they would be an awesome fit for product owner roles.
I think this article is a great example on how to mix "being a pure developer" with other parts of the whole process.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think there's a really fine line between being efficient and being bad. I try to toe that line by writing high quality code without focusing on the small details that could improve my code but would take hours of extra work to implement. It's cutting corners where it's possible and where it doesn't inhibit future development.
The way I see it, to be a specific type of developer (e.g. product or really technical), you have to learn multiple factions within the whole development.
A really technical developer can be a tech lead or CTO and help other developers grow with complex material.
Product developers may find it a bit more difficult when helping mid/sen developers with complex technical solutions, but they would be an awesome fit for product owner roles.
I think this article is a great example on how to mix "being a pure developer" with other parts of the whole process.