NextHendrix
Joined 9 years ago
Joined 9 years ago
The floppotron
Maybe this is what you're referring to. There are similar examples where people do this with old disk drives and printers too.
HDLs have familiar syntax that makes it seem like you can just program algorithms imperatively (for loops, if statements, functions etc) but it's all just a mean trick to catch software people out, and generally won't give the results you expect.
On top there's then the fact everything happens at the same time, the faff of making everything synchronised and making sure it meets timing and fighting the frankly awful tooling every step of the way.
Once you get it, it's fine, but you have to unlearn a lot of software muscle memory and keep the actual design work (boxes and lines) almost entirely separate from the implementation (typing your boxes and lines into a text editor).
Might sound a bit niche, and it is, but even if you ignore the stuff about actually certifying stuff to fly, it has some extremely useful and interesting tidbits about how to go about running very large and highly complex hardware/firmware projects in safety critical industries.
The chapter on requirements is especially useful, and the whole thing is written in a (relatively, for the topic) light-hearted way.
Not by its inventors, but by its management-type evangelists. Which do you think the mayor had in his ear?