Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Developer Roadmaps

roadmap.sh

Post reply on HN
Print view View original

81–90 of 139 posts

Re: Developer Roadmaps

#81

Post by BigJ1211 »

madiathomas wrote: post #62
kamranahmed_se wrote: post #7

Hey guys, I am the person behind this website. Please know that it is still in progress. I wanted the initial version out so it is just the "roadmap" images for now. However, I am working on making these roadmaps more accessible for the beginners and easier to contribute to. In the list of things planned for the coming week is the textual version for each with different sections (job-ready, intermediate, advanced, ov…

Instead of learning JavaScript frameworks, isn't it better to advise people to learn and master JavaScript itself? I feel learning HTTP, HTTPS, HTML, CSS, and JavaScript inside-out will benefit someone than to try to learn a framework that will disappear very soon. When you know undelying technologies, it is easier to learn new frameworks because they will always be based on underlying technologies.

Angular/React/Vue are unlikely to dissappear they've existed for a long time now.

Angular: 3* years *9 if you count AngularJS React: 6 years Vue: 5 year

That's a long time by web standards, they also keep up and push native javascript forward.

So yes, learn native JS. Definitely learn a framework though, as those skills are ultimately what you need to work on anything more complex than a simple website.

Re: Developer Roadmaps

#82

Post by madiathomas »

BigJ1211 wrote: post #81
madiathomas wrote: post #62

Earlier quoted context omitted.

Instead of learning JavaScript frameworks, isn't it better to advise people to learn and master JavaScript itself? I feel learning HTTP, HTTPS, HTML, CSS, and JavaScript inside-out will benefit someone than to try to learn a framework that will disappear very soon. When you know undelying technologies, it is easier to learn new frameworks because they will always be based on underlying technologies.

Angular/React/Vue are unlikely to dissappear they've existed for a long time now. Angular: 3* years *9 if you count AngularJS React: 6 years Vue: 5 year That's a long time by web standards, they also keep up and push native javascript forward. So yes, learn native JS. Definitely learn a framework though, as those skills are ultimately what you need to work on anything more complex than a simple website.

5-10 years is too little considering the fact that they spent first 2-3 years gaining momentum. Even worse for Angular because it was completely changed along the way. JavaScript knowledge is still relevant even after 24 years. Whatever is on those libraries and frameworks will one day make its way into JavaScript and that will be theur end. Frameworks will come and go. Even the most successfull JavaScript library ever, jQuery, is on the decline because of newer frameworks and features like querySelector.

Re: Developer Roadmaps

#84

Post by tonyarkles »

cossray wrote: post #11
colechristensen wrote: post #9

Earlier quoted context omitted.

I could condense that down to a single task that will get you 90% of the way there: Learn how to bit-bang a serial interface on two different microcontroller platforms.

Claiming a serial interface task will equip you with 90% of Embedded Systems is the biggest disrespect of a profession I've ever encountered. To outsiders, the field might be regarded to be just a microcontroller playground. But the spectrum of hardware design and programming in the field is at an unprecedented levels. PCB design, power supply, SoCs, SBCs, FPGAs, peripheral interfaces, Embedded C and Linux software d…

Well, yes and no. Depends a lot on whether you want to do the "full stack" or not there. Lots of bigger companies have EEs to do the PCB, power supply, pinmux, etc stuff, and then embedded software people to write the code that runs on it. An embedded software developer probably should be comfortable using an oscilloscope/logic analyzer in a pinch, but all of the hardware design tasks aren't necessarily required for doing embedded software work.

I say this all as a "full stack" embedded guy. I'd love to have someone else take on part of it, but I'm a solo consultant right now :). Did both EE and CS in school, and more than happy to do whole projects end-to-end, but I also don't expect EEs to be fantastic programmers, or embedded software people to be fantastic hardware designers.

Re: Developer Roadmaps

#85

Post by mitchdoogle »

pjmlp wrote: post #34
kamranahmed_se wrote: post #7

Hey guys, I am the person behind this website. Please know that it is still in progress. I wanted the initial version out so it is just the "roadmap" images for now. However, I am working on making these roadmaps more accessible for the beginners and easier to contribute to. In the list of things planned for the coming week is the textual version for each with different sections (job-ready, intermediate, advanced, ov…

Frontend roadmap completly ignores everything that isn't a Web browser. So no Qt, wxWidgets, Android, iOS, WPF, Forms, UWP, WinUI, GNOME, KDE, ...

I think this would come as news to a large group of people, including myself. I've only ever imagined a front end developer working on the web.

Re: Developer Roadmaps

#86

Post by paradox_hunter »

rgoulter wrote: post #41

These seem to be bags of words, which hardly explain the rationale or context for any of the items mentioned. In terms of 'brainstorm of words, some of which may be useful', fine. But I'd be very surprised if even the average dev had even heard of everything on that list. The scope includes some ubiquitous things, and some things that are surely niche. I'm hoping no beginner gets the impression that they ought to kno…

I think he should make it clear who these roadmaps are for. From the looks of it, definitely not a beginner, but probably for someone who has spent atleast some time in the field.

Re: Developer Roadmaps

#87

Post by abnry »

madiathomas wrote: post #67
mLuby wrote: post #65

Earlier quoted context omitted.

Doctors, lawyers, and real engineers at least have similar or more broad domains they must be experts in, or people die. CEO is a hard role not because of domain area but because of risk and uncertainty, both of which tend to be low when you're "at the bottom of the food chain."

All doctors, lawyers and real engineers I know only focus on one aspect. They are specialists. I know lawyers who specialises in rape cases, conveyancing, ligitation, but I have never met a lwayer who is expected to solve a rape case today and register a bond tomorrow. Same with doctors. They specialise and only focus on one domain. I was talking about skills when I included CEO, not about risk. When there is lots of…

There's the concept of T-shaped expertise. Start with a broad base but then narrow down to a specialty. So you've kind of got both. Doctors, for instance, still have to know the basics of every bodily system, regardless of what they specialize it, because everything affects everything in the body.

Re: Developer Roadmaps

#88

Post by abnry »

greggman2 wrote: post #30

I think I don't understand these. They seem too high level to actually be useful. There's a old Steve Martin skit from the 70s where he's says he's going to tell you "How to get a million dollars and never pay taxes...... Step 1: Get a million dollars ...". These roadmaps seem about that level. Am I missing it? Are these actually useful? For example clicking backend the first thing is it lists 14 languages (although…

This is a roadmap, not a tutorial. You still need to get in the car and turn the key in the ignition. Logically, it makes sense to learn some technologies before other technologies. They build on each other. And for someone like me who knows very little software engineering, just seeing some organized list of terms looks helpful.

Re: Developer Roadmaps

#89

Post by ducaale »

_akei wrote: post #60

These lists are so depressing. Is there any other career where people are expected to know 100 things just to be an employee at the bottom of the food chain? I won't be surprised if it is harder to be a Full Stack Developer than to be a CEO of a multi-national corporation. Looks like we are pushing everything to Developers. Developers of the future are going to need a fulltime pyschologist to cope with this ever incr…

Well, you are not supposed to know all of them by heart. just start by what you need and know what other technologies that exist so you can learn them when the need arises. for me, I think I know or have a vague idea about most of the concepts mentioned in Frontend and Backend. But DevOps sections seems intimidating to me. People in other fields might feel the same way about Frontend or Backend Development. The thing is, just like any craft, it requires time and practice.

Re: Developer Roadmaps

#90

Post by madiathomas »

tarsinge wrote: post #69
_akei wrote: post #60

These lists are so depressing. Is there any other career where people are expected to know 100 things just to be an employee at the bottom of the food chain? I won't be surprised if it is harder to be a Full Stack Developer than to be a CEO of a multi-national corporation. Looks like we are pushing everything to Developers. Developers of the future are going to need a fulltime pyschologist to cope with this ever incr…

The key issue especially in the front-end roadmap is how the scale is not taken into account. Expecting all front end developers to use the same stack from small operations to Facebook or Google scale is irrational, yet for a lot of reasons it is standard practice. I understand how it gives a feeling of playing in the same court, but from an engineering point of view it’s useless complexity in a lot of projects. Edit…

One thing I have realised is that most tools developed by big tech companies were built to solve their unique problem. Majority of applications will never reach scale of Google or Facebook but people still use whatever is being used or marketed by those companies.
Post reply on HN