Live data from Hacker News

Developer Roadmaps

roadmap.sh

11–20 of 139 posts

Re: Developer Roadmaps

#11

Would love to see a roadmap added for embedded development or system level programming etc. There is a huge emphasis on "the web" when it comes to software engineering, that people forget (especially college students figuring out a career path), that there are many jobs in defence, hardware companies, etc. that develop software without using any web technologies at all.

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 development...to mention but a few; are some of the skills a modern embedded system engineer needs at the lower level.

Re: Developer Roadmaps

#12

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…

IMO, you could put Remote Procedure Call (RPC) technologies such as gRPC for backend developer.

Re: Developer Roadmaps

#13

Would love to see a roadmap added for embedded development or system level programming etc. There is a huge emphasis on "the web" when it comes to software engineering, that people forget (especially college students figuring out a career path), that there are many jobs in defence, hardware companies, etc. that develop software without using any web technologies at all.

What exactly qualifies as a web technology? Isn't anything on an IP address a web technology?

Web != internet.

HTTP, HTML, CSS, JavaScript, etc are web technologies.

TCP/IP (among other things) are internet technologies.

Web tech builds upon internet tech.

Re: Developer Roadmaps

#14

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…

This is an outstanding piece of work. Kudos.

Re: Developer Roadmaps

#15
post #12

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…

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.

Re: Developer Roadmaps

#16
I've looked at the "Backend Developer" guide, I'm surprised that it doesn't mention git or any other version control tools.

I think it could be a useful addition; nowadays version control is part of almost all backend projects.

Re: Developer Roadmaps

#17
Great concept! Teaching yourself things is always difficult because you only see things horizontally and don't know how to actually build on what you know, especially without spending 000s of dollars.

Re: Developer Roadmaps

#18
post #11

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…

I interpreted the parent comment as do all of the parts yourself. Pick microcontrollers, design the PCB with power supply, find the right toolchain for both microcontrollers and implement serial communication. Which is almost 90% percent of the job.

Also, does FPGA come to mind when embedded is mentioned? I always assume that FPGA is a whole another subject (only FPGA not the board part).

Re: Developer Roadmaps

#19
post #16

I've looked at the "Backend Developer" guide, I'm surprised that it doesn't mention git or any other version control tools. I think it could be a useful addition; nowadays version control is part of almost all backend projects.

Thank you for pointing it out. It is still being modified and will hopefully be fixed this week along with the other changes. It was there in the "common" section in the repository https://github.com/kamranahmedse/developer-roadmap but was missed when moving the roadmap to the website.

Re: Developer Roadmaps

#20
post #15
post #12

Earlier 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.

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.

Post reply on HN