Also, learn Rust.
Ask HN: Going low-level – what to learn next?
11–20 of 59 posts
Re: Ask HN: Going low-level – what to learn next?
#12Re: Ask HN: Going low-level – what to learn next?
#13Re: Ask HN: Going low-level – what to learn next?
#14Re: Ask HN: Going low-level – what to learn next?
#15Re: Ask HN: Going low-level – what to learn next?
#16Re: Ask HN: Going low-level – what to learn next?
#17Some simple things you can do:
* Get yourself a suitable embedded development system - I would recommend anything ESP32'ish that suits your fancy such as a Liligo or Watchy ESP32-based watch, or PineTime if thats more up your alley - and then write some little apps for it.
* Get to know Godbolt with a great deal of intimacy, just as a general approach to understanding what is going on:
* Invest a little workbench time in some of the various embedded frameworks out there - platformio, FreeRTOS, etc. and, very important: learn the Tooling And Methodology techniques that these frameworks manifest.
* Invest some workbench time in the RETRO Computing Scene. Seriously, you can still learn extremely valuable principles of tooling and methodology from an 8-bit retro system from the 80's. Get your favourite platform, get all its tools onboard, engage with its community - you will learn a lot of things that are still entirely relevant, in spite of the changes over the decades.
* Get into the F/OSS tooling/methdology flow - find software projects that are interesting to you, find their repositories, learn to clone and build and test locally, and so on. There are so many fantastic projects out there for which low-level skills can be developed/fostered. Get onboard with something that interests you.
Good luck!
Re: Ask HN: Going low-level – what to learn next?
#18an optimizing Lua or Lisp compiler
Learning Lua is a great way to get introduced to a lot of low-level concepts, from bytecode to VM's to language design and beyond.