8 ms·
Roadmap to becoming a web developer in 2017
- yAak 10y agoThis was fun to look at from a novelty perspective as a native application developer. Q: Should Rust be considered a noteworthy web backend development option, or is there just not much community activity for that?
- muratsu 10y agoThis is not really an answer to your question but.. The one liner for Rust suggests that it's a systems programming language. It's designed to solve problems of software engineers who deal with lower level stuff than most application level engineers. Personally, I would try to pick a language that's more suitable for the job.
- azdle 10y agoProbably not in a list like this. If you're just getting started you want something where you can be productive fast. And I say this as someone who writes web backend code almost exclusively right now. The way that I see rust is as a language (& ecosystem) that is all about making things right, reliable, & efficient. That unfortunately comes with a bit of cognitive overhead during development. If you combine that with learning rust it gets a bit more difficult, and if you combine that with learning programming at the same time too you're going to end up with a lot of people quitting out of frustration.
- bpicolo 10y agoRust is not a particularly convenient choice for general backend. Specific, high throughput / parallel microservices, yeah, but doesn't lend itself to being particularly productive in the realm of web dev.
- crzwdjk 10y agoSpeaking as someone who is currently developing a web app with Rust: no, not yet. It's getting there, certainly, but the tools just aren't ready for general use yet and there's still likely to be a lot of change before things stabilize. In particular, tokio is still at 0.1, and many of the web frameworks have yet to move their internals to be based on it. Foundational pieces like serde and diesel have yet to reach 1.0, but are at least usable on the stable version of the compiler now. More bleeding-edge frameworks like Rocket.rs still require nightly though, and will continue to do so until procedural macros are stabilized.
- hughes 10y agoThis is quite an accurate overview of the surprisingly vast vocabulary of concepts a web developer needs to be familiar with. It certainly looks a bit daunting all laid out like this!
- sauldcosta 10y agoThis is really useful. We're building a lot of courses for Codevolve.com right now and definitely will be using this as a reference for where to focus.
- ryanolsonx 10y agoIt's pretty interesting that all of the backend languages are all interpreted languages. No love for any typed languages?
- zeptomu 10y agoThat is actually quite nice, but it also shows how incredible complex modern web development gets as there are many moving parts involved. The backend suggets Python, Ruby, JS or PHP and I agree that choosing one of them is probably a good decision, as there is lots of documentation. However if one goes down the Java or Go road, are there recommended packages - or do people just use the standard libraries?
- nothrabannosir 10y agoFor Go people use stdlib.
- mcdevhammer 10y agoSpring Boot for Java
- eranation 10y agoI second that. With honorable mention to Dropwizard
- psiclops 10y agoFor Go, people use either the standard library or third-party routers, etc. glued together That being said, buffalo is getting pretty popular. http://gobuffalo.io/docs/getting-started http://gobuffalo.io/docs/getting-started
- nicholassmith 10y agoFor Java JHipster (https://jhipster.github.io https://jhipster.github.io) wouldn't be a terrible starting point.
- lukeda 10y agoIt would be good to see the serverless architectures (eg. AWS lambda, API gateway) added to the backend and/or devops section.
- m_fayer 10y agoYep, surprisingly good. My only criticism is of the implied simplicity of the "backend". In reality the choices are vast with a huge long tail. That's because backend, as opposed to frontend or mobile, is really just good old fashioned general purpose computing with a sprinkling of networking and http middleware, and distributed systems glue.
- oever 10y agoExactly. It troubles me that all four suggestions for the backend have very few inherent checks and leave a lot of room for security problems and other bugs. Personally, I prefer Yesod for the backend. It gives a very fast, static binary. It requires learning Haskell. The Haskell package Esqueleto ensures type safety all the way from the HTTP requests to the database tables. A URI parameter that is encoded to be a key on a table can only be used when querying that particular column or columns that are foreign keys to it.
- alexashka 10y agoThis roadmap is for people who actually want to have a job at the end of their roadmap :)
- flukus 10y agoA job at a trendy startup. If you want a job learn something used in regular business.
- jhall1468 10y ago> It requires learning Haskell. Which virtually nobody is using in production.
- flukus 10y agoAnd java and c# only get one little box each even though they're more widely used in the industry than node, ruby and python combined.
- 10y ago
- anotheryou 10y ago"star building" should be at the top
- Etheryte 10y agoIf a guide recommends jQuery as a central basic in 2017, it's hard to agree. Sure, it can have its uses in old projects and simple one-off scripts, but for any reasonably sized project with reasonable browser support you will be going with something else. Is it still worth knowing? Sure. Is it something you should learn first? Absolutely not.
- sarreph 10y agoThis. Thankfully, the only thing 'foundational' about the web is the pure languages that it is built upon, and not its frameworks. The reason I had a 'web-development epiphany' is that I moved away from for months fleetingly trying to hack jQuery into my web projects, and then suddenly grokked React within days. If you come from a programming background (and especially a functional one at that), learning ES6 javascript with a more modern framework (React, Angular, Vue) is the way to go.
- spraak 10y agoSimilarly I'm confused at the 'personal recommendation' of gulp over npm scripts. Does anyone really use gulp for new projects..?
- bshimmin 10y agoIs gulp seriously so out of fashion already?
- markdown 10y agoI heard webpack is in now. Grunt and Gulp have gone the way of the <marquee> tag.
- Zalastax 10y agoIt was used to hack together build pipelines since the tools didn't fit together nicely, creating hard to debug messes which we grew tired of. Those hacks can be replaced with webpack and you're often left with a few snippets that fit nicely in the script section of package.json (npm scripts). Gulp is still useful for some projects, but a lot less often.
- gketuma 10y agoLike it
- chrisabrams 10y agoWhat I find most interesting is that the majority of these technologies did not exist or were in their infancy ~7 years ago when I first moved to Silicon Valley. Looking at this chart must be much more intimidating for a young developer today. I remember a decade ago when a front-end developer meant you handled HTML/CSS/JavaScript/Apache/PHP/MySQL. Today, there are 15 forks in the road all leading to different paths as a front-end developer.
- scriptkiddie95 10y agoAs a young developer, it really is intimidating. Hard to know where to even start these days, it's overwhelming.
- voltagex_ 10y agoDoes 28 still count as young? I've been doing some form of web programming for 8 or 9 years now and it's almost impossible to keep up with JS/Node/NPM/100 different poor re-implementations of 'make'. Luckily there are big enterprises that provide job security without chasing every new framework.
- cholantesh 10y agoI'm 28 myself, with experience primarily in web and ETL. I'm finding that even the big orgs are doing buzzword fishing on their jobs descriptions. MV* frameworks for largely static sites and data sets, served up to small, internal audiences, etc. Strongly weighing my options for moving into another space such as embedded systems or DSP, where the problems are a bit more tangible.
- newbear 10y agoI feel like I got into programming years back ( I chose JS/web focus for future job prospect reasons) because I wanted to be introverted and solve problems. Instead it's become an extroverts heaven of circlejerk-buzzword-sixfigurehunting-pretension. I kid - there are amazing people doing amazing things but maybe embedded systems or dsp is more what I'm looking for?
- soneca 10y agoWould anyone care to estimate how much time would take to someone starting from scratch be able check all bright yellow boxes?
- andrewstuart 10y agoI just recently completed my journey to "tick all the yellow boxes", i.e. to have sufficient competence in every required technology to be able to build my own full stack applications from end to end. For all three of the roadmaps on the diagram, it took me five years, part time weekends and nights. What this means in practical terms is that most of the things that I need to build an application are familiar to me and I have worked with them and programmed them at some point, and I feel like I know where to start when resolving issues with those technologies. And that was starting from the point of being extremely technical, and having previously owned software companies and already having architected and designed more applications than I can even remember, and having done a little programming here and there over the years.
- et-al 10y agoOptimistically? You could do it in two years if you're studying full-time, focused, and have a mentor for any roadblocks. Six months getting familiar with programming, and 6 months in each area (front, back, devops). However, with things like devops, I'd personally want someone with a year or two of real, working experience. And this is not factoring in the potential of burnouts from repeated 8-10 hour days of studying. Lastly, it's pointless to check off all the boxes there unless you're trying to make yourself super marketable. For example, if a company is hiring a Rails developer, they don't care if you know Node/Django/Go/the next hot thing.
- alpha_squared 10y agoA lot of time. Which roadmap in particular were you asking about? I'll attempt to estimate each of the three, though I'm sure others here will have better estimates in each. I'll overestimate as well, as much as double what I think is fair because, if we're honest, developers are bad at estimating large time periods. This is hours-technology pairing. A '?' designates uncertainty. Front-end: 010 - HTML 024 - CSS 070 - JavaScript 020 - jQuery (controversial / optional, I'd suggest it) 026 - JavaScript: ES6 010 - JavaScript: gulp 012 - JavaScript: npm / Yarn 0?? - JavaScript: Webpack 0?? - JavaScript: Typescript /// TOTAL: 172+ hours Back-end: (going to generalize) 060 - Language: Ruby / Python / PHP (+20) / Node.js (+??) 006 - Package manager 012 - Testing framework 024 - Web framework 120 - Web Server, Restful APIs, ..., Docker 0?? - Storage: Caching 036 - Storage: Relational databases 020 - Non-relational (NoSQL) databases 080 - Search engine, GOF design patterns, ... (+??) /// TOTAL: 368+ hours DevOps: 120 - Operating System 080 - Automation 140 - Cloud 0?? - CI / CD 0?? - Monitoring & Alerting 030 - Containers 030 - Cluster Managers 050 - Web server 999 - Love for terminal ??? - Everything else /// Total: 450+ hours You'll notice there's a lot of overlap between back-end and devops, though. I'd say this is the _minimum_ time you'd need to understand the basics of each branch, but you'd understand enough to be competently productive.
- brian-armstrong 10y agoComputer architecture isn't even mentioned in the backend roadmap. That's going to make a pretty weak backend type, who are usually very familiar with the "how long does X operation take?" game
- fizwhiz 10y agoLooks like it's mostly targeting application developers that don't normally deal with nuances of specific microarchitectures.
- hoodoof 10y agoNice. What was this drawn with?
- deleted 10y ago[deleted]
- et-al 10y agoBalsamiq - https://balsamiq.com/products/mockups/ https://balsamiq.com/products/mockups/
- noobiemcfoob 10y agoAll of these can be reduced to... learn what you need to learn to build your thing, learn that, then go build your thing.
- bshimmin 10y agoMy initial reaction to this was "Good grief, no one needs to know all this stuff!" Then I saw the "Pick any" label in the key and it made a lot more sense.
- henryw 10y agoThe backend is missing Java/Scala frameworks. Also, maybe Hack can be added to the PHP branch.
- nkkollaw 10y ago"start building" should be at the beginning, not the end...
- robodale 10y agoThis. Start building now. Get some momentum and motivation by working with what you already know, then pull back on that stick and get that airplane flying. Figure out how to steer/not-stall/do-loops/land with fancy stuff later. It's the fear that you might do something wrong that's preventing you from starting.
- sAbakumoff 10y agoHow come the 2017 backend chart doesn't have Golang?!
- dullgiulio 10y agoIt is correctly mentioned as "Go".
- sAbakumoff 10y agoOh, it's barely visible and for some reason it's in the same bucket as C# and Java. That's so lame.
- idlewords 10y agoIf you're a newcomer to web development, don't be intimidated by this stuff. Much of it is unnecessary at any reasonable scale. The best piece of advice is to have a small project you're genuinely interested in, and don't ever be embarrassed because what you make is too simple or too plain-looking. Your brain can only handle a fixed amount of complexity, so fight it at every step, especially when you're just starting out.
- domparise 10y agoI feel like this could also use DNS for backend or devops
- jetsnoc 10y agoIs anyone still developing multi-page architecture apps? Seems like you could still develop simple applications a multiple of times faster with Ruby on Rails or Django and sprinkle in Angular and/or AJAX Requests as needed. Surely that is still a thing. I know that a lot of you are all engineering for Netflix scale but developing two independent applications that speak to each other over an API spec sure has it's costs and is a drag on a small scrappy team wanting to iterate quickly.
- jaredklewis 10y agoI spent a long time developing traditional rails apps. Today I spend most of my time on SPAs, and that I can tell, development time is similar. Of course the first few SPAs took much longer while I learned things and the ecosystem built up, by today, I feel equally comfortable.
- jetsnoc 10y agoIf you can get the time to develop the software to be similar with all of the benefits of a SPA, that is hard to ignore. Any recommendations on how to make this a reality?
- szastupov 10y agoIt totally depends on task at hand. If you have a db/forms heavy project than Rails/Django gives you advantage, if your project is more driven by interactions and subtle UX then SPA lets you focus on that. Like, imagine how hard it would be to make Shopify as SPA (https://engineering.shopify.com/17489056-rebuilding-the-shopify-admin-improving-developer-productivity-by-deleting-28-000-lines-of-javascript https://engineering.shopify.com/17489056-rebuilding-the-shop...). On the other hand, Trello would never feel so fluid if it was driven by server rendering (notice how weird Github projects comparing to Trello). Personally, I've been doing SPA for years and think it's the right way for reach UI. But recently I had to build a form-heavy app and decided to go with classical server-side setup + some jQuery on client. Old school but very productive. EDIT: added link to shopify blog.
- 10y ago
- hmans 10y agoFocus on HTML and CSS. Those will still be relevant in ~10 years, while most of today's JavaScript hotness will be nothing but a memory long gone.
- iLemming 10y agoNothing about other languages transpiled/compiled to JavaScript? No Clojurescript, Elm or Purescript?