4 ms·
Don't know if you're serious, but for the most devs, the job is chosen for, not by, you
by hans1729 7y ago
Don'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"