Chip's comments illustrate a couple points I've been trying to make. One is that the question is outside just engineering decisions, it involves economics and ITS LAWS. And these laws defy national boundaries.
Also his remarks display a certain desperate helplessness. All 'must' do this, that or the other thing. Says who? Nobody's in control. It's Smith's 'Invisible Hand' gone amok.
Japan has pretty much lost the huge Consumer Electronics market in the US & W. Europe to So. Korea, Taiwan and China. If unlike Europe, Japan does not want to let go of this low margin but high volume segment, then they have to compete with So. Korea in terms of NPI, with China on the basis of price. The article mentioned something about sticking to 20 year reliability even for DRAM for throwaway Consumer products ! Thats a no no ! The Japanese must re-examine all their assumptions and quickly change course accordingly. This means faster development cycles ( more science & simulation and fewer experiments ), more robotics ( even if it causes more unemployment among factory workers - at least there will be more money from exports to retrain them in something else ). Otherwise I am afraid it would be 1945 all over again. I say this as a well wisher who has managed semiconductor projects in Japan.
While I agree that engineers might and should see themselves as free agents, reality in the semiconductor industry is that they will work for a mid-size to large company. The economics of making chips do not lend themselves to true free agency, i.e., being a consultant for one's own firm. Please let me know how I'm wrong on this b/c I'd love to throw up my own shingle.
Probably a dumb thing to say, but was there any discussion about the "overwork" culture in Japan? Having visited there a few times, I could never come to terms that tired Japanese engineers were staying in office, day after day, not going home, rarely spending time with their families - at times simply because their bosses were at office.
On an individual level, can not such pressure sap the mind of creating innovative ideas and the pleasure of working on technology?
I was most interested in reading about how Japanese engineers identify themselves with a company, in which they fully expected to devote their entire careers. So even that, like the rest of the topics covered, strikes me as something that the US and European electronics industries have already gone through.
My own "paradigm shift" when this was going on was that engineers now, in the US, are seen by their fellow engineers much more like free agents. It's your name and your reputation that matters most and that precedes you, not so much the company you happen to work for today.
I remember at the start of my career, that a more seasoned engineer told me, "You don't owe any loyalty to the company." It sounded a bit harsh at the time, but with the big layoffs in the early to mid 1990s, I could see exactly what he meant. You owe loyalty to yourself first and foremost. The company can and will lay you off at the drop of a hat, if the bottom line doesn't add up right.
I worked as a Principal Engineer in the late 80's through the early 90's at a fairly large company that rather quickly went from the industry's darling to a hopeless basket case. That was Digital Equipment Corporation (DEC).
I learned and gained experience from looking at projects from a systems perspective. After DEC failed to perform to expectations and then evaporated, I looked at that experience too, from a systems perspective.
It's on a bigger scale but I believe also that the performance of a national industry must also be seen as part of a bigger system. The article here referenced decisions by government agencies including banks.
The article raised organization, vertical as opposed distributed, etc.
My Mom the Radio Star Max MaxfieldPost a comment I've said it before and I'll say it again -- it's a funny old world when you come to think about it. Last Friday lunchtime, for example, I received an email from Tim Levell, the editor for ...
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 ...