Here's an idea to improve this site: make the texts searchable somehow. Ctrl+F -> "JavaScript" shouldn't yield 0 results.
It's a png.
Developer Roadmaps
51–60 of 139 posts
Re: Developer Roadmaps
#52The Frontend Developer "roadmap" ignores any kind of native UI development. It should be renamed to Frontend Web Developer.
When people in the modern era say “front end developer” that basically implies web. Most people in common nomenclature don’t call iOS and Android developers “front end developers”. They are referred to as “mobile developers”.
Plenty of digital agencies do frontend work across multiple delivery platform formats
Re: Developer Roadmaps
#53Earlier quoted context omitted.
When people in the modern era say “front end developer” that basically implies web. Most people in common nomenclature don’t call iOS and Android developers “front end developers”. They are referred to as “mobile developers”.
Plenty of digital agencies do frontend work across multiple delivery platform formats
I don’t doubt that. But, if they advertise a need for “front end developers”, that would strongly imply web developers.
I would definitely be surprised if they advertised a position for a “front end developer”, I applied and during the interview they asked questions about Windows Forms development.
Re: Developer Roadmaps
#54Earlier quoted context omitted.
IMO, you could put Remote Procedure Call (RPC) technologies such as gRPC for backend developer.
Definitely a great idea. gRPC has been a huge benefit for us. I'd also get rid of learning NoSQL databases. It's good to know but in 99% of situations you should be dealing with them especially not before you learn about things further down the list like Docker, RESTful APIs, Auth, etc.
NoSQL is not less important than others. Especially not with the rise of many startups that want to scale and want their sites to be lightning fast (e.g. available at the edge). Many companies I worked lately actually thought the non-traditional databases are becoming more important.
Also distinguishing NoSQL and SQL is quite old and still dating from the CAP theorem which is also becoming obsolete. You have traditional databases and the rest since 'NoSQL' are incorporating SQL features (ACID, joins, etc) and vice-versa, soon it will just be databases with feature X,Y,Z. If you want to add something I would rather add 'distributed databases'. Learn relational databases probably boils down to 'learn SQL'
Knowing which database to use in the landscape is extremely important.
It should imo be: - Learn SQL - Learn GraphQL (becoming the new SQL quickly) - Learn gRPC - Learn about database features (consistency, distribution, replication, sharding, OLTP, OLAP) and what database to use in which situation.
Re: Developer Roadmaps
#55That's a really nice website. I'm a young developer interested in web developer and it gives me a good roadmap for how I would go along figuring stuff out till I become a full stack web development. I just hope that the full stack roadmap comes soon, the front-end and back-end seems really well planned out.
Another thing that I'll say that would be nice, if there were other roadmaps for become a mobile app developer like those including OSes like Android, iOS, Mac OS, etc.
Re: Developer Roadmaps
#56Earlier quoted context omitted.
Implying desktop job ads exist...
Plenty of them, specially in automation.
And games, medical, research, etc.
In my previous job i was working on game tools with wxWidgets, in my current job i am working on game tools with Qt. In between i got an offer (which i rejected since i am interested in games) for a Qt tool to be used for (IIRC) DNA research (or something like that, i'd just be doing the UI not the actual logic).
Re: Developer Roadmaps
#57These 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…
Yeah, it's just a word soup presented as a giant image. I've seen these before. They're not bad for at least laying out the landscape, but I think a more interactive format would be helpful.
Like allowing you to pick a language and then relevant frameworks/tools/patterns are shown. Furthermore it'd be useful to split it up into junior, intermediate, senior, principal level expectations. As a junior if you see this you might just want to quit on day one. As a senior it's useful to spot any gaps. As an intermediate it's useful to pick a next area to gain proficiency in.
Re: Developer Roadmaps
#58Earlier quoted context omitted.
Definitely a great idea. gRPC has been a huge benefit for us. I'd also get rid of learning NoSQL databases. It's good to know but in 99% of situations you should be dealing with them especially not before you learn about things further down the list like Docker, RESTful APIs, Auth, etc.
I would hope new developers ignore comments like yours. NoSQL databases are just a tool like other tools. And you should know when and why to apply such tools not just dismiss learning them altogether. Also every developer goes on their own journey. So if someone wants to build a social network then a graph database is going to make more sense even at the beginning than a relational one.
I’ve seen way too many junior developers fall in love with NoSQL databases to recommend them as a starting point. NoSQL is a niche tool whereas relational databases will be the bread and butter in a vast majority of cases. Many junior devs try to use NoSQL for everything and then fuck it all up.
Postgres even supports using NoSQL concepts with JSONB so there’s no reason not to start with it.
I’m sure I’ll get downvoted since HN has been very hostile to real talk lately but I don’t care.
Re: Developer Roadmaps
#59Good overview. I also like it as an illustration for beginners to explain, that "learning to code" is very broad and can be broken down into tiny areas.
When I teach friends how to code, I show them the bigger picture and then narrow down what I'll actually teach them no manage expectations: Java / Kotlin basics and some android development. So they now what they get in the beginning and what else is out there.
Re: Developer Roadmaps
#60These 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 increasing list of skills required from them.