Hacker News new | ask | show | jobs
by thom 4186 days ago
I worked at an agency where it was common to practice CV-driven-development. You'd decide what bullet points you wanted on your CV at the end of a project - be they new languages, frameworks, responsibilities etc - and manipulated the project (often disastrously) to make them true.
3 comments

Gah -- now that I know the phrase "CV-driven-development", I can't unsee it!! This happens everywhere :-/
I'm guessing this tactic was a means to an exit for individual developers looking for the door?

One of the things that bothers me about resumes that cross my desk is the emphasis on skills over projects. I blame linkedin since it allows HR (generally, not the most innovative or thoughtful people I've dealt with, especially at the banks) to half-ass their job to the Nth degree with filters begging to be reverse engineered by a job seeker.

I think there is value in building towards a goal skillset (I do the author's resume goal setting myself, actually), but I generally never share my resume and if I do, I am completely legit in what I present).

I have worked at companies where this happened some one wanted to get promoted to a first level manager) so to tick the required experince boxes they burned 10 man years and £1,000,000 to re impliment an existing perl system in Oracle as orace was teh prfered solution in our company.