Top
Best
New

Posted by llmblockchain 3 days ago

Ask HN: Tips for transitioning from web development to embedded/firmware?

I started my career 15+ years ago doing native development (c, c++, etc), but the last decade I've been doing fullstack web applications.

I'd like to transition closer to my roots with a job doing primarily c, c++ or rust. The natural place seems to be in embedded development or firmware work. How feasible is the transition this late in the game? Any advice?

79 points | 59 commentspage 2
mikewarot 3 days ago|
You can get started learning with any of the amazingly cheap and powerful ESP32, Raspberry Pi, Raspberry Pi Pico, and Arduino stuff out there, along with dirt cheap TANG FPGAs, etc. Get some projects under your belt in your free time. Start with the canonical blinking of an LED, and step it up from there.
oivaksef 36 minutes ago||
We have a couple of outstanding embedded developers with decades of experience.

Neither of them write a single line of code anymore.

Just be realistic about the post AI world, don't fool yourself

jon-wood 4 hours ago||
It’s totally doable, as with all things in this industry the bulk of the work is proving you can already do it before someone employs you. Build some toy projects, learn how to use embedded Rust or C, maybe write some blog posts but at the very least have some code on GitHub you can point potential employers at.

You’re also going to have to get comfortable with some level of electronics, because it’s very rare someone wants embedded development done that doesn’t interact with the outside world in some way, and that’s going to require knowing how to drive some IO.

yard2010 2 hours ago||
When I went to uni, they had this fun iot course that a company from the area ran as a hiring campaign. Ill brag shamelessly: after the course was over they tried to hire me and I politely declined to keep working in web dev. So maybe find how can you take an iot course in the nearby uni, it might be even free, I feel like this industry is small (at least where I come from) so you can make nice connections, and even if not, well at least you end up with a nice project to show.

By the way, this course was hands down the most hardcore thing I ever did. At one point I had to count high pulses for a number of c for loop ticks to read a temperature, in the process of writing the driver by hand (no AI yet), ending up with too high readings, and I couldn't debug it since it's actual pulses of electrons in the wire, once you signal it to start you can't stop it. In the end it was an off by one error, but not the usual kind, I shifted left 1 bit too much. I got stuck like 2 hours in the library trying to figure out what went wrong (I always suspect it's the hw fault, naturally), so that aha moment was really fun!

There is something special about creating something physically. I wish you make it soon and have fun!

RetroTechie 1 hour ago|
> this course was hands down the most hardcore thing I ever did

Recurring theme here on HN. It's as if programmers are scared to directly touch hardware.

I remember a thread where I explained how sending infrared remote codes worked (RC5 iirc). It was something like "set a bit on some IO port, waste a specific amount of CPU cycles, reset that IO port bit, waste some more CPU cycles. Repeat a fixed # of times, repeat that for # of bits to send".

One poster kept naggin it wasn't that simple: the bits had to be modulated on a carrier frequency. I countered "yes, high-times + low-times + CPU frequency + a # of pulses = close enough to carrier frequency. That's really all there is to it". Poster somehow couldn't believe it / wrap their head around it.

Personal view: not scary! Follow some demo project, switch your LED on, switch it off, and before you know it you have your blinkenlight. Go from there.

1970-01-01 56 minutes ago||
>Any advice?

Yes. Read a book about it, don't just jump. Amazon has dozens of them you can buy overnight if you want; https://www.amazon.com/b?node=10806604011

qazxcvbnmlp 4 hours ago||
As someone who currently does embedded, and transitioned into it with extremely little professional experience. You need to be able to demonstrate that you understand the tradeoffs that come with embedded and how you can provide value to someone who would hire you. Web development is very much a continuous integration easy to fix bugs kind of environment, in embedded bugs can have real cost.

As someone who frequently hopped around across different domains, the key is demonstrating that you understand their problems and can provide value. Also, being curious helps.

Also, today with AI am not sure how much native development is going to matter. A handful of best practices in an already set up project plus an AI agent is gonna spit out very workable code. Right now the problem space is very much about reasoning about the larger system, de bugging stuff, thinking about how pieces work together, going in the lab and connecting debuggers so that they agent can do stuff to the hardware, etc.

zergrush 3 hours ago|
> Right now the problem space is very much about reasoning about the larger system, de bugging stuff, thinking about how pieces work together

it's already being done without humans, you are already far too behind here

hingler36 5 hours ago||
IMO the single most important thing about embedded that doesn't exist in web dev is timing assurances. Juggling several competing tasks and making sure each one gets completed at exactly the right time is not an uncommon constraint in this space. My suggestion would be to pick a toy example like motor control or something and use it to learn about state machines.
rleigh 2 hours ago||
I transitioned from C++ native development at the age of 39, 7 years ago now. Haven't ever looked back; embedded development is a lot of fun and I'm constantly doing new stuff, be it exploring a new peripheral and making it work just so, or integrating lots of different activities into an RTOS and making sure the timings are still spot on. Yesterday was implementing a radix tree. Or doing mechanical design and test fixtures. There's a lot of variety, and the hands-on application of software, electronic and mechanical aspects to make working systems is very satisfying.

Not having an electronics background or an embedded background, there was certainly a steep learning curve. Lots of stuff to learn and master. But anyone who already knows C and C++, and who is prepared to knuckle down and get stuck in, will do fine.

peteforde 1 hour ago||
Most important thing is to have a passion project that you are extremely motivated to complete. I'm always baffled when folks try to learn an extremely deep domain by just watching random videos and following tutorials.

ChatGPT is an incredible engineering mentor. You can copy/paste chunks of your KiCAD schematic into the chat and it will just jump in and start recommending parts that meet the moment. Just ask it everything, and keep asking follow-up questions.

Make no mistake; you aren't just learning embedded development... you're learning electronics. That means you should get into the mindset that you'll be doing a lot of skill stacking.

If you don't know how to CAD things in Fusion and 3D print them, fix that. I'm happy to recommend an excellent tutorial video.

I recommend getting a bag of 25 of each of the ~100 most common resistor values and putting them in a bin. This will cost ~$100 and you will have all of the resistors. I cannot tell you how great this is. It's like having a jar of every spice.

Amazon has many vendors that sell plastic snap cases of capacitor values and various diodes. I have a stack of different parts. Again, all of the spices.

IMO the most underrated microcontroller is the ESP32-P4. It's a powerhouse, and a company called Wireless Tag makes a module called WT0132P4-A1. It is the bee's knees. RP2354A is also an amazing thing because it has something called PIO that will make you very happy when the time comes.

Not all breadboards are created equal. Many are terrible. Invest in BB1660.

KiCAD has become really, really good. And JLCPCB is both cheap and flexible.

If you get curious about surface mount - and you will - if you remember one thing from all this, it's to invest a few hundred in a decent STEREO microscope on AliExpress. If you give your brain the ability to perceive depth, you'll suddenly realize that you're a soldering ninja. (A Robin's Tools Pixel Pump doesn't hurt, either.)

kooi 1 hour ago|
Check out Rust with RTIC or Embassy on ESP devices. The tool chain is fairly well developed and you'll get experience with Rust and microcontrollers.
More comments...