Posted by llmblockchain 3 days ago
Ask HN: Tips for transitioning from web development to embedded/firmware?
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 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