5 ms·

It's called resume driven development, and the reason it's done is because it helps those who do it get jobs

shantly 7y ago
As long as companies keep expecting experience in very specific technologies (only at work—400 hours on a hobby codebase don't count for as much as 40 hours writing something at a job for determining competence in a language or framework or whatever, it seems) this will keep happening. It's really, really dumb, but there's little other choice for folks who want to keep their skills (=the names of tools & languages they've used to write something for pay) up to date (=trendy high-paying buzzword compliant). Doubly true if you're not all-in on one of the major Bigcorp silos (Java, C#).
- royjacobs 7y ago
  At a previous job I worked with someone who didn't see a buzzword they didn't like. Since nobody was stopping them, they designed an incredibly convoluted system using all the latest tech. In the end we replaced it with a JVM server and a Postgres database. I occasionally check their LinkedIn and they're still spending 12-15 months every time at companies, being CTO or Big Data Strategist or whatever.
  - aswanson 7y ago
    Ambition and incompetence. Nice combo.
    - mannykannot 7y ago
      The Dunning-Kruger career path: persuade the people hiring to think that you are more competent than you are.
- unlinked_dll 7y ago
  anecdata but I've only had terrible experiences with companies looking for specific technologies (e.g. a job listing of "$LANGUAGE Developer"). Mostly good experiences when it's a specialist gig that happens to require a specific technology. Like some parts of a stack aren't interchangeable and aren't easy to pick up overnight.
aswanson 7y ago
RDD. That is effing hilarious.
camdenreslink 7y ago
Almost nobody is hiring rust devs right now.
- chc 7y ago
  I wouldn't be surprised if the ratio of competent Rust developers to Rust jobs were worse than 40:1.

As long as companies keep expecting experience in very specific technologies (only at work—400 hours on a hobby codebase don't count for as much as 40 hours writing something at a job for determining competence in a language or framework or whatever, it seems) this will keep happening. It's really, really dumb, but there's little other choice for folks who want to keep their skills (=the names of tools & languages they've used to write something for pay) up to date (=trendy high-paying buzzword compliant). Doubly true if you're not all-in on one of the major Bigcorp silos (Java, C#).

royjacobs 7y ago
At a previous job I worked with someone who didn't see a buzzword they didn't like. Since nobody was stopping them, they designed an incredibly convoluted system using all the latest tech. In the end we replaced it with a JVM server and a Postgres database. I occasionally check their LinkedIn and they're still spending 12-15 months every time at companies, being CTO or Big Data Strategist or whatever.
- aswanson 7y ago
  Ambition and incompetence. Nice combo.
  - mannykannot 7y ago
    The Dunning-Kruger career path: persuade the people hiring to think that you are more competent than you are.
unlinked_dll 7y ago
anecdata but I've only had terrible experiences with companies looking for specific technologies (e.g. a job listing of "$LANGUAGE Developer"). Mostly good experiences when it's a specialist gig that happens to require a specific technology. Like some parts of a stack aren't interchangeable and aren't easy to pick up overnight.

aswanson 7y ago

RDD. That is effing hilarious.

camdenreslink 7y ago

Almost nobody is hiring rust devs right now.

chc 7y ago
I wouldn't be surprised if the ratio of competent Rust developers to Rust jobs were worse than 40:1.