Hi Paul, thanks for your post . Really interesting.
I'd maybe add : " always have the feature in mind" or " be feature oriented"
developpers tend to focus on the technical value / quality before focusing on what we're doing for the user.
Thanks, excellent point!
There's a double standard around #10 - "Don't be afraid to be involved in non-coding stuff" that I think it worth pointing out. Men who do this work are seen as team players, so it's great advice for male engineers, but women (and queer folks, and people of color) are often expected or assigned to do non-coding work, but then not rewarded for it. I'd highly recommend the Being Glue talk by Tanya Reilly.
I like your list, especially #8 preparing us to have our pride hurt. Humility is extremely important.
I also have a remark about #10 - Don't be afraid to be involved in non-coding stuff. I generally agree with it, but be suspicious when as a developer most of your time is consumed by such activities.
I totally agree. You should "protect" your development time as much as possible, but also have a time slot where you work on non-coding stuff :)
Yo Paul great points you picked, in both parts of your article. The urge of not going of my comfort zone is for me pretty strong, so communication with other developers for asking and giving advice and trying to be passioned while doing, is something I need to do more often.
Well written and thanks for reminding me of some good manners I used to have.
It was a good read, both Part 1 and Part 2. Thank you for sharing.
+1000 for points 12, 13. Great article(s)
Thanks for sharing, Paul. That was a great read.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.