|
|
|
|
|
by madaxe_again
1276 days ago
|
|
On your old car, you can just take it apart and see how it works. Don’t have the part? Improvise. It’s heavily skill-based, and a little knowledge will take you a long way. As long as you know your fundamental toolchains, you can make any part, do any job. On your new car, it’s a series of black boxes, cables, and tubes - you don’t know and don’t care what happens inside the boxes, just what goes in, and what comes out. It’s heavily knowledge based - you need to know an awful lot about the boxes and how to work with them - but nobody expects you to machine your own parts. If one isn’t made that suits your purposes, you have to go to an old car guy. The skillsets are similar but different. To be clear, I really am talking about cars and mechanics here - you won’t find many who can fix up both a 1960 and a 2021 motor. You’ll find plenty who can do one or the other, however. And yeah - the same applies to developers. |
|
I specialised in new vehicles and then you have specialise in brand to actually know whats going on and how to fix said black boxes and systems.
My reason for training to become a software engineer was mainly because I felt like the knowledge and on-going training you need to retain/constantly learn was not worth the money earned.
Instead now I earn my bread from what was my hobby, essentially the same work ethic as far as knowledge is concerned just less back breaking to put into practice.