An epidemic problem in software development: Resume driven development
An epidemic problem in software development: Resume driven development.
What it looks like: Developers suggest the tech they want to learn, instead of the tech that’s warranted for their use case.
Example: “We should use <super complex tech> to implement this contact form.”
To avoid resume driven development, get multiple opinions for key technical decisions. The group can help sniff out over-engineering.
Ask:
Is this warranted for our use case?
When is this tech a good fit?
When is it overkill?
What are the tradeoffs?