6,000 years of supply chain logisticssite_graphlogo
  -   Terms of Use and Privacy
Lucius | Operations | Virus
cutup   rss
6,000 years of supply chain logisticssite_graphlogo
  -   Terms of Use and Privacy
Lucius | Operations | Virus
cutup   rss

<<   <   >   >>

2020-10-11 | Virus | Messages

I normally write dreams up at mudhut, but this is more luvcounter, so, there ya go. I dreamed that I was sequencing my build, and the build sequence was in the form of messages. That was probably four hours ago that I woke up, so my details are weak. I attempted to write it down, but my journal was broken because of some modifications I made to the man.py software. The more important thing, though, is that as I considered the dream, I quickly jumped to the idea that in my case the written word was knowledge, so the messages were structured and towards a goal, but in McLuhan's case, there was something fundamentally different about the world view I am subscribing to.

I have his book Understanding Media, and have wanted to read it for many years, but just haven't found the time to read it. Plus, now I have to read Schulz's book Being Wrong too... but I have so much to do!!! Sigh...

One thing that really struck me this morning, is how flexible OWA is, particularly from an operations perspective. While it is true that the build sequence for the OS is linear overall, I can still reorder, document, and look at bits of the tree. Ultimately, the whole is pushed to sources under websites. This is also where I point my Recoll local search. I can work on the build, and while it is compiling, I can bring up another instance of MCJ to research later dependencies. Also, I can do a search on the previous steps to see if I've already compiled it. At the time I'm writing this, I have 240 build steps. I may end up at 500 or even more by the time I hit libwx_gtk3_webview-3.

knowledge mcluhan