[mhinze]

I'm tired of these posts.

I'm tired of an industry where it's assumed that using technical tools is the skill, rather than understanding and applying technical concepts.

I'm tired of "I'm a .NET developer" or "I'm a python developer". I want a world where we're not tied to a particular framework, where people hire expert technologists and business analysts regardless of what framework they used at their last job. Where managers truly value people and interactions over tools and process.

The inhumanity and subsequent waste of it all is really piling up, and theses posts only reinforce the ignorant and shallow perception that the tools make the professional.

[roadnottaken]

Why is it different than the way doctors specialize. Sure, a doctor should have a basic understanding of all physiology - but you want the guy that operates on your heart to have lots of experience. Why is specialization in programming offensive for some reason?

(FWIW - I am not a programmer/developer)

[roc]

Precisely because tool-specialization isn't a good analogue to problem-domain specialization.

e.g. Saying "Ruby Developer" isn't like saying "Brain Surgeon". It's more like saying "Hammer Carpenter" or "Scalpel Surgeon".

Web Developer, Embedded Developer -- these are more akin to specialization on the order of "Brain Surgeon" or "Endocrinologist". Notably, no-one's taking issue with that kind of specialization.

[mhinze]

There are valid specializations for programmers. There are application developers, systems architects, UI engineers, operations specialists, cryptographers, scientific programmers, etc. You don't care that your doctor uses the Acme Scalpel 4000, you just want your gut cut.

[nlawalker]

Yes, but the lead surgeon at the hospital probably doesn't want one doctor using an Acme Scalpel 4000, another using an Ajax Scalpel, and yet a third using a FooBar X-Scalpel.

Maybe that part of the analogy doesn't hold up for a hospital, but it sure as hell does in a software engineering organization. If you have a bunch of people working together towards a common set of goals, it makes things a hell of a lot more complicated if everyone is just working in the language they like playing with the most, regardless of their overall technical knowledge. Organizations standardize on best practices, languages, frameworks and technologies because it simplifies things.

[gdltec]

"You don't care that your doctor uses the Acme Scalpel 4000, you just want your gut cut." Exactly. What makes you think that this is different in software... the end users DO NOT care what tool or framework you use to build the solutions they need. Now, doctors probably have preferences on what tools and procedures to use - just like we programmers.

[mhinze]

And the elevation of those preferences to a dogmatic self-identification is a Really Big Problem. People and interactions over tools and process.

[Gilson_Silveira]

I think you can compare a programmer more to a musician than to a doctor specialist.

If you have the feeling for the music you can create music using anything. Ideas just blow to your mind. The tool, well, it's is just an interface to concretize your idea.

But I think specialization is not a bad idea.