We are looking for an experienced frontend software engineer to fill a key role revamping our student-facing code review and mentorship platforms. You'll be joining a US distributed team of 7 engineers who have been working to democratize education together for a few years. You will write React / Redux (and read some older Angular), live and breathe GraphQL in a BFF architecture, and help us explore the Apollo ecosystem.
Apply here: https://boards.greenhouse.io/udacity/jobs/4290774002
Tech is wildly lucrative, is in current demand, and is not physical labor. That reduces the barrier to entry to anybody who has a laptop and an Internet connection. Honestly how many people would be so eager to learn to code if you dropped down the average tech salary to 45,000 (matching other professions)? I think far less: people seem to learn to want to code to ride the high-pay wave, not for the actual love of code.
Again, let's compare to music. Anybody can go to a guitar store and buy a 200$ keyboard. But if I took a 14-week class and afterwards had the aught to call myself a "Music Ninja Rockstar" or some other such nonsense, and start applying to orchestras and bands, I would be called crazy.
Software has eaten the world, and it's here to stay. Increasing the general software literacy is no more different than saying we should teach everybody how to read (and a good thing). However, throwing each person in a bootcamp telling them "coding is wonderful! you can master it in 5 seconds and make 200k a year!" is no different than holding a similar bootcamp for any other vocation and then wondering why the average plumber can't actually fix your house, but can only use a plunger. I sincerely hope this trend stops. This mindset is broken, and the paradigm is highly unsustainable. Where will we be in 20 years?
I am not sure if you read the article? The point is that age isn't a barrier but that becoming a software engineer is a lot harder than just going to a bootcamp and expecting a job to appear. This is about spending a year trying to find a job.
I have zero problem being compared to a plumber with a plunger! If something breaks in the middle of the night, I get paged, grab my mop and my tools, and fix it.
Why does it matter if the average plumber "can't fix your house"?
The pay is good because of supply and demand but I really do not know programmers who decided to get into it for money.
Never was truly a developer, and decided I wanted to accept a job as one. I've programmed in the past, how hard can it be?
Wow, it's been enlightening. Really hard. I thought it would be straight forward since I've used scripted quite a bit in perl in my past, but being a developer is much more than writing a few scripts to automate a task.
I'm a few months in now, and I am still slower than all my colleagues by quite a bit, and the main language I'm working in has changed already, moved from Python to Go.
Even right now, I'm stuck on an issue around pointers and data structures that feels like it should be easy, and I'm just not getting it.
All you can do is keep confidence up, and keep at it. Immersing in it, and knowing that irrational levels of effort will lead to results.
I thought it would be easier though :)
I couldn't agree more that it is tough going when you realize a challenge is more than you expected. That plus impostor syndrome is what caused me to quit on my first try.
We are moving a lot of things from Python to Go at the moment and it has been great.
Certainly, I think Deep Work require full concentration. So when in the mode of learning, I find keeping focus instead of going to a website to read news, or checking e-mail/messages to be incredibly important in maximizing the incremental process of grasping concepts.
That being said, whereas the author seems to prefer taking a few months to go deep into it, I prefer to immerse myself over a long period of time by learning and practicing a few hours per day (just like an instrument), letting my mind stew in the knowledge during diffuse thinking periods, and then come back to it the next day.
Frontend engineer on my team: https://boards.greenhouse.io/udacity/jobs/4320541002
All open engineering positions: https://www.udacity.com/jobs#engineering-it?location=all