Some recent work has got me thinking about how KODA goes about designing systems. More to the point: how do systems perform when things go wrong? This week's post contains a few notes on what you can do.
You know you're working in an interesting industry when the currents of the week push you to spend a couple of late night hours searching for some 'standard' dimensions for humans to try to justify the placement of a datalogger in a certain location on site.
As a repeat reader of Frank Herbert's Dune, I've found myself intrigued by a particular phrase written towards the end of the book.
I think that the phrase intrigued me because I'd never heard of it before... A rather trivial reason for liking a statement, I know, but I think there is something more to it...
Sitting here at MeatStock, doing the dawn shift, lighting the fire and tending to our 30 day dry aged briskets I'd just laid down, I started thinking about all the different ways I could apply what I do at work to cooking a great brisket. Was this madness? Or worth the musing?