4 ms·
Heh. Yeah, a memfault tanking the machine is not conducive to iterative programming :o)
by peterashford 2y ago
Heh. Yeah, a memfault tanking the machine is not conducive to iterative programming :o)
- lanstin 2y agoHonestly, I forgot all about that aspect of ancient programming. It probably made one more careful, or more patient. (Source: typing 6502 programs into a hex "monitor" which is a way to edit memory, view memory, and issue "jump to this memory address".)
- rob74 2y agoGuru Meditation anyone? (https://en.wikipedia.org/wiki/Guru_Meditation https://en.wikipedia.org/wiki/Guru_Meditation)
- RandomThoughts3 2y agoJust stop writing memfault. I say it in jest but that's actually how I used to program a few years ago when I was working on large industrial pieces of software with long compilation time. You just have to be careful and check what you wrote before sending it to the machine. I think "iterative" programming has made people really complacent when it comes to silly errors. Slowing down can often do wonder.
- ChrisRR 2y agoI feel like if you're writing C then writing with memory safety in mind should probably be autonomous anyway