1–10 of 94 posts
For context, I recently heard having a breadth of knowledge (along with depth in chosen areas) is really helpful in problem solving and I'm looking for concrete examples for the same.
Some of the "top" hospitals in the US are downright miserable to go to as a patient.
A real popular one would be QR codes. They were initially created to track manufacturing processes in the automotive industry. And you know how it is these days...
A real popular one would be QR codes. They were initially created to track manufacturing processes in the automotive industry. And you know how it is these days...
I feel like QR codes failed as a general UI tool. I get annoyed whenever I have to deal with one. They wee HUGE about 10 years ago. Now, not so much.
Earlier quoted context omitted.
I feel like QR codes failed as a general UI tool. I get annoyed whenever I have to deal with one. They wee HUGE about 10 years ago. Now, not so much.
I don’t know about other places, but they’re getting a lot of use in NYC right now as a method for viewing restaurant menus for outdoor dining.
ISO 9001 was implemented in manufacturing, and is quite popular in many circles of hell.
Also, not an industry, but I think that some mathematicians use category theory to translate insights from one domain to other.
(Trying the recipe itself here to find a meta-recipe) I think an insight itself from category theory to a more general recipe could be: don't try to move "laterally" to other industry, but go first "up" from a specific solution to a more general interpretation, and see what more you can solve "down" from there.
I suspect a big one is "regular" engineering vs software engineering. Regular engineering has schedules and (apart from the apple campus) can put up a building in a predictable amount of time. Also testing and maintenance and more.