Such mess indicates 'disorganization' and related 'inefficiency' (drag and impeded progress) to me in most cases. Hey, where is that damn 'xxxxxxx' I need and been searching for all day and where can I find it if we even have one? I've entered some extremely messy development lab and seen it all. Personally cleaned up and organized the lab for 4 weeks and started (continued) a manufacturing process development with results and success within one year and this after 4 years of neglect, frustration and failure by the previous 'undisciplined' R&D crew.
Agree. A messy lab means real work is being done. Always question a clean engineering desk. If the research in room temperature levitation properties helps us get flying cars, then I'm all for keeping the lab as messy as possible.
A messy lab like that means job security. Who would be able to make heads or tails out of it that is not intimately familiar with "the layout". (I am joking and agree that a messy desk or lab usually means a lot is going on).
Very interesting stuff. Thanks for sharing the views.
The lab doesn't look messy to me, it simply looks jam packed. Wires, cables, etc are not bundled up, making their access and debugging easy and adding flexibility. However, I'm guessing that there is a lot of old "junk" in those cabinets in the background...
some old folks of IBM lab should switch to a college or sth instead of hanging around and squeezing out nonsense.
this one i'm not 100% sure, but for the other IBM achievement --the 10k nanotube microchip, I can tell you safely it's a piece of junk, completely hoax.
These vacuum deposition are notorious for lots of pipes and cables.
At one point, IBM actually had to excavate out a space below the floor of one of the systems to maintain it and add some capabilities to the chamber.
this is a warehourse indeed.
these equipments are not dependent /connected, ie. they don't have to be packed so close.
Is IBM lab so short of space? maybe, or maybe they just want to wow those outsiders.
If you take any fab tool's cover off it will look same or more complex.
this just shows how inexperienced Rick is.
A Book For All Reasons Bernard Cole1 Comment Robert Oshana's recent book "Software Engineering for Embedded Systems (Newnes/Elsevier)," written and edited with Mark Kraeling, is a 'book for all reasons.' At almost 1,200 pages, it ...