Voxera762920dWeb development has a low entry bar since so many companies want a page but know very little about it and want to pay as little as possible.
This means that with a few good templates you can wip upa page pretty easy.
But lately with wix and orher sites I guess the really easy jobs might be less common as it requires literally no real knowledge to make a super simple page.
Even if web design is not your thing, many larger sites need backend developers to that rarely poke in html.
Also, learn some database along with one or two orm frameworks and you should be above most applicants I have seen fresh from school.
The major problem outside of web dev is experience.
Web dev for really small companies usually do mot requirer any experience, just a decent own page and possibly some examples.
But for most other they will look at experience to.
dan-pud68920dServerless. It requires you to know a public clould platform and be able to put applications together from their services with very little code. A common pattern on AWS for a web application is S3 to host the 'web' code, then API Gateway with Lambda and Dynamo.
I would suggest picking a cloud platform and then learning it inside out. AWS has a very generous free tier where you can experiment for free.
There's a right process and a wrong process to being a part of this industry. The right way is:
1. Learn the principles of engineering, comp sci, math surrounding a domain
2. Apply them to a discipline (web, embedded, service, etc etc)
3. goto 1
As others have confirmed, web has a low barrier to entry. Lots of bodies claiming knowledge, lots of sources churning out people with rote knowledge and low investment. They skip the understanding and go straight to the doing. That's fine right up until you encounter a challenge that requires an engineering perspective. At that point all the packages in the world won't save you.
Just like code has a smell, so too does opportunity. If something is regarded as "easy" it's often more because people don't want to pay for the work than the work is trivial. There's not really a sweet spot where you're guaranteed good pay, the intersection of demand and value shifts. Where there is pain, there is money.
Tl;Dr more pain = hazard pay. Want a big paycheck? Find work where your code relieves pain. If you don't know what value you provide, don't be surprised when you're made redundant.
C0D45677920dWebdev doesn't guarantee a good paycheck.
Small to medium business, they just want a cheap page and walk away - that's the freelancers game, it's just pimping out templates for $5.
Large to enterprise want e-commerce, crm's, erp's, api's and the list goes on.
This end of the bar requires experience and a decent understanding of comp sci.
it's a tough journey if you don't have the fundamentals of a degree behind you. I speak from experience.
If your journey into this industry is for the $$$, you will have a hard time anyway. it's a never ending journey of teaching yourself how to do the next thing, unless your that $5 ho from earlier.
@fast-nop, any advice?
Fast-Nop2705020d@C0D4 I'd stay away from domains where there's no real money on the line. If Facebook has a hiccup, nobody cares. That's why they invented "move fast and break things". The more shit you can throw against the wall in a given time frame, the higher the odds that something will stick.
Also avoid the whole game domain. Employers demand insane working shifts for ridiculously little money because they exploit devs thinking the job is "cool".
Anything consumer related sucks. Consumers will happily fudge around with stupid shit and tinker around if they can save $10 on a $100 item. Its also a "shit against the wall" approach.
Industrial customers are different. The production line is down one day? That's a price tag in the million dollar range. Shit has to work, and what's more, it has to be made sure before delivery. Even more so in regulated areas like medical, automotive, avionics. That's often more system design than coding, but it pays nicely.
Fast-Nop2705020d@WildPotato Well as I said, e.g. medical, automotive, avionics. Outside of that, industrial automation is interesting, and also anything related to predictive maintenance which is a somewhat hot topic.
The latter means you don't want to maintain too often because downtime is expensive, but you also don't want shit to break and cause unplanned and even longer downtimes.
So you have tons of sensors in your machinery, and the whole thing is self-diagnosing so that it can tell in advance "check this thing here within a month". Machine learning to spot patterns should be an interesting approach.
Also, industrial quality control with stuff like highly complex PCB testers right after production. Or using image processing e.g. for stuff like bread or tile factories.
dan-pud68920d@melezorus34 not really. If you want to learn serverless properly you should look at one of the big three, AWS, Azure, or GCP. AWS is the public cloud leader, Azure is catching up, Google is way behind.
The Serverless framework is really good too and agnostic of provider. However to know concepts better I would suggest not using the framework and wiring things up yourself. If you can bring up a web application (Django, spring, whatever) and compare the two approaches
LLAMS331319dCyber Security. Everybody needs it and always will. Its a cool domain and if you know your stuff companies will want you.
Also with regard to the current pandemic and likely recession to follow, cyber sec will still be a booming business because customers wont want to cut it from their budget.