I am an aspiring web developer. I have been self learning for around six months and still have not found a solid path to follow. Six months sounds like a lot but realistically it has been a few solid weeks of learning since it is a side hobby that I hope will turn into my career.
Is the Web Dev job market in a good enough state that I should risk more time and money?
Thanks for any advice…
If you are thinking along the lines of the first example, eg. the "I know html and css, I can build a website with pictures and operating hours for a mom and pop shop" developer, this market is shrinking with platforms like wix and squarespace where regular people can build these sites and maintain them easily and for cheap. Not to say you can't still make a living doing this, but it is something to be aware of if it is the route that you choose to take.
If you are thinking more about the second example, yes, there is a high demand (and rapidly growing market) for this kind of developer at startups and fortune 500s and everything in between.
Overall, the answer is yes, web development is still a growing field and it is absolutely a viable career choice, but it is important to keep learning and be aware of the market and adjust accordingly
The big question is if the internet and its primary portals, the desktop browser and the smartphone, will reach the end of their tether. The only thing I could see replacing it is neurotechnology of some sort, and that seems so far off and so difficult to commercialize that it's not something web developers need to worry about any time soon. Or perhaps quantum computing becomes commercially viable and simply shoves digital computing aside, negating the need for those skills completely.
Another alternative is that the web radically changes unforeseeably and new practices instantly antiquate everything people are learning now, which is a more frustrating and realistic possibility and also something that is bound to happen. Given how difficult it can be for many people to learn these skills, and given how much knowledge one must integrate to be a productive developer, this is an upsetting potentiality and one that is bound to happen eventually.
Not every field carries these risks. Law practice isn't going to change fundamentally in the coming decades. And some aspects of coding can be exhausting and demoralizing to learn. Past generations of coders have had their skill sets rendered null and void and it will probably happen again at some point to this generation.
>Amazon tier complexity
I'd go even further and say that Amazon-level things aren't web apps to, that's a different level of web resources. It is one thing to write fairy complex web app with auth, log in info, security etc, building enterprise level system is a different thing.
I'm also thinking that how people code could change drastically, but even so, that's less of a problem. Because the rules and logic of any programming language boil down to fundamental computer science principles which should remain constant despite the interface you're using to code, whether it's a keyboard and monitor or some kind of visual drag and drop thing or whatever someone comes up with.
You still have to describe to the automaton what you want it to do -- and in doing that, you're programming.
Modern languages are all "automated programming" already -- you aren't writing machine code, you're describing to the automation system what you want, and then it generates the machine code for you.
Faster machines, but with each new language, you still have the baggage of design/code/compile/test/debug/refactor and the library/dependency hell that plagues things like oh, say Node.js with NPM, maven with Java, make with C/C++ etc. etc.
Then there is the flood of new "UI hotness libraries" in the JavaScript space alone. Pick one. wait 6 months and see what else is now the new hotness or if your current one has changed with a new major version release (Angular?).
There should be more folks like Bret Victor working with language teams in the FANG(+MS) companies to drive some further breakthroughs in reducing cognitive load and tool/library dependency complexities.
Where are this generation's Alan Kay and Jean-Marie Hullot types, pushing the envelope on software development environments?
All coding is itself the act of automating something. I don't think there is a risk to developers as there is always more to automate. We use products that automate our own programming tasks to create more code to automate yet more things.
So regardless of market fluctuations, server-side development will always be in demand, and server-side dev is a subset of "web development".
So yes, definitely, web development is a worthwhile field to go into.
Web development could be solving someone's essential business problem or totally non-essential for someone else.
The key is to find the customer for whom whatever you're doing will solve essential business problem.
Quite often web development is exactly what customer needs but he won't call it this way. He won't use this wording. He won't look for web developer. He won't pay for web developer.
But if you approach customer by speaking customer's language and showing customer how you can solve his problem - the result could be way more win-win and productive.
You won't hire an expert in "connecting wooden boards with nails" but you'll more likely to hire an expert in "building houses" to build your own house.
That's an idea.
You'd then try to work on projects where your construction specialty is seen to be more valuable than not, that goes to your comment. But that's an entirety different question than whether a specialty should be pursued, and if so what specialty.
E.g. in this case whether it's still a good move for a new developer to start out his career by focusing on web dev v.s. say native mobile dev, or mainframe development or whatever.
What I do think is that 'Web Dev' might be a viable first step within a career. It's a good way to get yourself into a spot where you're exposed to signifiant problems, and if you're lucky, it will also give you exposure to people that can help you along, as you develop your career. (But it's important to be intentional about both.)
At the very least, that's how I answer then question when asked in person... focus on the specific tech as a tool in the short-term, and then focus on effectively solving problems people care about. It's better for them, and most likely, better for your own personal career development.
(Edit: Some of this may just be my own perspective... My professional work has included everything ranging from small scale embedded programming to large scale clustered web apps and platform development. I'm grateful for never having thought of myself as a 'web dev', even though it is something I'm capable of.)
I love this kind of work. Writing learning software for airplane systems. Accounting and auditing systems for fortune 100. Kiosk+POS for water distribution platforms. Security software. Election services software... It's been an amazing 24 years, and I have absolutely every intention to keep learning/working until I die.
I find that a lot of people just think that "web dev" stops at the browser.
Tangent: “general carpentry” is not a superset of plumbing/tiling/plastering. Carpentry is its own skill related to working with wood and similar products. Maybe you meant general contracting? Although that’s still not actually a superset and you won’t find that most general contractors are licensed for plumbing and electric work.
Edit: To summarize, not every web developer needs to be an entrepreneur.
I often wonder at the whole "gotta be a contractor" mentality. I understand there's more money there, but I think that there's a huge value in learning to be a team player where you're building something you are actually invested in, if even for only a 1-2 year period. As a contractor, the skills you build and lessons you learn are important, but they aren't as concrete as living and dying with a particular team and a particular solution for an extended period. In addition, I feel like you are more likely to get vital mentorship at the critical early part of your career as a member of the team instead of a replaceable contractor cog.
This is spot on, whether you are free-lancing or working as an employee in a big organization.
More generally, software development benefits from a large flow of money precisely because, whether directly or indirectly, it enables businesses to accomplish things in a {faster, more efficient, cheaper} way. When career planning, always remember where the money comes.
Interacting with an end-user is not a "solved problem" that has been commoditized. There are still a lot of human touch, optimizations, edge cases and performance issues that are actively being worked on and have not been formalized and standardized in ubiquitous ways for all industries. Sure framework XYZ may get you 80% there but then there are specific UX issues that you will have to delve in, and that's where the real fun begins.
You’ll likely hear a lot of people talking about how the market for juniors is flooded. That is partially true, but it’s flooded with people who cannot code. If you can actually be a productive employee I literally know 100 companies that will hire you today. As a self-taught engineer you have to convince them of that, which mostly means a solid portfolio, but there is insane demand. And if you get even one year of experience you won’t believe how many opportunities open up.
There are individual companies whose annual growth in engineer hiring is greater than the total number of CS and bootcamp grads combined.
This just isn’t true.
The industry has become insanely competitive for anyone but the top level seniors who are above the whiteboard/coderpad interview. I’ve been on the market for 4 months now without so much as an in-person interview. It’s absolutely brutal. And that’s with 3 years experience + solid references.
For every job posting now there are a hundred freshly minted CS grads applying who can pass LeetCode exams in their sleep. It seems companies are far more interested in these people than those with self taught skills and practical experience.
Get off the job boards and use services like Vettery and Hired, do outreach on LinkedIn with recruiters and startup CTOs/VP Engineering/Engineering Leads, go to more popular tech meetups consistently and network. Every job I've gotten has been through this.
Yes it is (but you need to be overall personable and have good communication skills). After 1 year at a small dev shop I started with 0 years of experience, I got an offer at a big company you've heard of (not FAANG but public) for double. I didn't take it because I got bad vibes from the management but it was great to know I could. I say this not to brag that I'm brilliant because I am decidedly NOT brilliant - there have always been better coders than me everywhere I've worked since.
However, I had some PM experience before learning development which helped my "business" bona-fides. If you are 19 going from taco bell to a bootcamp I imagine proving that you can fit into an actual business culture is more important to getting you a job than coding ability (which is the min bar).
Truthfully, if you have 3 years exp with solid references, you should have recruiters knocking down your door with (mostly) bad offers of underpaying shops. There's no reason you shouldn't unless theres big red flags on your resume.
During my last round of looking for a job I never applied to a single company, I let all of the recruiters come to me. In five months, I had a total of five interviews and three offers.
I have an active github portfolio which shows a professional picture of myself and I have React skills which might set me apart (React is very hot right now, won't be like that for much longer though as the market is starting to saturate), but aside from that I'm self taught and have about 3 years of professional experience, ten if you include personal/self-taught experience.
I had to go through some BS phone screens though, it was to the point where I had to buy books specifically on C# design patterns and architecture just to pass them, I had managers grilling me on some pretty esoteric aspects of the language, but it was worth it. (I have ten years of self-taught .NET development experience)
I am seeing it as well. And am recommending Lambda School to just about everyone who asks ;)
The main problem I see is the steep learning curve. The intro lessons are facile enough. Anyone can setup VS Code, and install an App Engine SDK. But by the time they get to modules 3-4 ("designing the data schema"). They are ready to throw in the towel.
At some point, a student requires one-to-one mentoring and repeatable reinforcement. Like learning a second language or playing the piano.
Also check out this nice write-up in Dealbook today on Lambda's model:
https://www.nytimes.com/2019/01/08/business/dealbook/educati...
It’s entirely possible to be a self-taught pianist. It’s also entirely possible to learn a second language without ever speaking to someone else in that language. What you can’t realistically do is become conversational, because you cannot practice that skill in isolation.
Similarly, it’s entirely possible to learn to develop software independently. You can learn languages and SQL normalization and good design all by yourself. You might learn faster with a teacher, but you can do it independently. You cannot learn to work well with others (properly subdividing designs, dependency ordering, giving good feedback, etc) in isolation, but honestly these are the things you generally learn on the job, because schools also suck at teaching these things.
Self-drive is probably 50% of success as a software developer. 35% is knowing what some of the options are (prescriptive or otherwise) and the last 15% is aptitude. You can be a solid B level developer without any aptitude, but it requires more drive. YMMV.
Different people have different personalities. When I was 4yo, I broke the training wheels off my bicycle and figured it out myself because it felt like they were more in the way trying to ride. In my early career, I spent time removing obstacles and learning literally everything I could. I am self-taught, not higher education at all. Other people need more hand holding. Once you start working, you need to be able to jump into the deep end and at least tread water.
Over the past decades, many developers are self taught. And online communities and resources have only improved over time.
I've just graduated (did 3 IT study programs in total -- 6 years of studying, overkill yes, I didn't have any good career advise via my friends, family or uni).
Do you help people from the EU to work in the US? If so, then I'd really consider applying to your school since I am noticing that I can't get there myself and US companies aren't noticing me.
I am also pretty open to learn basics again since right now algorithms and data structures has been years away. And for advanced topics I only needed that knowledge on a surface level.
I'm in the US and have looked into moving overseas in the past. Good luck, I wish I had contacts that could help/share, I just don't.
Also, I noticed on the website that when I check a course it says that ISA option is available for EU citizens as well, but your FAQ says that it is for US only.
Do you have some salary statistics (maybe broken down by market) for your grads?
We need to do a better job of breaking it down geographically, but it’s what you’d expect. $100k+ in SFBA, big salaries in cities, lower salaries (but actually higher standard of living) in smaller cities.
If what you have in mind is feeding data into TensorFlow or PyTorch, and tuning parameters to get some magic out the other end, I don't think there's as much of a market (there are many juniors looking for work from bootcamp programs), and you risk yet another "AI Winter" backlash making companies go sour on these sorts of approaches.
I think you could also easily getting a job as a master of a particular analytics tool, like MixPanel or Google Analytics. But I'm not sure how timeless this will be: in my experience sooner rather than later you'll want deeper and more customized tools and run into the limitations of simple event-based analytics services.
In the end, you will never be able to stop and rest on your laurels, as you will be unable to find work if you do. Constantly learn, constantly grow, and when starting out, go above and beyond any assigned work.
What companies actually need (or should need, if they're solving some problem), I'd argue, is people who are capable of solving domain problems in structured ways. This has everything to do with logic and almost nothing to do with 'programming' or 'coding' in the sense that I believe most people understand those words today. This is a skill that has very little to do with knowing xyz language, framework, or even paradigmatic abstraction and everything to do with having familiarity or mastery of both recent and ancient mathematical and logical principles (algorithms, data structures, computability theory, set theory, lambda calculus, etc.) Of course, the way we actualize these skills is through programming languages, but programming languages themselves are not the important part (at a high level).
I think a lot of hopeful and ambitious autodidacts unfortunately miss this, as the bulk of (I'd wager) free resources for learning 'how to program' do not do an adequate job of conveying the fact that programming is ultimately the application and encoding of abstract principles into a concrete solution for a particular problem domain. This effectively leads to a pool of job-seekers that are well versed in the latest lower order abstractions (as these are encoded in programming languages, e.g. iterators or a particular framework or paradigm) and not higher order abstractions (e.g. what makes a particular construct iterable, what structural properties suffice to assert 'iterability' of a set or structure, or e.g. how should one compare paradigms and select between paradigms for a particular problem).
At the end of the day, a lot of this doesn't matter. Most people in the programming field do just fine without diving too deeply into the heart of computability or information theory (some demanding positions in the field, of course, are exceptions to this). But I think if we want to produce better 'coders' an important step lies in disambiguating logical/mathematical/programmatic problem solving from the concrete practice of 'programming' (using a particular language with particular resources, paradigm support etc.) From what I can tell, University CS programs do an effective job at this (e.g. classes on algorithms and data structures and architecture are all distinct) but many free resources, I feel, do not. This may be the culprit in the production of that bevy of people who 'cannot code'--they can program, but they can't problem solve computationally or model problems well (I can't do this myself). And I think it leads to the following common realizations on a.) b.) and c.):
a.) Companies need people who can determine and analyze sets of potential structured/logical/computational solutions to problems. b.) Companies think they need people who are good at using xyz tool in particular because xyz tool/language/paradigm etc. is popular, new, generally thought to be useful, etc. c.) Prospective developers think they must learn xyz tool/language/paradigm/framework because companies seem to want that. They do so, never exploring the fundamentals behind xyz tool/language/framework and move on to learning the next xyz ././. next year to stay relevant.
The result is that many companies are bound to the solutions, abstractions, patterns etc. that xyz tool/language/whatever supports and thus they're actually quite okay hiring people who cannot really 'code'.
In truth you probably only need a few smarty-pants engineers behind the important stuff. The majority of folks can enter the workforce only having a basic knowledge. The ones that are curious enough will start to dig into the general/abstract principles behind computation and eventually learn enough to fill the shoes of the big boys. Most entry level programmers can get by just fine with a thirst for further knowledge, the ability to notice, adapt to, and use patterns that are already in place, and some very basic analytical skills. Of course, many hiring practices don't necessarily reflect this, which leads to the classic condition of "in the interview I had to show that I could do abcd with data structure xyz and implement algorithm hjk to solve problem p in t time but on my day job I just write against apis."
Disclaimer: I am not a programmer or software engineer. This is just my sense of the state of affairs as a curious outsider (I do work in the software field, but my job role is different).
One of my coworkers has a Math/CS degree and I feel like he's light-years ahead of me when it comes to solving algorithms, to address just one facet of your comment. He can see the underlying problem/solution at a much deeper level. At the same time, I think that teaching the deep theory first would have been too abstract to me; it makes more sense now that I have some practical experience and have encountered real-world problems that need to be solved.
I no longer believe this.
I think “people who cannot code” is a myth perpetuated by those who gain something out of it. People who’s business or job is to filter candidates, people who’s business is to sell their own “improved” version of training, people in need of an ego boost and actually, mainly by people who just repeat it cause they heard it somewhere. I’m off that train.
But, then again, I just might be old and wrong.
I literally know 100 companies that will hire you today. As a self-taught engineer you have to convince them of that, which mostly means a solid portfolio, but there is insane demand.
I’d like to test that.
That’s my homesite: https://www.ronilan.com
I’m in the market.
Thanks,
Ron
My experience has also been that most raw junior candidates need significant handholding to implement anything into a typical production system at first, and that the learning curve from there varies greatly.
What do you think?
It's an unknown unknown, a lot of programmers will simply not know you can use quick and dirty scripts to process data if you're only going to do it once.
I work mainly in .Net and the similar problem I see is devs who don't even know that console apps exist, let alone how to make them, which simplifies prototyping new code immensely.
Sure it is taught. It's taught by some people ( including me - plug here for my Linux and Python courses, with testimonials: https://jugad2.blogspot.com/p/training.html ) in their Unix / Linux courses, as examples of how to really put the classic (and oft-quoted) Unix philosopy + command-line tools + shell scripting to good use, synergistically ("write small tools to do one job each, well, and connect them by pipelines and I/O redirection, etc. etc.").
It's not even rocket science; bread-and-butter EDP/IT folks (programmers and even operators) (not just clued-in software engineers in product companies) have been using such scripts for decades, routinely, without thinking they are doing anything great or out of the ordinary. (And similarly for other OSs, I'm sure, such as Rexx on some platforms. Not sure what was used on Windows before PowerShell, maybe Perl and/or one of the Unix toolkit clones like MKS Toolkit or Cygwin or UWin - apart from clunky batch file language and DOS/Windows command-line commands).
It's just that it is not so well known nowadays among the (often mainly JS-using) generation, who even write CLI apps in Node.
>It's an unknown unknown, a lot of programmers will simply not know you can use quick and dirty scripts to process data if you're only going to do it once.
It's their loss (and that of the industry), comes from not trying to learn about prior art.
There's even a name for it: NIH syndrome [1], and heck, even that is not new :) Dates from early IBM days or earlier ...
The focus is on pumping out Java or C++ folks who never were given assignments using said tools and therefore never knew or learned them. Python is the new Perl, not sure what the new awk is.
Red, said sed.
"The market is flooded with people who cannot code, therefore it's easy to find a job as a junior engineer"
The market could in fact be flooded with people who cannot code (I don't know for sure). Assuming that's true, that doesn't necessarily mean it's easy to get a job as a junior dev (speaking from someone on the interviewing side).
Even though the last job ended months ago, I'm still trying to unconvince myself that everyone in this world is stupid and incompetent, because that was what it felt like.
You should try interviewing "software engineers" that claim to have 10 years of experience architecting and coding in various languages and cannot write a function that doubles the value of each number in an array.
The easiest questions I've been asked are unimaginative but straightforward things (build a binary tree, print inorder, find all permutations of a string, code a hash map).
There's also a particularly pernicious trend toward asking for on-line assessments or homework assignments, things that save the hiring company time but put an even greater time burden on the applicant.
I'd say "cracking the coding interview" is a good reflection of the kinds of questions you need to be prepared to answer in an interview, and they are miles away from doubling the value of each integer in an array.
I think this is why there's such a disconnect between us. You do see self-described software engineers with 10 years of experience who can't do fizzbuzz, I really do believe you. But we (the applicants) never see this, instead we see a vastly higher standard applied. Which would be fine if the companies acknowledged that they are having trouble hiring because they're extremely picky. But instead, we hear people claiming that there's a "shortage" and that they can't hire because all these supposedly senior people can't code fizz buzz.
Exactly this. I'm mid-level, trying to switch jobs. Several front-end javascript positions I interviewed for asked me anything from pretty tough algorithms to "how does Angular do namespacing" to object-oriented questions relating to Java to how to style a page and add event listeners to it without ability to reference the docs, etc.
The questions per se are not undoable, but the the sheer magnitude of the corpus they can ask questions from is what's so difficult. I accept this and try to cover as much as I can in self-study and outside courses, so I can better in future interviews. But it is a substantial burden timewise, and seems to be of diminishing marginal utility regarding actual, on-the-job performance, which is pretty annoying. Oh yeah, and then they reveal that they want to pay me $75k per year for a mid-senior position, in California. I know people who make that starting out of college as Account Managers for bigger CPG (consumer packaged goods) or pharma companies, with a company car and cell phone. (Granted, I think those jobs would be boring and also at-risk over the long-term, but the time spent/compensation difference seems out of whack.)
If there really were a shortage, companies would check for fundamentals but relax their standards and offer more on-the-job training for candidates. And wages would be significantly higher! Should get rid of H1Bs as a start, and see if that helps.
It's also not my point at all.
The comment I was responding to was advocating that there is a myth surrounding the flood of people who don't know how to code. This is not a myth.
Doubling an array of integers is one of the easiest questions I can possibly think of, and use it to build interviewee confidence as a warm-up before diving into pragmatic questions related to the job.
Unfortunately, there is a not insignificant number of candidates who claim experience and yet are unable to write `.map(x => x * 2)` or use a for loop.
This assertion is often mis-used (a slight of hand to resolve the question of why companies reject so many candidates yet claim that anyone competent will find "100 companies that will hire you today".)
However, you were not making that second assertion, you were insisting that something that is real is not a myth, fair enough.
This other is title inflation where someone at junior-mid level has a senior title after 2-3 years of experience. It's all over the map. For every good developer, I've seen 2-3 bad developers. For every 10 good developers, you might get 1 great developer. For every 2 great developers, 1 has a personality that doesn't work well with others.
It's a challenge to build a team where you need to balance ability, room for growth with need. I also agree that the hiring practices outlined in "cracking the coding interview" are excessive for most environments. Most line of business applications will use tooling that abstracts some of the more difficult challenges. Cloud environments offer services that take care of many of the rest. In reality, there's more need for someone to have an understanding of when you might use a given SQL variant, Mongo or Cassandra (or any number of others), vs even thinking of creating your own systems.
In general, for "senior" javascript developers, I ask a single question. Something that's in every JS book from beginning to advanced that I've ever seen. And less than one in 10 give a complete answer, and less than half get it half right.
I like to ask them to explain either the concept of closures in javascript, or how `this` works.
I don't even need them to know the word closure, knowing why you can't reference a variable written inside another function, the difference between var and let, or what does bind/apply do.
false, null, undefined, NaN, "" (empty string), 0
Bonus: An object with a toString() method that returns one of the above won't evaluate directly, but will roughly equal (foo == false).
sometimes I'll ask for a function that returns input as a whole number or null, if it's a string, attempt to parse base 10, return null if invalid, return null if the input isn't already a number or a string. 0 is usually what will trip people up.
Not to mention in general Javascript does some pretty not intuitive things with objects: https://archive.org/details/wat_destroyallsoftware
It's (knowledge of falsy values) been a very representative indicator of how well they know the language itself. It's not an indicator of understanding software as a whole, or a given UI framework or library.
You shouldn't extrapolate your own experience into "never" or "always". I have twice your experience, and I've had insultingly simple questions like this. Amazon asked me to do fizzbuzz, for crying out loud.
When I started my current job I remember the announcement said something like 15 years experience and I thought "I've been doing lots of things for a long time, but I don't feel like I have 15 years experience in any of them" at least no the same way someone in a more stable domain might...
I would look at a resume and think "wow this person is gonna be amazing". And then I would ask them very very basic questions, and they would get them wrong.
I still don't know what to make of it, because it doesn't make any sense to me.
I'd also add that "junior" can mean very different things for different companies. A junior engineer at Google could very well be "mid level" or even "senior" at a different company. Maybe even a CTO at a startup.
The industry is still relatively new and I think we're still in the early stages of grappling with how to best match programming expertise with company needs.
I don't know exactly how common either is, but I've run into both categories multiple times doing freelance work.
Most people seemed to have workable skill levels. A pretty good portion of people seemed to still be in the novelty phase of programming where they would be slightly too excited and surprised at themself, and perhaps slightly unconfident, in answering a fairly basic question correctly.
Me neither, in the real world, but I have seen a couple of excruciating mock interview videos where the "candidate" was unable to complete the fizzbuzz task. I think this might be a result of people thinking that learning to be a developer involves following along with video tutorials on Udemy, and that as soon as some threshold is reached, they should be ready to look for work.
Even after I explained what an odd number was they couldn’t do it.
No, it does not. Learning new skill from scratch takes time. You're trying to master 2 new, orthogonal, in some sense contradictory skills: web development, and self-promotion (to find your place in "the job market"). Take a deep breath.
There's a difference, and not insignificant, between "learning everything for CS degree" vs "learning what you need to get hired as a web dev".
But I'll agree that 6 months is not that much time in the "learn new career skills and find a job" timeline. I spent around 18 months of nights/weekend practice and learning, followed by 3 months of interview prep before I found a job and that was with a big spoonful of luck.
To OP - this is a marathon, not a sprint. Get used to learning things on your own, you will be doing it for the rest of your career if you make the switch.
Cannot second this enough. As a developer, there will always be new tools and technology. More room to grow into adjacent development. And more line of business knowledge to gain. I can't think of any other field, that has more lifetime learning involved in it.
Granted, he's very smart and basically coded all day for 6 months, but I'd say it is possible for a motivated individual.
Which isn't to say the non-programming stuff in my degree was irrelevant, but you don't need to spend 4 years full time studying to learn relevant skills for a junior web developer job, and you could easily learn them in less time outside of a degree.
I can see two viable, yet very different definitions:
1. Frontend web engineer: Versed in HTML, CSS, modern Javascript libraries such as React, Vue, Angular. This is a programming role first and foremost, better paying than #2, and what I would suggest focusing on.
2. "Classic web developer": Versed in HTML, CSS and just enough JS/jQuery. Knows the inside out of some CMS such as Wordpress. Not recommended, yet there are a TON of small companies and clients that just need a small website or ecommerce site. A friend of mine fits this role, I wouldn't define him a programmer by any stretch of the word, yet makes a living adapting Wordpress or Magento into functional websites.
Magento is a fairly complex platform too. It uses lots of very formal software engineering paradigms joined together in a well thought out framework. I would consider it a bit more traditional programming than Vue or React, and if I had a general programming role to fill I would sooner hire a Magento only backend dev than a React only dev. React/Vue are very specialized frontend tools and working with themm doesn't translate all that well to general programming.
3. Full-stack web developer.
4. Back-end web developer.
3. HTML, React/Vue (and related libraries like redux/vuex), CSS, SCSS, JS (including ES6+), JSON, REST, Node.js, Webpack, Babel, Python/Java/.Net/PHP/etc., SQL, Postgres/MySQL/etc. DDL/DML, Git/SVN/etc., Apache/NGINX/etc., HTTP/HTTPS, Let's Encrypt, Linux related technologies (SSH, BASH, etc.), etc.
As someone who's neither I rather disagree.
But no one would ever hire me as a "front end developer" or a "full stack developer" without knowing one.
If you're advocating for traditional server-rendered websites (perhaps with very small bits of interactivity via JS), then you're #3: A backend developer.
If you're suggesting building a complex client-side app, just without a framework, then I reckon that this is just a variant of #1. But you'd better be a very experienced developer, or your code is going to be a complete mess. This isn't really a viable path for a new developer just starting out.
In terms of what is being done, I'm far more judicious with removing unnecessary libraries. I've followed up other developers removing any number of modules in favor of hand-crafting from baseline modules. Since it's JSS it includes semi-dynamic styling that is based on async loaded modules. ex: if you don't go onto a chart/graph page, you don't get those modules.
It really depends on your tooling, knowledge and what your needs are. IMHO it's far better than typical jquery + bootstrap + bootstrap extensions that many of those who look down on client-side frameworks lean towards.
It's all patchwork on top of JavaScript, though. Another programming language like Elm, or something that compiles to WebAssembly, may be another option to consider.
It is entirely possible to dislike React for being React, rather than for the fact that it's not minimalism. I have to work with React, and it's a constant source of pain for me.
As other people have noted, classifying "web developer" as "frontend web developer" is a bit restrictive.
You're not going to find this kind of developer in a run-of-the-mill WordPress shop. You probably won't find them in the latest startup that is all on the serverless bandwagon, either. But there are quite a few of backend positions in larger organizations where you might coincidentally find better pay and job security as well. Bonus points if you're well versed in security, or know how to talk to the database guys over there.
there is a ton of room for number two still. Maybe not in the heart of Silicon Valley, but other major cities—sure. There are a ton of businesses operating using WordPress as their primary platform because it's relatively easy for non-technical or semi-technical users to wrap their heads around.
Here in Toronto there are a lot of thriving WordPress/PHP-stack shops that service those businesses so that they don't have to hire their own web team. I would never want to work with one because I personally really don't like working with that stuff. 100-foot pole sort of situation— but they're there, and they pay okay for the local market.
Once you've honed your skills, focus on the more complex, bespoke projects. Become good at delivering on time and try to find clients that wish to invest in tech to improve their business further. They will generally appreciate your work more and will not hesitate to pay you good money if you're genuinely adding to their bottom line.
This, THIS! Many web devs do a bit of this starting out and that's fine... just don't try to make it into something more, not only because it's worthless and the clients will drive you nuts by chasing them for petty bills but because you will also get bored out of your mind. Get involved in, or start a more significant project as soon as possible (Even FOSS for no money is better for your experience than wasting more time on these).
Add in the business side - finding clients, chasing bills, and the small 3 page sites won't be making you any money unless you have an army of developers churning them out.
Personally, I see "Web Developer" as a skillset worth knowing, not an industry to be in. Use small gigs to learn HTML, CSS, Wordpress etc - but branch out. Contribute to some FOSS JS/PHP/Ruby/C#/whatever libraries, build some sites without WordPress or similar, and angle yourself towards being a web developer at a company who tag line isn't "Web Development" (or digital marketing!).
All that said, I know there are people who LOVE the 3 page site work. So maybe that is what you want, but it wasn't for me :)
The main problem with this is these days it's so easy to whip something together with Wordpress and a template, and many web hosting and domain purchasing sites even offer extremely simple ways to set these types of sites up.
Quite frankly, it was never that hard, but these days the value proposition is practically nil.
And on the opposite side, it is quite easy to start a business of creating websites using those tools with minimum knowledge. I know a few people who started from that and eventually moved to more complex projects.
There is a surplus of beginners due to a surge in tech bootcamps.
If you're in the bottom half of talent it's a race to the bottom of low cost.
If you're top 25-50%, you'll probably have consistent good paying work.
If you're top 25%+ you can make a great living.
Probably similar to any skill set.
My 8 months of studying were full-time studying (freeCodeCamp and plenty of small projects). 6-8 hours every weekday.
Not sure what you mean about "solid path", but you have to have focus.
edit: these are my tips for becoming a frontend web developer, which was my path.
First, learn the essentials of CSS - don't aim to be a CSS wizard because that won't help you get your first job on good jobs (the ones that are not on agencies where your sole job is to transform photoshop images in HTML).
The most basic and true advice is to focus on learning Javascript properly and deeply. Read books (EloquentJS for starters is a good one), read documentation, watch videos (Fun Fun Functions youtube channel is a nice one), practice on code-on-the-browser platforms (I am a huge fan of freeCodeCamp) and create some projects of your head using Javascript only.
At least 3 (full-time) months on Javascript only. Then, move on to focus on React, because that's where all the jobs are going. And I say this being hired to work with Ember on my first job (and I enjoy Ember), but pragmatically, React is the way to go (assuming you have learned Javascript properly before).
Also, pay attention to good software development practices (The Pragmatic Programmer is a good one) that are not about language syntax (e.g. coherent indentation of your code, good variable and method naming, how to make code more readable and maintainable). Become what in the United States they call "an engineer" with certain glamour on it. You don't need to buy the hype that software engineers are a special breed of people superior to all others, but do make an effort to learn best practices, design patterns, clean code and all that.
Don't get into any tech discussions in forums, flamewars, don't take sides, etc. This early in your career you should focus and be pragmatic.
Summary: Learn the essentials of HTML+CSS. Focus first on Javascript, then on React. Create your own projects and learn what good development practices you should use on them.
I wrote a few blog posts of my learning and career change to web development, you might find them helpful: https://rodrigohgpontes.github.io/
Start with a Website, Not a Mobile App https://news.ycombinator.com/item?id=18824993
I found their web-first arguments mostly unconvincing. And kinda hand-wavy on certain points. Two relevant points, rapid MVP development and instant updating of your app I have to agree with. But the idea that desktop software pricing translates to people being willing to pay more for a website is a crock. People think websites should be free. It’s not just users who think that. I have to educate my clients why their business app that needs a login, data storage and access controls is not “just a website” and why they have to pay me significantly more to make it happen.
At certain companies there are definitely people who get paid to write compilers or develop frameworks (for any which thing), operating systems, backend cloud tech, robotics, etc. but it would probably be seriously hard to break into this without a CS degree or relevant experience
I see it more like data science, 10% programming 90% math.
Edit: 3% programming, 30% math, 67% scrubbing data. Thanks for the correction shortoncash. :)
I could be wrong, but this is my experience.
Aside from tech giants, the web is probably one of the most used interfaces ever. There a tons of business opportunities online. Just about every business is participating online. There are tons of jobs here.
I specialized in computer security and am basically doing web development at a major tech company right now. It's kinda sad but I like money.
What you're missing is three fold...
1: Where do people hire freelancers.
2: Sales skills.
3: An alternative to worrying about 1 and 2.
1. Create a profile and Upwork. While everything you'll read about Upwork will be negative you need leads. Upwork gets them for you and yes you can create your own website and start there but Upwork already spends a ton of money on ads / SEO and content marketing to keep generating leads. Take advantage of it.
2. Learing how to sale is critical for everyone, especially web designers and developers. Go down the YouTube rabbit hole and got to Amazon and search for sales books. There are a million ways to sale things so read the first chapter of each book and read reviews until you find something that sounds like you can feel comfortable using with clients.
I recommend Jonathanstark.com, Doubleyourfreelancing.com and read How to Become a Rainmaker: The Rules for Getting and Keeping Customers and Clients
3. Alternatively you can skip the above and do one of the following. Subcontract with a marketing agency that needs to hire a developer. Find them using Google and could email them. Tell them you will lower your rate since they're getting the clients and that you don't like sales.
Finally you can hire a sales person on 100% commission to find clients in need of web development and if they ever find a client that doesn't match your skill set outsource the work using your same Upwork account. Upwork allows you to not only freelance but to hire as well.
The sales person should get 50% of the project costs upfront to start and upon delivery the client would pay 50% when completely satisfied.
Pay the sales person 20% to 30% of the project or agree on a fixed fee. They don't get paid if they don't find a project for you so make sure and hire many salespeople.
Finally if you're smart (which you seem to be) don't worry about knowing everything before you jump in. I've been freelancing since 2004 and run into new technology I have zero clue about. Howler I simply read the documentation or watch videos and boom new knowledge.
Start now and be confident in yourself!
However, having six months of experience, Toptal might not hire you. As someone already posted, I'd advise you to find a team and gain some experience. Having a deadline, and a customer with very high expectations - perhaps set by your initial promises - is sure path to a very stressful worklife. Don't do it.
Also, web development can be a good entry point to get into software development in general. You'll inevitably cross paths with backends that power the web and can grow into a backend developer as well. Also, today developing for web frontends and native mobile/desktop apps is more similar than ever.
There are a lot of php/laravel jobs still, but JS seems to pay more, and it's everywhere - the # of jobs out there for frontend or full-stack js devs is crazy. Plus with JS you can do backend and frontend.
One thing you might do to get started is find a mentor, or partner with someone and just start building stuff. Tutorials are shit (except when you need them to solve a problem). You can't just learn to code following a book or guide or video. You've got to get your hands dirty and 'tinker' with things. When you try to do something and can't figure out how, then you'll go and watch tutorials or read stackoverflow threads.
Everytime you break through these 'walls', is when you level up your skills and reach new heights as a developer. I've been doing laravel since 2013, and Vue since 2016 and I'm still learning every day.
Every time I see older code I wrote even 3 or 4 months earlier, I cringe at how ugly it is and could be improved with what I now know. You have to love learning though to be a good dev, because you'll be learning/googling your way out of problems for the rest of your life or until you build an app that brings in residual income and lets you retire.
This is great -- people tend to quickly get good at hobby skills (as those are something they like and do voluntarily). However, a few weeks of learning is not nearly enough to get a taste for what a job there requires / involves and especially decide whether you will like what you do for a hobby as a career. I suggest two paths, pick one that you like most:
1. Pick something cool you can do as a "web app" and do it. Repeat 3-5 times. Don't worry if there are 50 existing options to do it, you are learning. But the end result should look good to you -- that is to be something you would enjoy using or showing to friends. Some examples: generate a beautiful ready-to-print PDF calendar with custom something (birthdays, vacation pics / links, etc); take a photo and make an STL file ready for 3D printing a coin (render on display, allow some options, etc.); capture and analyze OBDII data from your car; etc.
2. Find where others doing the type of development you want to do hang out (meetups, etc.); buy them beer and ask what they did, what the job market is, what skills you would need. Tell them that you did it as a hobby and wonder what the job market looks like. Many folks would gladly share wisdom or even mentor if they feel it is useful and appreciated.
Good luck and have fun!
There's a lot of demand for devs across the board (this is my gut feeling from participating in hiring at my current company). This probably varies a lot across teams in a company, across companies in an industry, and across industries.
One strategy I recommend is to narrow down your target employer market so you can get more specific answers. What industries are you interested in? What are some companies you might want to work for? Do they have an engineering team (most likely). Then figure out what roles they have open and do your best to position yourself for those openings once yo u start interviewing.
> that I should risk more time and money?
What kind of self-learning have you already done? Can you give us some information about the courses / tutorials you've been following? Is this something you find yourself enjoying?
More details about your situation would help. For example, if you've mostly been following a coursera course for the last six months that's heavy on the theory side, I might recommend that you spend more time with something more hands on like building a web app to solve a problem you have.
Python, go, c# and Java can open 'enterprise' doors for you.
If by web developer you are referring to what many now call a "front end" developer then yes, that field is very busy and can pay quite well. Front end developers are expected to know a popular JavaScript framework (such as React) as well as CSS and HTML. Front end development is a dynamic and exciting field. I've been in and around "web development" for roughly 20 years and it is quite fun and has quite the future ahead.
Just last week the top trending article on HN was about how you should start with a web app instead of a mobile app. Today there are really powerful and much easier to use frameworks than what we had compared to just a few years ago. I say, if the web truly interests you then dive in head first and pour your heart into your work and most of all SHOW YOUR WORK publicly so people can find you and know you. That's how you find great teams.
The problem with the Web Dev job market is that everyone and there dog is doing what you are doing. If you want to be taken seriously you need to set yourself apart from this crowd as a professional developer.
Yes, but work on learning the full stack. Learn frontend, backend, SQL, sysop. Can you set up a server from a base image and eventually have a full app running reading from a database? Great! Now get familiar with cloud solutions like AWS. That might sound daunting, but it's actually easier in some respects. You don't have to know everything before you get a job, but knowing a little of all will show great promise in an interview.
Don't get attached to any one technology or programming language. This field changes all the time (annoyingly so). There was NOSQL, React, Node, hell I remember the times before Memcache. So keep your eyes and brain open and be ready to adapt. Your current place of work will likely stay stale with whatever they have, but if you don't keep up with the outside world, finding your next job will be much harder.
- Don't just learn Django, learn Python
- Don't focus on React, Vue, etc. learn JavaScript
Those skills will last longer and make it easier to transition into other roles if front-end doesn't feel right for you at any point in the future.
Here was a typical (not verbatim) exchange when I was a Front-End Architect interviewing candidates for my team back in 2012 or so:
---
Q: Tell me about your experience with JavaScript.
A: I know JavaScript because I've been working in jQuery for a year.
---
Further questions would isolate the fact that they've _only_ used jQuery. It was depressing, really.
I mentor developers to really strive to learn and understand the fundamentals precisely to stop propagating the idea that libraries and frameworks > fundamentals. Problem is, I've already started to witness history repeating itself when interviewing candidates and getting the equivalent answer above--but with "React" in its place.
Most developers will never need to solve “hard problems”. They will be working on yet another software as a service CRUD app or a bespoke line of business app that will never see the light of day outside of their organization.
I’ve found studying architecture, soft skills, and my business courses (before I dropped out of graduate school) to be much more helpful in my career.
You don't need to spend a penny (or too much time) to learn web development if you put in the effort. Mozilla Developer Network [0] is what I recommend as a learning resource. I'd advise reading the JavaScript Guide if you have previous experience; if you don't, there's stuff for beginners there to. Learning some HTML & CSS will be most helpful.
I'd advise that after you learn JavaScript, you learn React [1]. Take the tutorial. I'd recommend watching one of the React talks to explain to you what makes React useful.
I'd advise you prefer learning Node.js [2] next, and it's probably a better choice than learning PHP or Ruby for the purpose of server-side web development. Perhaps take a look at TypeScript after.
To become a good programmer, branching out is helpful. A requirement to be a good programmer is that you have some basic level of CS knowledge (there's many free ways to study CS). Learning some C/C++/C#/Java/Rust/Go is also good, but this is not a priority to getting your initial webdev jobs. This isn't necessarily going to be useful in getting a job directly, but improving as a programmer will help indirectly.
HTML & CSS mastery is a lot less important for a web developer (as opposed to a web designer) than JavaScript. You don't need to memorize everything, but you should be able to get by with Mozilla Developer Network open for reference.
Other resources to check out: Eloquent JavaScript /r/JavaScript Free Code Camp javascript.info
[0] https://developer.mozilla.org/en-US/docs/Web/JavaScript [1] https://reactjs.org/ [2] https://nodejs.org/en/
1. No one here can really tell you. They would be guessing. I would go on to indeed.com and type in the skill set you consider to be "web dev" and make note of the number of jobs and (where available) salary offering. This is the current state of the market.
2. You are asking an even more complicated question about the future state. The answer is even more prone to speculation. Your guess is as good as anyone's.
3. Although web-dev in its current form will almost certainly not be in demand, the future form will evolve out of the current form so the time you spend learning, debugging, networking will likely not be wasted. (unless we crack General AI).
I know it's anecdotal but here is my story: I'm used to hearing that my friends are looking for work, and some tell me about how many applications they have sent out.
I went on to LinkedIn and ticked the checkbox that says I'm available for hiring, and I got a bunch of recruiters asking for a chance to speak with me. I'm now going to a new job where I'll earn what a typical senior exec earns in my country.
Tell me that's not powerful.
For example, here is what a Front End Engineer might have knowledge in:
- HTML (semantic markup)
- CSS (layout, animations, responsive, mobile-first, media queries, SASS, etc.)
- JavaScript (the language itself)
- HTTP, AJAX, Promise API, RESTful APIs, async VS parallel
- DOM APIs, DOM Performance
- UX/UI methodologies
- Accessibility, ARIA
- Module bundlers, transpilers, build tools (webpack.js, rollup.js, etc.)
- Various frameworks and libraries and knowing why and when to use them (e.g. Lodash, React, Ember, jQuery, etc.)
- Programming design patterns, methodologies, and best practices
- Object oriented programming
- Functional programming (.map(), .reduce() and knowing about immutability)
- Test driven development and various testing frameworks/libraries
- Command Line (Bash, and/or other Unix/Linux shells)
- Version control (GIT)
- Data Structures and Algorithms (arrays, trees, DFS, BFS, and more)
- High or deep level knowledge of how Browsers work (the event loop, reflow/relayout, etc.)
- A server side language (NodeJS, Ruby, Python, PHP)
- Databases (MySQL, NoSQL)
- A server side web framework (ExpressJS, Ruby on Rails, Django, Laravel, etc.)
- Security (authentication, authorization, XSS, SQL injections, cookies, and more)
- Ability to deploy a product in a production environment (e.g. AWS)
- Development workflows (GIT, code reviews, continuous integration, and more)
I personally think it's a mistake to only focus on what will be useful in the future while ignoring subjects that you find interesting. In reality, you don't have enough information to know whether the choices you make today will be optimal for your future self. In my opinion, it's best to just follow what interests you and keep an eye out for opportunities along the way.
Two more interesting questions you should be asking yourself are: 1. Do you love writing sofware, and 2. Are you good at it?
If the answer is yes to both then you're on the right track. If not, you could have a problem down the road.
The advantage of learning some of the newer technologies like Vue and React are that they haven't been around for too long. So, if you get 3 years of experience with that, you can be considered relatively senior. Just something to think about if you're totally new.
The bread and butter of alot of "Web Developers" is Wordpress. If you learn that inside and out, you can likely find a job somewhere in a decent market. There are other CMS you can learn instead, but once you pick up one, then the others shouldn't be that difficult.
Another path is to pick up a ton of client side javascript skills (ideally combining bootstrap with frameworks like Angular, Vue, etc) and become a "front end" developer. This is relatively easy to break into, but it's harder to muddle your way through as you have to know a wider variety of skills. If you have the aptitude it can pay very well, though.
Probably the hardest to break into, but maybe the most stable, is to learn about databases and how the server works, and then go into server-side programming using PHP, Java, or javascript using node.js. I think this would involve some serious time commitment, and may be something you pick up after you get your foot in the door.
* Within Web Dev, others have pointed out that there are many technologies you can work with, but there are also very many different kinds of output. Some web developers produce production code. Some web devs focus on producing early prototypes, and have some mix of UX Design and WebDev skills. Still others work for agencies where there is a heavy emphasis on delivering prototypes to pitch, but then the team will need to produce a production version of it. All of these start with a common skill set, but depending on what you want to do you might need more depth in some areas than others.
* While I think it is a great career choice, there is still some Computer Science elitism in some circles - depending on where you apply for jobs, you may get asked interview questions that have little to do about WebDev itself. This practice is obviously not helpful, but it is a reality in some places.
* Try to focus on getting an area of depth as well as sufficient breadth. You want sufficient breadth so that you can make it through most situations, but it's also really helpful in selling yourself as being an expert in a particular area.
[0] https://www.cnbc.com/2019/01/04/the-30-most-in-demand-skills...
Invest your time - over a period of YEARS - into studying computer science, where coding is only a small part of the course.
Then you'll be able to expand your career far beyond just Node web dev.
It may be important to clarify exactly what you mean by web developer though. I work in many different portions of the web stack every day (database, server side code, front-end code, etc). The more diverse your skill set, the more opportunity there will be.
At any rate, web is a really good entry point, and after a few years in industry you'll probably start to see different branches of development that appeal to you more. If you start out as a web dev there will always be different avenues and opportunities as your career advances.
I got a BS in Entrepreneurship and Innovation and all my web development learning and experience came from my own projects or on the job. It's been difficult for me to find an engineering or product management position despite having experience (one phone interview for ~25 applications). There's definitely more I can do on my part however this isn't unique to me.
Perhaps the fact that many companies have switched to automated screening systems to filter out all the junk resumes has made it harder to get interviews? To answer your question, the need in the market is there and if you are patient, your risk should be rewarded.
The work is not super complicated and it's often based on popular CMS software and/or frameworks, so it's easy to get going. But you'll be getting paid and working on real projects, which are what you need to start building a career.
You'll get to work with other developers and start making professional connections. Agency folks enjoy networking so you'll learn how to do that. And, jumping into a client company can be a viable way to move on to more complex work.
I'm in the DC area and basically every single agency is looking for developers right now. But there should be a similar industry in any medium to big city.
But there are a lot of people doing this work. You have to compete with them. That will take a lot more work.
This is a great related thread: https://news.ycombinator.com/item?id=18862790#18865742
If you're interested in combining your coding skills with customer-facing/problem-solving responsibilities, Sales Engineers are in huge demand. Companies are desperate to recruit for this combo of talent because it's so rare.
I'm the founder of Flockjay (YC W19 - tech sales bootcamp that helps people break into tech, without code). We have students with coding experience who are doing incredible things - companies can't wait to hire them. Happy to chat more.
Personally, I had a good friend mentor me and point me at things to learn early on, which helped a lot. A structured program would have the same benefit.
I have no connection with it, but https://lambdaschool.com/ looks very interesting in that they bet on your ability to get a job: you pay nothing unless you do (other than the opportunity cost of spending the time to learn, which could be large).
The easiest place to start as a developer in 2019 is Web.
Technologies you learn now will be outdated tomorrow. Learning is a journey, not a destination. Try to focus on the larger concepts since these generally carry over across technologies.
I say this in an era of bootcamp grads, online micro degrees Udemy courses etc. where you can now study and 'become a web developer in 3 months etc.'.
It's true, you likely can learn enough about Javascript / frameworks / etc to build web applications in that period of time, but your overall knowledge and ability to draw inferences between web dev and other areas of CS will be severely lacking.
This isn't to poo-poo your path (I myself am a bootcamp grad), more hindsight as part of my journey.
What you are doing now is what most would likely call a 'top-down' path. Build some applications, work on some projects, learn one language all for the sake of building a portfolio. This is great! But it is only a piece of the puzzle. I would highly suggest you sprinkle in some 'bottom-up' learning as well (taking an algorithms class, or something fundamental to CS) and trying to draw the connections between what you are learning in the two domains.
I know that was a bit of rambling so to more directly answer your questions and concerns:
Q: "I have been self-learning for around six months and still have not found a solid path to follow." A: It is likely that self-learning is not cutting it for you. It sounds to me like you need structure. This could take the form of a bootcamp or micro degree or something more involved (slower) and academic... like a bachelors degree with projects mixed in. All have their advantages and disadvantages. At a high level:
- A good bootcamp will require you to be there in person, with fellow students who are on the same path. You will have structured learning and so will meander less. You will leave a good bootcamp having gotten out what you put in (ie if you slacked off they will not hold your hand) but may land a job. You will have spent a good chunk of money and even if you land a job you will have to fill in a lot of gaps.
- Micro degrees (like from Udemy) same caveats as the bootcamp apply but with swings. Will likely be far cheaper, but with less support, and likely less guaranteed outcomes. I haven't looked in a while but it's rare that I find people who have landed jobs doing these programs, while I can find multiple 'good' bootcamp grads who end up at many 'top' tech companies.
- If you go the University route you will have to amp everything up to the nth degree. You will spend more time + money. The effort that you put in will also matter A LOT (ie from what I've heard some people do the bare minimum CS work to pass classes, but never do interesting projects, push for good internships etc so they graduate and can't land jobs). It, however, my belief that if done right this can be the best possible option. A lot of bootcampers severely underestimate the importance of foundational CS concepts, these will be the first people in trouble during a recession or if there is a major technology shift.
Q: "Six months sounds like a lot but realistically it has been a few solid weeks of learning..." A: Six months is not a lot of time to learn almost anything. Let alone a year, or two etc. Especially if that learning has been very undirected (it sounds like you are meandering a lot). I know you are in a rush to be gainfully employed in a new career, but you shouldn't emphasize the time you've spent so much. The best engineers I've worked with are 15+ years into their careers and still think they are idiots.
Find a more structure path for learning, and don't beat yourself up over the time you're taking to learn anything. Good learning and understanding takes time.
Q: "Is the Web Dev job market in a good enough state that I should risk more time and money?" A: Yes, the market is still quite good for anything engineering related. Frontend, Fullstack, Backend you name it. Companies need smart people who can code and understand the systems they are working on. However like I said you should develop your skills so that if the current definition of a "Web Dev" changes in the next few years you can easily move onto the next thing. That means developing a love of learning and really understanding the core concepts that tie all of these seemingly disparate engineering fields together.
I think there are many good jobs available in web development. But it will depend significantly on your location.
I recommend looking at job posts for the jobs you want and teaching yourself the technologies they require. Consider looking for paid internships, especially if you’re in college (even if you’re just taking some community college courses).
I feel like good web devs require a tremendous amount of knowledge on different aspects of CS, Design, UI, UX, networking, etc... The problem, however, is most people approach the role like its a job at a fast food chain. I think both aspiring web devs and the vast majority of employers are guilty of this perspective.
These best people building new software and need help:
https://news.ycombinator.com/item?id=18807017
The most in-demand skill is: React. [From using grep/sed excluding JavaScript/JS].
So my answer is: Yes.
But, of course can you still make a career in nearly everyting where there is demand, and for webdev there is demand. The question is whether your skills can match the demand. And frankly spoken, six month's is nothing, especially if it's just learning, not actual work.
The base-level of learning for solid software development is usually measured in years, and that would be 30-40h/week of real learning. But there is also the student-market where you can earn get some pocket-money for low level-work. And depening on the country you live this can be a serious amount. There are several people from poorer countrys working remote for low money.
So when you wanna take this serious, you should really know your position, market and demand. What can you offer? With whom do you compete? And how much do you must earn to survive, to grow higher?
I used to be contacted by headhunters at least once a week. Nowadays, I hear from Indeed and LinkedIn that often. I have been to their offices for interviews and assured they would find me a job quick.
While I have risen through the ranks over the years to project manager and a prolific company and, eventually, ran my own profitable company, I have never, ever been sent on an interview anywhere by any of the operations I mentioned above.
Remember software dev is not about assembling big pieces of codes given in a framework, it's about logic / control flow, data structure, architecture. Once you understand all that, you don't consider yourself a "web dev" or a "mobile app dev" anymore, but just a software developper.
Computing disciplines aren't easy, so you're best off following your interests as you get started (self directed or otherwise); with the goal of sufficient skills in completion of a product. Move laterally, instead of deep prior to your first job, or until you have a more diverse understanding of the technology space. That'll paint your first job; there you'll do what you're payed for, and that can totally reshape you. This repeats forever.
Email in profile if you want to know more.
It is a great launchpad to do other programming besides web dev. Go into web dev, because there is a lot of cool tech in it and lessons. But learn other technologies as well that will not be replaced by automation.
It became something people who attended a 3 month code-camp can do without prior knowledge.
lol, it takes YEARS to be a good developer. It depends of where you live and what are your expenses and local job market among many other things.
But if you thing 6 months is a lot, maybe this is not the thing for you.
Are you asking because you are concerned about the field dying? This would be a viable question, so I will assume this is your actual question.
I would get involved today, not tomorrow, today. Contact a web development business in your area, or online and talk with someone. Ask them about what kind of work they are doing. Contact a few different types of web businesses. The smaller/medium sized ones are more likely to give you the time of day instead of just a secretary that will give you someone's voicemail.
My son is 17 and got an internship last year with a local company doing web design. (minor dev work) And now he contracts with them from time to time. The business owner would hire him right now full time, but agrees with me that he really needs some life/education under his belt first.
Every field out there _needs_ hard workers. People that will show up, have a good attitude and learn, learn, learn. Being a rock start is far less important. This is odd to hear when you are on the other side of this equation, but trust me, people hiring these days will hire for character and work ethic over perfect job skills, you just need to be able to get your foot in the door.
Last, find the kind of "web dev" you want to actually do. You couldn't make me do anything else right now in life, I have to do web dev, it's not a choice I could walk away from, it's what I like doing and I have no interest in other work for the time being.
You asked "risk more time and money", everything is a risk in life. There's very few absolutes. The question is are you willing to make it work? Web dev isn't like driving a truck or being a nurse where they teach you almost everything you need to know to do your job. With web development you have to keep learning and be ok with this. And you start off not knowing enough to really do the job perfectly. I am mostly self taught, and I had to go through years of re-educating myself out of bad habits, and deciding to chose industry standards and chosing the hard, but right way, to do things.
It's always paid off for me, but then I like learning, I like seeing fascinating solutions, I like puzzles and problem solving. I'd do web dev as a hobby if I didn't do it for work.
My last suggestion is to get started how I did, build something you actually want. And keep doing this over and over. I never wasted any time doing this. I made everything from my own text-to-speech tool (silly and half baked) to a full CMS. When in school I made multiple websites, games, apps, multiple portfolios, (trust me, a lot of this stuff was total crap, but I really learned a lot). Everyone else in my class did the minimum to get by. I've learned databases, server management, a few different version control systems, multiple languages, animation, design theory, etc... It's all been interesting, fun, often stressful, often exciting, but always useful.
In the end, if you don't find work, either keep looking until you do, and keep up your skills (always, always be working on something) and eventually you will find something. It's just a numbers game. Or find satisfaction in whatever job you find yourself in outside of web development, it's always an option for some people.
Cheers!
So what I found is that students find jobs pretty quick. Some of them after 2-3 months from the ground up, from nothing! Absolute beginners! (the entire course is for 6 months, 100 hours of video).
I was thinking why is that, because here is some quotes from reddit:
1) "why is it still so damn hard to get your first job?"
https://www.reddit.com/r/cscareerquestions/comments/6zxrzt/t...
2) lots of interviews, no offers
https://www.reddit.com/r/cscareerquestions/comments/4s9foi/l...
3) "I graduated from GA Tech.. looking for entry level... position for over 6months but still nothing."
https://www.reddit.com/r/cscareerquestions/comments/6ypimg/r...
But in Russia it's different (99% of my students are physically located in Russia, I'm in US). There is huge demand for web developers. You can jump on the train after couple of months. Why it's so different than US?
And I found explanation: there is no Russian-speaking cheap labour that can write code. Companies in Russia need Russian developers only because English isn't number 1 (or number 2) language in the country. For US (and English-speaking market) it's the opposite: lots of English-speaking cheap labour, while locals are struggling to pay their bills and asking for more $$$.
$30/hour for any US-based programmer is not a big deal, but for some countries it's a huge deal. So countries like India, China, Russia, Ukraine all contribute to that. For companies it's easier to hire someone from these countries with experience, rather than finding local for the same money without experience.
So the bar is pretty high if we're talking about US. If you're based in Russia, it's probably the best time ever to become web apps developer, especially FOSS webdev: sanctions force government to switch to open source solutions and demand is damn high.
I'm also author of the book about Ruby for absolute beginners, if you're interested https://leanpub.com/rubyisforfun