In my experience for most developers the behaviors boil down to just a few questions?
1. Are the developers willing to write original code or must they be limited to configurations or tooling?
2. Are the developers willing to accept any API (RTFM) or must the developers be limited to prior known APIs?
3. Are the developers willing to accept failure for missing unspecified, but commonly known, requirements such as accessibility, usability, security, or domain specific knowledge?
4. Are the developers willing to alter their personal routines to accommodate a shift in requirements and delivery dates or do the developers shift requirements to accommodate their routines, such as work-life balance?
5. Will the developers write technical documentation to describe process and approach or will the developers shift requirements in anticipation of forth-coming technical documentation?
6. Will the developers refactor code to achieve simplicity (imperative), descriptive concepts (declarative), code style, or not at all? The motivations generally do not overlap.
7. Will the developers accept code that better achieves business concerns or end-user preferences (object measures) in violation to preferred structures or styles (subjective measures)?
8. Are the developers willing to read the existing code (RTFC) before recommending new tools or solutions?
1. Are the developers willing to write original code or must they be limited to configurations or tooling?
2. Are the developers willing to accept any API (RTFM) or must the developers be limited to prior known APIs?
3. Are the developers willing to accept failure for missing unspecified, but commonly known, requirements such as accessibility, usability, security, or domain specific knowledge?
4. Are the developers willing to alter their personal routines to accommodate a shift in requirements and delivery dates or do the developers shift requirements to accommodate their routines, such as work-life balance?
5. Will the developers write technical documentation to describe process and approach or will the developers shift requirements in anticipation of forth-coming technical documentation?
6. Will the developers refactor code to achieve simplicity (imperative), descriptive concepts (declarative), code style, or not at all? The motivations generally do not overlap.
7. Will the developers accept code that better achieves business concerns or end-user preferences (object measures) in violation to preferred structures or styles (subjective measures)?
8. Are the developers willing to read the existing code (RTFC) before recommending new tools or solutions?