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?
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.
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
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.
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.
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.
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.
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.
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.
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.
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!
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.
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.
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.