I absolutely love the degree of control you can get at the microcontroller level. One of my proudest projects had IRQ handlers written in assembly where I counted instruction cycles in order to guarantee worst-case latencies and well-defined impact to realtime activities in the main loop. There were also some lower-priority tasks going on that were cooperatively multitasked.
Some time later I wrote a JavaScript library that mimicked some of those cooperative multitasking concepts to queue background image downloads and other generic "ITasks" in a manner that maximally utilized available connections (which were extremely limited by servers back then) and allowed on-the-fly reordering. The frontend used it to always ensure whatever image the user was most interested in (i.e. tiny previews, and large version of the result presently hovered over or that we anticipate will be hovered next) came up as close to instantaneous as we could get, and the rest of the large images lazy-loaded in an intelligent order. The result was an experience that felt so much faster than how most other websites operated back then (and ironically even now as bloat has really slowed a lot of sites down), and users loved it.
So the concepts you learn at one end of the spectrum can definitely benefit you at the other.
I have much less fun now that so much of the web has moved to React and other cookie cutter frameworks where the level of control comes at a higher cost (in terms of learning curve, understanding all the layers of abstraction, and space for developer creativity).
In other words, just get in there and start playing with a personal project or two, and trust your instincts and all the experience that honed them!
My point is, whoever has actually done the transition, their experience may not really help you a lot. They might have a cousin who actually refers them to the company; They might have worked 10 years of embedded projects as a hobby; They might be lucky because 5 years ago there were a huge opening somewhere. I heard of a metaphor about elevators -- Several people ride an elevator to floor 100, and a reporter asked them how they get there -- one of them said he did 1,000 push-ups, another said he read 2 books, and a third said he bumped his head against the elevator's walls.
Those experience might be very well relevant, or not. But above all, copying others' experience, in THIS market, probably doesn't work. Now that you are 6 years senior than me regarding SWE experience, I think you already know what to do -- just do it.
I clicked on the title to write a comment saying exactly this. I didn't know anything about the experience or skills. Unless you're trying to get into Enterprise Java without knowing what a bean is, just doing it usually works.
Can't you just learn what a bean is on the spot as well?
If your question is instead how you make a career transition to embedded/firmware work, that's much trickier. The obvious concern is AI's impact on the job market, but I'm chiming in to observe that this isn't the biggest problem with a web->embedded transition. Good jobs doing embedded stuff, at least for people who don't already have a pedigree doing that work, has for as long as I can remember been a bottleneck for people wanting to do this stuff. There's simply a lot more high-level work to be done than low-level work.
I can see bright spots potentially ahead; I'm not a big Jevon's Paradox person but one kind of clearly Jevon-y area is hardware, because we've zorched one of the biggest impediments to getting new projects off the ground. But it hasn't happened yet, and might not.
Couldn’t agree more. I just had to redesign a PCB from an old client and it took me less than a tenth of the time and money that it took me to make the original fifteen years ago. What used to be $30,000 for ten assembled boards is now $2,000 shipped. Finding all the footprints and reference designs was faster than ever, what took two months end to end took a week (not including shipping wait times).
HALs and vendor libraries are in a far better state so writing the firmware felt less like slogging through a MCU reference manual and more like actual programming. LLM to do the brute forcing so that peripherals like the DMA channels play nicely together, which always burned up so much time during bringup.
Hell I was tempted to just through ESPHome on the firmware and use one of their modules with some custom C. I was dreading the redesign because I hadn’t designed any PCBs in a while but I had an absolute blast.
Just start with some cheap ESP32 boards from Amazon, a breadboard, and a wire terminal breakout for the ESP32
QFT
--former(?) embedded engineer who moved into devops
Absolutely true. I'd say it's different by a factor of 10.
But on the flip side, there are a lot fewer people with the skills and/or willingness to do embedded. So it works out to pretty steady employment, at least in my career. Be aware, though, that the smaller market can mean more time spent looking before you can find a job.
For fun - just do it. There are no barriers. Esp32, audio synthesizer gadget, cameras. Everything is cheap and available.
For the money? Expect lower pay, lower standards, worse hours and shit conditions
Embedded development has never had a lower bar to entry. There are cheap development boards, free tools, and modestly priced test equipment. Doing embedded development is entirely up to you.
Getting someone to pay for your time doing it is just the generic problem of getting someone to pay for your time doing something you would prefer to do. It depends on other people and your social capital
Who you know, how good a hang you are [1], the economics of the field, your opportunity cost and compensation requirements, etc. are what matter most. Luck aside there’s no free lunch. The place to start is your building your network. That’s hard.
[1] technical skill might or might not be a determining factor within a workplace culture.
But embedded is something else entirely that I'd argue is fundamentally incompatible with the perspective of a web dev. In embedded, you need to be aware at every moment of exactly what the CPU is doing and how many resources are being used. You generally don't have multiple CPUs or even threads. Multitasking means hardware interrupts instead of cooperative threads. You also likely need to be aware of assembly because sometimes you have to write a really hot function in raw assembly to get the required performance.
Embedded is all about resource optimization, and we dev is about throwing more and more resources at the problem. It will probably be a difficult transition to make because it's a fundamentally different way of looking at and thinking about programming.
I would recommend you find a problem, then buy the cheapest microcontroller you can find and spend a few weeks learning how to optimize your code to make maximal use of the hardware while still solving the problem in acceptable time. A big part of getting my current job was talking in my interview about how I solved a novel problem by using an obscure CPU feature in assembly that resulted in 30x fewer instructions than optimized C.
Find a problem, solve the hell out of it, and speak confidently about your solution.
One benefit that web dev does bring you is thinking about concurrency. Your CPU can only do one thing at a time, but microcontrollers have peripherals that run in parallel, and the embedded system usually consists of multiple chips talking to each other and doing independent work. Managing this concurrency efficiently with a single CPU thread is a large chunk of embedded engineering. Instead of IPC, you do things like set up a DMA pipe between SPI and RAM, trigger an interrupt on I2C bytes, use harhardware timers to simulate threads. You'd be shocked at just how much concurrent work can happen with only a single non-pipelined in-order CPU thread.
If you want to break into a new field, the advice is always the same: do the work in your own time, build a portfolio, show you know the job, and speak confidently about the hard problems you learn to solve.
The "hard" stuff you described is already being done with LLMs
Now, if you’re just over, focused on technologies and want to use a technology for the sake of using that technology, probably won’t be as easy.
Saying you want to transition to C, C++, or Rust is like a handyman saying they want to to get better with electrical tools vs plumbing tools or circular saws vs reciprocating saws. They focus on the problem than try to pick the right tool for the job.
Focus on what you want to solve, and then apply the tooling. Solve the same Problems you’ve already been solving, with your new tooling and weigh the pros and cons of both. The obvious choices will come out based on the problem at hand. The jump from web apps to firmware may be a big jump. But if you focus on a problem that interests you, and it appears those techs may be a better tooling for your task. Maybe solve it in your traditional languages first, then re apply the new stack. Or contribute to tools you’re already using, written in those stacks.
Neither of them write a single line of code anymore.
Just be realistic about the post AI world, don't fool yourself
Get comfortable with breadboards, scruffy command-line interfaces, and hex dumps. You'll need to stare at a block of raw memory, and determine the data structure, therein.
I started with embedded. It's a lot of fun, but you'll spend a hell of a lot of time, preparing the stage. You will be responsible for all the low-level stuff that a modern host OS does.
I'd actually suggest starting with pure Machine Code, first. It will make ASM look easy, and help you to really understand the processes in the chips.
Also: IRQ is The Way. It's a whole new way of looking at threading. There are absolutely no safety nets.
That said, it's been 35 years, since I did that low level work. I suspect the tools have come a long way, since.
The #1 thing to remember about firmware, is it's often a big deal to patch. It can be done, but it should not be done often.
Get in the habit of triple-checking everything. Mistakes can be rather difficult to fix.
Transitioning your skills is possible. But embedded is a different world and a different mindset. You a lot less RAM and a smaller CPU. You may have hard deadlines - the right answer can be wrong if it's too late. You may have multiple threads that have to share data and not corrupt it, no matter what order events occur in.
In the worst case, you may not have logging available at all, and you may not have a debugger. (I think the worst I ever had to do was attach a logic analyzer to the address bus, triggered by a specific address, and then use it to look at past memory addresses in order to figure out what path of execution had got me to the point of the crash.)
So, yeah. It's a different world. Learnable, but different.
Getting someone to believe you can do it enough that they're willing to pay you: I don't have great advice there. I spent almost my whole career in embedded. It seems to me that it's easier to get from there into, say, desktop programming, than it is to go the other way. Your best bet might be to emphasize your native development background, and count on there being a shortage of embedded people.
I'm sure you can make Claude help you with this .. but still..logs are important. So is a good debugger and software support for it. It saves so much time in the end.
And in my case, I was actually troubleshooting the code that makes leds blink, with a bit-banged implementation on a deterministic processor.
I recently restructure a logging module in a client’s project, and the resulting performance gains exposed all sort of race conditions.
Sometime all you get is an LED.
So... please tell us more!
This is the reality of highly constrained embedded systems. If you don't like that, I'd suggest moving to web dev where you have state of the art debugging.
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!
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.
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.
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
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.
it's already being done without humans, you are already far too behind here
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.
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.)
I started with data engineering around 2015ish purely because python was easy, and moved into frontend because I needed to make the data understandable for execs. Start building projects and showing them to people, get feedback and iterate. Nothing has changed.
don't know why everyone's acting like this is hard, seems straightforward
While they are very different, if you know C, it's not hard to transition.
Getting a job in the embedded space though is obviously a lot harder than web. There are simply fewer jobs to be had. Doing some personal projects in the space may reawaken your C skills, and help demonstrate competence.
Good luck!
If part of the reasoning is you are hoping to escape implications of AI I don’t think this will help.
Firmware, especially for the various SoCs, is not a solved problem. There’s far fewer examples of publicly available code for LLMs to learn from, and documentation is at times behind paywalls.
While I’m sure on any long enough time horizon this will change, at the moment finding useful code for some of these SoCs is a lesson in pain. I would also expect relying on an LLM for correct code for low level work like this would be a mistake at best. There are subtle bugs that you can’t shake out with code review and it takes far longer to debug embedded devices than it does web systems.
Have you done any self-directed project to further this ambition? the answer depends on your current state..
Much tech comes along, for example, I think USB-C is brilliant, and I am sure that, if I knew how to make USB-C gadgets, there would be a job there for me, albeit in China, because we don't make anything in the country I am in.
I can use USB-C now, no brain cells required, but nobody is going to give me a job because I know how to plug my phone in. Yet, if I knew the USB-C specs because RTFM, then it would be a whole different ball game, even amongst developers, where they might be adapting reference implementations rather than taking a RTFM + first principles approach.
Just saying...
This list of rules applies to most languages ( https://en.wikipedia.org/wiki/The_Power_of_10:_Rules_for_Dev... )
A bit of history where these rules came from, and why they matter.
"Why Fighter Jets Ban 90% of C++ Features" ( https://www.youtube.com/watch?v=Gv4sDL9Ljww )
The basis of the cited 10 rules helped form many standards for reliable code ( https://www.stroustrup.com/JSF-AV-rules.pdf )
The age of the legacy mcu is closing, as full blown SoC with specialized peripherals now cost about the same.
It is shite pay, naive people incorrectly assume they can write for real-time, and unless you wrote bare metal Assembly at some point in your past... you will have difficulty understanding why certain things break. esp32 are a cheap capable chip to learn on, and the Pluto course work is a great intro to the Zynq 7010 fpga hybrid Soc.
https://www.analog.com/en/resources/evaluation-hardware-and-...
The world needs Erlang/Elixir OTP devs right now as everything shitty is burning down in CVEs. Easy money if your work can take the "AI" audits and survive. =3
Primarily the transparent fail-over multi-host cluster coordination areas need cleaned up, or will likely face resiliency issues moving forwards.
>trying to get into SWE work with the AI slop
OTP languages remain operational even when other areas are under active RCE attempts. These systems usually remain operational when pinned at 100% CPU usage by a code defect, interpreter has live internal state debugging as part of the API, and are compatible with constraint programming paradigms (Erlang's list comprehension feature is somewhat functionally similar.)
The fact is daemon functionally will be more important than perfection when repo code is audited several times an hour... long before patches can be pushed out to the public.
"LLM" cannot help much in my problem domains, but are good for looking up poorly maintained documentation. Anything that lies to you 30% of the time is a waste of time, but does certainly bring out the petulant and naive. lol =3
C++/Rust/C these languages are no longer gate keepable and LLMs can write better code at greater volume and speed than a human can, so the question for a business is they would not need as much engineers, so you are competing against incumbents who are already likely in a position to be entrusted for managing LLMs when they are not looking to expand their teams, makes sense ?
The days of "renting out" your coding services is over, it's similar to how we used to have yarn spinsters that insisted on finding work even as automated systems took over in the UK industrial revolution.