[quote Shelddd]@CastawayQueen I disagree completely. Not sure what your background is.. that might be why we have a different viewpoint. I have a masters in data science, it was a conversion course but I have a technical bachelors, but 90% of the people doing the masters didn't have a technical bachelor's degree. Vast majority have data science jobs now and got them fairly quickly after graduating.
Cloud computing is easy. Infrastructure is easy. Service delivery is easy. Support is easy.
Programming is very hard. Data science is harder than the first 4 i mentioned but not as difficult as programming and it's a brand new field (commercially at least...) That is experiencing crazy growth.
Tableau is not data science... It's a data visualization product. It's considered part of business intelligence which is a different vertical than data science. Data science is basically programming + statistics.
I wasn't suggesting all of those things but rather giving different options.[/quote]
I have the same background as you - started in support and moved into programming. My degree was not technical. I have several cloud computing qualifications and lots of programming/infrastructure experience under my belt. I have also been instrumental in bringing people from diverse backgrounds into the field, most of whom are not only still at it but have been promoted. Sometimes over people with ' the right things' like computer science degrees.
A tech support person (while they know how computers etc work) does not need any additional insight apart from how to troubleshoot and fix things. They have set steps that say if X - do Y. If the steps don't work they need to figure out why but it's all short term thinking with the only goal being to solve the problem at hand.
A programmer/infrastructure engineer requires an additional level of insight. Because they are creating something for the long term they need to know several methods to do something, the pros and cons, short vs long-term tradeoffs. That is why it is difficult.
There are people who think of themselves as programmers - but they are actually tech support people. Yes they write code - but it's only simple scripts to achieve a single task. Not a whole piece of software that will continuously be developed with other people, do several things, need improvement and maintainance, need to meet security standards, etc.
Now the reason that programming is easier to break into is because there are already a lot of bootcamps etc. Again this is very restricted to web development. 99% of bootcamps train people to be web developers because a) most computer science degrees teach things like Java and C, focus on theoretical principles and backend developing, leading to a talent shortage and b) Web development can be easily templated and is easier to pick up.
From this base people pivot into other things (such as infrastructure). But you won't find bootcamps for being an 'infrastructure developer' because there isn't quite a linear path. Most people if they don't start in tech support or direct infra engineers are programmers. Alice Goldfuss is a good example.
So if someone is considering programming the top 3 ways are:
- Get into a bootcamp/apprenticeship structured programme that gives you a job at the end of it.
- Get into a tech support role and then work your way into development. Google has free tech support qualifications.
- Get into an unrelated role. Service delivery, service management, project management are all related but not quite.
And if someone only wanted 'a' good job and wasn't really interested in coding I would advise going for 3) Maybe do a couple of Python courses to show your interest in tech, but focus your effort on your people skills etc. The more things are automated the more these roles will expand. The building and maintenance of software is in fact 10% technical and 90% planning , communication and stakeholder management. The whole 'learn to code' is overblown.
But under none of these circumstances would I advise taking cloud qualifications on their own because they'll not only confuse you more, they also won't be worth very much. This happened in one of my orgs where graduates with no background at all were forced into taking the AWS courses. Lots of effort to pass, but when sent into the teams they weren't much use compared to graduates who didn't have the qualification but had infrastructure knowledge.