4 ms·

I found the trick was to get a job in software development. That solved the problem of trying to find things to do, other people do that hard work and bring me

by eterm 4y ago

I found the trick was to get a job in software development. That solved the problem of trying to find things to do, other people do that hard work and bring me requirements. They even pay me for it too! I don't know what you're after, but if your aim is to go into software development as a profession then read on. Otherwise skip the rest. Honestly, if you have the fundamentals down you can probably find an entry level job and learn the rest on the job. No tutorials will prepare you for real experience in software development. Programming is only about 20% of software development in my experience. It's a critical 20% that you can't do without, but the rest is hard to prepare for and best just to get real experience of. There's no point spending forever learning to be the best in the world at that 20% without discovering if you even enjoy the other 80%. There are even far too many who hate that 80% and often will not be scared to share this disdain freely. The trick is to ignore them, fully engage with the whole job and you'll quickly out pace them in career development, and you'll likely enjoy your job a whole lot more too.

programmor 4y ago
> There are even far too many who hate that 80% and often will not be scared to share this disdain freely. The trick is to ignore them, fully engage with the whole job and you'll quickly out pace them in career development... Taking cheap shots at your coworkers is the true way to get outpaced in career development. If OP is looking for career advice, this kind of attitude is not good advice. Humility is the right path. The 20% is not accurate, at least in the U.S. in my personal experience. Requirements-gathering, software design and implementation is maybe around 60% of your job at most companies in the U.S. At the end of the day, you get paid to connect the business domain to the technical details of software that will solve the problem; the other 40% of the time you are not doing technical things, you are responsible to communicate, attend meetings, give updates, ask questions, and manage projects. At least, after you've gained some experience. Being a good programmer is how you get the job in the first place. You have to build up the rest of the package, which is very doable if you are humble and join the right company.
- eterm 4y ago
  I think you misunderstood my comment, at no point did I suggest taking "cheap shots" at anyone, and indeed my advice was to focus on "the rest of the package" as you suggest.

by eterm 4y ago

programmor 4y ago

> There are even far too many who hate that 80% and often will not be scared to share this disdain freely. The trick is to ignore them, fully engage with the whole job and you'll quickly out pace them in career development... Taking cheap shots at your coworkers is the true way to get outpaced in career development. If OP is looking for career advice, this kind of attitude is not good advice. Humility is the right path. The 20% is not accurate, at least in the U.S. in my personal experience. Requirements-gathering, software design and implementation is maybe around 60% of your job at most companies in the U.S. At the end of the day, you get paid to connect the business domain to the technical details of software that will solve the problem; the other 40% of the time you are not doing technical things, you are responsible to communicate, attend meetings, give updates, ask questions, and manage projects. At least, after you've gained some experience. Being a good programmer is how you get the job in the first place. You have to build up the rest of the package, which is very doable if you are humble and join the right company.

eterm 4y ago
I think you misunderstood my comment, at no point did I suggest taking "cheap shots" at anyone, and indeed my advice was to focus on "the rest of the package" as you suggest.