3 ms·
Resume-driven development - never heard that term before. Now I have an excellent descriptor for what I see all too often. Maybe O'Reilly should release a boo
by tryitnow 9y ago
Resume-driven development - never heard that term before. Now I have an excellent descriptor for what I see all too often.
Maybe O'Reilly should release a book on RDD?
- ThrustVectoring 9y agoResume-driven development is an organizational pattern, and like all patterns, it exists for better reasons than you'd first think. The lifetime compensation of developers isn't just tied to how much salary they have at the moment. Getting into a dead-end and not developing your skills will definitely set you back over the long term. Like, there's a reason people will pay you a premium for working with COBOL. So there's a very rational pressure to get better total compensation out of a role by choosing resume-developing tools and technologies. On the other end, organizations mostly just care about getting the task done. They've got the choice of doing it in a boring way and paying lots of money for developers who don't want to grow their resume, or indulging in the developers fancies and getting it done more cheaply. tl;dr - resume driven development is a way for companies to pay for projects with "you'll get experience".