Peter Benjamin
Feb 25, 2017 · 1 min read

There are a few fallacies I’d like to point out in this article:

Over-generalizations

Saying that “full-stack developer” title is bad because it’s bland and vague without offering substantive evidence to back it up (beside a link to an article by DHH) is a disservice.

Furthermore, saying that “full-stack” is equivalent to saying “ I’ll do whatever job, it doesn’t matter” followed by:

And if that’s the case, well, stick with that label.

Is very demeaning.

What if a developer is truly passionate about developing complete products, comprised of front-end and backend components (such as Rails web apps)?

Job titles are tied to quality of software

You tried to make a case against using “full-stack developer” title by saying:

But can you really do all of that well?

This is just absurd. In fact, you link to DHH’s article about how rare it is see good software. So, according to you, no one should call themselves any title unless they can write (and ship?) good quality software?

Final thoughts…

I noticed from your bio that you work at Basecamp.

I hope that you don’t repeat DHH’s common transgressions of hyperbolic & antagonistic attitude towards issues that you don’t agree with.

    Peter Benjamin

    Written by

    Now migrated to https://pbnj.dev & https://dev.to/petermbenjamin