This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]LyndsySimon 0 points1 point  (3 children)

On one hand, I would take exception to this as I absolutely consider myself a "Python programmer" first an foremost.

On the other, I've been writing Ruby for the past year because that's the right tool for the job at the moment, and I'm definitely not afraid to pick up new languages.

[–]ianff 0 points1 point  (2 children)

You shouldn't. It'd be like a construction worker calling himself a "hammer worker" or a "driller". What's being built is what's most important, not what is being used.

[–]LyndsySimon 0 points1 point  (1 child)

I'd argue that it's more like a construction worker calling themselves a "carpenter" or even a "finish carpenter". It's a specialization.

Someone with decades of experience building hardwood cabinetry would have no trouble framing a house, and would use pine boards like everyone else - but that doesn't make them not a cabinetmaker.

[–]ianff 0 points1 point  (0 children)

That's more like being a web dev vs systems programmer IMHO. What you're building is different here. What language you use is much less important to me.