4 ms·
A cited subset "emphasize that the people part of the process is just as important as the technical part", and I'd argue "1. Be a Developer" does as well. In t
by hga 17y ago
A cited subset "emphasize that the people part of the process is just as important as the technical part", and I'd argue "1. Be a Developer" does as well.
In that case, while in and of itself it's technical, it's the minimum required to work well with developers and is a prerequisite for doing part "10. Proximity breeds understanding" well. It also lets you effectively "3. Ease their pain", since you understand it at some level.
A lot of it comes down to respect and what falls out of that. It's clear the author respects everyone in the process and that goes a long way towards making the disparate functions and people cohere.
I think I'd like to work for this guy: he'd let me hunker down on "engine" work as I prefer most of the time, would welcome the times I want to do HTML/AJAX GUI work, and be very happy about my focus on the big picture, requirements, hand off to QA and production, etc. etc. etc.