3 ms·
- Bouncing a developer from task to task without ever finishing a task - Letting whatever customer screams the loudest dictate product behavior, and then effec
by gwbas1c 9y ago
- Bouncing a developer from task to task without ever finishing a task
- Letting whatever customer screams the loudest dictate product behavior, and then effectively alternating product behavior based on which customer is angry this month
- Deferring technical debt until a customer screams
- Hiring unreasonable product managers who have unreasonable expectations. (This just leads to a lot of time being burnt in haggling and a much worse product delivered.)
- Treating software as an art project, getting obsessed with pixels and fonts instead of functionality
- Not paying enough
(edits)
- Interrupting programmers constantly for trivial matters
- Allowing the entire organization to interrupt a developer at any time because he's unofficially become a "go-to" person
- Not backing up critical processes when departments interact. (This is the information needed when there is a bug, support escalation, ect.)
- Expecting developers to handhold people in other departments
(more edits)
- Micromanaging task priority, assuming that a developer jumped on a specific task and completed it instantly
- donatj 9y ago> alternating product behavior based on which customer is angry this month This strikes way too close to home.