@bphogan “I am a developer who solves problems with Ruby” is the same as “I am a Ruby developer”. If you need crown moulding done, are you going to hire someoene who says “I do crown mouldings” or someone who says “I solve problems involving wood with carpentry tools.”
@grmpyprogrammer@bphogan I get it. It’s laziness. If I can make the thing I’m really proficient in my identity, and I convince others to do the same, and we convince managers and tech leaders to use it, then we’re set for life and don’t need to learn anything else.
@ramsey@grmpyprogrammer@bphogan You use an adjustable wrench? I’m a screwdriver guy myself. If it can’t be done with a screwdriver it can’t be done. Besides I heard wrenches are insecure.
@andrewfeeney@grmpyprogrammer@bphogan The analogy starts breaking down. Maybe we should use “toolbox full of a certain brand of tools” instead of just “tool.”
@andrewfeeney@ramsey@grmpyprogrammer@bphogan I think that's still over stating it. If you're used to Makita tools, you can pick up a Dewalt tool and use it effectively in about 7 seconds.
Even switching between closely related languages (Java, Kotlin, C#, for instance) can take weeks to build up muscle memory.
Identity is a very complex topic. In many ways, language identity is a thing because we lack other good identity groups, and suck at identifying self identity in a non-tribal way.
@Crell@ramsey@grmpyprogrammer@bphogan Yeah but would you been seen with Makita? Makita is for toy projects. Real craftspeople use “mature” “professional” tools like DeWalt or Milwaukee.
@grmpyprogrammer@bphogan Of course, that’s a very narrow way of looking at it. There’s a whole lot more to “tool” identity than being lazy. For me, there’s a lot of value in being a part of a community surrounding a tool, and using something else sometimes feels like a betrayal.
Add comment