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?

80 points | 60 commentspage 3
rozenmd 4 hours ago|
Just do it.

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.

mkozlows 1 hour ago||
Instead of saying "hey claude, I need you to build this web page for me" you say "hey claude I need you to build this firmware for me."

don't know why everyone's acting like this is hard, seems straightforward

bruce511 3 days ago||
I've done both over my career (as well as some other stuff.)

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!

dehrmann 1 hour ago||
Not advice for switching, but I've worked on both, and one interesting commonality is special cases for bug handling and vendor compatibility.
svnt 4 hours ago||
I’d ask why you want to change and what kind of embedded work? Demand is lower and more specialized. Embedded is almost a solved problem by AI in many cases. The compiler plus physics proximity to ground truth means you give the agent the tools a debugger and output access and it does a more thorough job than maybe 90% of embedded devs.

If part of the reasoning is you are hoping to escape implications of AI I don’t think this will help.

gortok 4 hours ago|
I’m not sure this is accurate, at least it doesn’t match my experience.

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.

svnt 31 minutes ago||
Maybe then it is reflective of my experience doing this that I end up working in pockets where I seem mostly useless. Meanwhile the agent is banging out similar datasheet-adjacent tedium of the nth flavor that would have had me considering hiring someone else or seeking a new job five years ago.
mirmor23 10 hours ago||
> 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?

Have you done any self-directed project to further this ambition? the answer depends on your current state..

Theodores 4 hours ago||
Try the 'Brian Eno' approach. When the early synthesizers came out, he was one of the few to read the manual for the Yamaha DX-7. Everyone else was getting the same sounds out of this synth, except for Eno. They had one-hit wonders, meanwhile, Eno's album Apollo was the start of a very long career, where RTFM was crucial to his success.

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.

coryrc 2 hours ago|
In Bluetooth, that's because nobody follows the specs because you'd break a bunch of nonconforming devices and you would get the blame. Ultimately you end up making "do I want to break this group of devices or this group of devices" decisions. You definitely aren't starting from scratch, partially because of patents butt also because the reference implementation is the only one which encodes all those legacy nonconforming variance to the spec.
samiv 1 hour ago||
Why would you go to embedded? Its mostly pain in the ass where you have stupid old as shit toolchains like gcc-euabi-foo-armwer123 based on 20 years old GCC or some utter garbage like QNX Momentics. Debugging is a pain, dev iteration is a pain where you have to continuously upload your build artifacts to the device etc.

Just saying...

Joel_Mckay 3 hours ago||
C is king on mcu with C++ for higher end chips, but most use a subset dialect compatible with janky compilers on multiple platforms.

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

AeroNotix 2 hours ago|
Can you expand on why the world needs Erlang/Elixir OTP devs? I have a decade of experience working with Erlang/OTP. I've taken a few months off and the thought of trying to get into SWE work with the AI slop that you've all gotten into fills me with dread.
Joel_Mckay 1 hour ago||
>Can you expand on why the world needs Erlang/Elixir OTP devs?

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

xesni 1 hour ago|
people here say "just do it", but i don't think that it is that simple - you have to have some background/projects etc. to even get an interview...
More comments...