let's start a low level academy
This Tweet was deleted by the Tweet author. Learn more
Conversation
This Tweet was deleted by the Tweet author. Learn more
Replying to
Might be interesting to start with compiling existing resources. There is already a ton of material online, just not easily discoverable. Also many different voices, disagreement on how to do things. Narrowing scope is going to be difficult.
1
This Tweet was deleted by the Tweet author. Learn more
Replying to
Examples of recreations?
I mean, tbh I'm pretty bad when it comes to re-implementing things... So I hope we mean patterns here, not code reuse.
I do see a lot of good stuff in the Rust embedded world, but have not used it in anger yet...
1
Rust takes the edge off. Gives more people access to embedded development, together with a community and some best practices baked in.
What I don't know is how do you teach someone to break out? To dive into assembler? To know when to remove printf because it's too big? Etc...
1
1
Maybe the latter is better suited for a mentoring setup and not a formal class. It is true that the need for low level knowledge would diminish if e.g. Rust is enough. I find it hard to tell because I rely on the arcane knowledge a lot during debugging for instance.
1
1
btw I have been giving this some serious consideration, but I do not think it is practically possible for me to take part, at least not yet. time being the most important factor but tbh i do not think i am stable enough in my approaches to teach basics
the embedded software / lowlevel systems programming landscape is horrible. there's so much nonsense that you just get used to. this will all need to be tought. i don't now if i want to be part of that
1
1
but if anyone is listening: debugging is the most important skill. write your programs so they can be debugged/tested. how? that is hard to convey.
also write a scheme interpreter. it will change your mind forever.
1