Re:Three Tribes of Programming (2017)
by astuary on Friday September 06, 2019 @02:53PM
(#20898639)
I'm continually surprised at how quickly non-technical problems come to dominate my time on a software project. E.g. my code doesn't work because two business stakeholders have slightly different, irreconcilable notions of what a "customer" is and it has to satisfy both.
[ Parent
| on HN ]
Re:Three Tribes of Programming (2017)
by nudpiedo on Saturday September 07, 2019 @05:26AM
(#20902743)
Or things as mundane as discover that a third of your coworkers (even seniors) are so much emotion driven that may as well go back to high school in order to learn how to socialize and be professional avoiding jealousy, envy, unnecessary competence or just plainly learn how to work in team and how to follow some sort of structure in an organization.
unnecessary competence
What on earth do you mean by this? It sounds rather like advocating just doing the minimum you can, for the sake of harmony.
I think he/she meant unnecessary competition, rather than competence.
Re:Three Tribes of Programming (2017)
by nudpiedo on Saturday September 07, 2019 @08:40AM
(#20903406)
*unnecessary competition, (cannot edit anymore)
What I speak is about individuals trying to compete against its own team to defeat them in some unnecessary priority rather than collaborate and play all together.
Re:Three Tribes of Programming (2017)
by ALittleLight on Friday September 06, 2019 @11:48PM
(#20901678)
We desperately need them to do X for our project to succeed. They have a brilliant and extremely compelling reason not to do X.