4 ms·
It's not obvious to me why choosing the right tool for the job is better than choosing the right job for the tool.
by im3w1l 7y ago
It's not obvious to me why choosing the right tool for the job is better than choosing the right job for the tool.
- hans1729 7y agoDon't know if you're serious, but for the most devs, the job is chosen for, not by, you
- collyw 7y agoI have worked with a couple of devs who decide to pick and choose what they work on. Usually they are seen as important by management / company owners and not team players.
- barbarbar 7y agoI have worked with them too.
- coldtea 7y agoIsn't that a slave mindset? You weren't born prebound to a specific job. Most devs (heck, most workers in any industry), can try and look for appropriate jobs.
- dkersten 7y agoSure, you can, but its usually not desirable to jump ship the moment a task comes along that is less suitable to your tools of choice. I often find myself using languages I’d rather not (yaml for ansible/docker-compose or shell scripts are common). Or maybe you love everything else about the job, besides the language you must use. Or you love everything and the language, but now you’re asked to complete a task that’s not really suited to the language. Ir maybe you love everything about your job and then are asked to fix something in a legacy project.
- masukomi 7y ago"appropriate jobs" most devs have "appropriate jobs" for their skillset. It doesn't follow that the tooling chosen by others before you at that job is "appropriate" or that the language is "appropriate" or that you have any choice in the matter. Most of us don't. Most of us work within the constraints provided. Some of us work to remove or change those constraints. getting an "appropriate job" rarely addresses these problems and even more rarely makes it evident that they exist before you take the "appropriate job"
- pintxo 7y agoMight it be easier to switch tools than jobs for most people?
- eurg 7y agoThat has not been my experience. In a C# shop, if you want to do something not-C#, best is to switch employers. I don't say that placing such high value just into what tool you use is smart; but changing tools in a company is often a total no-go.
- m0xte 7y agoYes totally that. I have been told many times in the last 20 years that the only thing that gets used comes from Microsoft. Literally the same shops end up with several piles of unmaintained crap which is either "not invented here" stuff, abandoned microsoft frameworks and all the staff have left to go find another job because it's not shiny any more. Also a bad outcome.
- mpiedrav 7y agoBehind the enterprise tooling propaganda, there is the real programming endeavor with whatever tools are appropriate for the tasks (given the constraints of time, team size, developer expertise, maturity of libraries, etc.) A software development business is not really about programming languages, libraries, or tools, but about the game of power in the organization (even when the end user doesn't care how the product was developed). Anything that threatens that power is easily dismissed.
- im3w1l 7y agoA NIH attitude is kinda the the opposite of what I meant. Choosing the right job for the tool, would mean that all the wrong jobs should be outsourced.
- masukomi 7y ago> Choosing the right job for the tool, would mean that all the wrong jobs should be outsourced. outsourcing that is just "kicking the can down the road" some poor developer is still left dealing with the same problem. It doesn't change anything other than who has to do the thing you don't want to / don't think is right.
- mbrodersen 7y agoI think it is better because it pushes you beyond your comfort zone. You will learn new things. And sometimes those things are better than what you currently think is "best". If you can only function well in a very specific environment then you are not very flexible.