1. 12
  1. 3

    Wow, I skimmed through the first chapter and it looks very interesting - I wonder how the whole state machine approach is reflective of designing circuits. maybe computer scientists at the time viewed formal methods as necessary because they underestimated how much computing resources could grow? Ps. That is, this looks so low-level, that I imagine teams of engineers in a space program setting. Looks so close to the metal.

    1. 2

      Oh! McCluskey algorithm! I had a little bit of nostalgia, but I can confirm this is what people study at university in Italy. It seems “useless” at first, but gives you a boost of skills for computer science that should not be ignored.

      1. 2

        Speaking of usefulness for computer science… I was doing electrical engineering (~2010) and decided to switch to computer science. But before I officially switched over I did a C++ course (last experience with C++ was turbo c++/c++builder) and I ended up doing a basic raytracer with a scene description entered in through a forth interpreter. The forth interpreter was designed directly from my courses in electrical engineering on state machines, as I hadn’t done any language parsing courses yet. Instead of using a regex like I might now, I designed a rather impressive state machine.

        Fun times school allows.

        1. 1

          Whoa, that’s great! Part of the syllabus I studied was mainly for electrical engineering courses. At first I judge that useless, but now I can not ignore this anymore.