The Microprocessor is 50

Andy Kessler, writing in the WSJ, notes that the Intel 4004 microprocessor was introduced to the market on November 15, 1971.

Here’s a history of the project, and here’s an article which describes some of the related projects that were going on at other companies.

Busicom’s decision to give Intel the rights to sell the 4004 for non-calculator applications in exchange for a break on prices–rather than royalties or equity or warrants in Intel–has to rank as one of the most expensive business mistakes ever.

 

Dangers of National Dependency

I recently read a history of the French Air Force–The Rise and Fall of the French Air Force, Greg Baughen–which includes much analysis of aircraft design and construction.   One historical fact I thought was interesting: in 1939, the French licensed the design of the Rolls-Royce Merlin engine (the engine that powered the Spitfire and Hurricane, among other airplane) and contracted with the Ford Motor Company to manufacture these engines.

But when war was declared on September 3 of that year,   Henry Ford–who had strong neutrality and ‘antiwar’ beliefs–pulled the Ford equipment and people.   No Merlins for you, Mr Frenchman!

Closer to our own time, during the Iraq War, the Swiss company Swatch Group refused to supply contracted components for the JDAM missile.   In this case, there was a US company that could provide the items, and the Swiss refusal was ultimately overcome by diplomatic pressure.

In this retro-reading post, I cited an old copy of Mechanical Engineering magazine, which discussed the shortage of certain chemicals for which the US was largely dependent on Germany:

America did not make much progress (with aniline dyes) owing to certain complications and the lack of consolidated action.  What was produced here was in most cases equal to the imported product, but owing to the greater facilities for producing the color, the greater attention given to research, substantial government financial aid, and, primarily, the exceedingly low labor cost abroad, competition was out of the question.  Hence up to 1914 we had practically no dye industry and depended on Germany not only for dyes but also for many valuable pharmaceutical preparations as well as for phenol, the basis for many of our explosives.  

This problem was solved by intensive efforts during the First World War.

Prior to 1914, most people, including government people, probably thought (if they thought about it at all), “Well, dye for fabrics isn’t exactly a strategic resource…sure, we like wearing & seeing attractively-colored clothes, but it’s not really a matter of life and death”…but missed the connection to the pharmaceuticals and the explosives.

If we do wind up in a military conflict with another major power, the time constants are likely to be relatively short–more comparable to the time pressures the French faced in 1940 than to our situation in 1914, separated by oceans from any immediate threat to the country.

And today, we have a report on US companies investing significantly in Chinese semiconductor companies and related software providers.

Worthwhile Reading

A teacher’s experiences in an American high school…a highly-rated American high school…with thoughts on the power of incentives.

Related: the effects of easing up on school troublemakers.

Research suggests that CEOs born in “frontier counties with a higher level of individualistic culture” are more effective at promoting innovation.

The market value of Tesla…$1.2 trillion…now exceeds the market value of the entire S&P 500 energy sector.   (The components of that sector can be found here.)

“Believe the science”, bureaucracy, speed, and creativity:   America needs a new scientific revolution.

Planning is a bigger job than planners can do.

Offshoring is not just for manufacturing jobs: Teleshock.   See also my 2019 post Telemigration.

Interesting memoir by a woman who started as a clerk for Burlington Northern Railroad, worked her way up to Yardmaster, and then worked closely for many years with the legendary RR executive Hunter Harrison, focusing mostly on improved data and methods for performance measurement and operational support.   (The author has since made a major industry & career change and is now focused on bioinformatics research related to cellular development!)

 

What Would You Do if You Were Running Greyhound?

Greyhound Lines is being acquired by the German company FlixMobility at a cost of $78MM…which seems small for a storied company with a well-known brand name which still provides important services in a lot of places…but I haven’t looked at the financials.   Certainly a much lower number than the 2007 acquisition of the Dog for $3.6 billion.

So, what should FlixMobility do with this property in the current market, economic, and technology environment?

Hiring, Algorithms, and Criteria

A lot of businesses are pretty desperate to fill open positions.   Pay rates are being increased, and hiring bonuses are being offered.   Yet at the same time, the software that frequently intermediates between candidate and company is often structured and configured in a way that does nobody any favors. (except, perhaps, the vendors of such software)

Over-specification of job requirements is a   frequent problem…some hospitals, for example,  have scanned the resumes of nurses for ‘computer programming’ skills when what they really wanted was someone with data entry experience.   Years ago, the WSJ ran an article on overspecification, featuring the quote “Companies are looking for a five-pound butterfly. Not finding them doesn’t mean there is a shortage of butterflies.”   As an example, it mentioned a company that makes automobile bumper parts and was looking for a factory shift supervisor. They eliminated all candidates who didn’t have a BS degree, even though many had relevant experience, and also insisted on experience with the specific manufacturing software that was in use at the plant. It took six months to fill this job (during which time the position was being filled by someone who wouldn’t ultimately be chosen for it.) Another company, Wabtec, which makes components for railcars and buses, insisted on knowledge of a specific version of the computer-aided design system it uses, even though the differences between that version and the earlier version were not all that great.

It’s a basic reality of life that you can’t optimize everything at once. So, if you insist on a perfect fit for certain things, you are probably getting less of some other attributesand these may be ones that matter more. I’d personally rather have a salesman who has demonstrated (for example) skill at managing the customer politics in a large and complex sale than one who has specific experience with the Snarkolator CRM system. It’s a lot easier to train for the second than for the first.

Similarly, if a newly-hired mechanical engineer doesn’t work out, the cause will probably not be his lack of experience with the latest version of a CAD system. More likely, it will be a lack of good design intuition…or poor interpersonal skills…or an inability to integrate mechanical design with electrical and electronics aspects of the same product…or fit with the cultural style of the organization. Maybe he comes from an environment where he was closely supervised, and the new environment is more open and requires more self-starting…or vice versa. These things are not easily represented in “checklist” form, as is knowledge of a specific software package and version, but they matter a lot.

But…in addition to the overspecification problem…I think it’s a fallacy to believe that an algorithm, at the current state of the art, can reliably look at someone’s resume to decide whether or not   they have a good shot at meeting the needs of the job. (Some programs are even looking at the applicant’s photograph, which opens the door to all kinds of problems.)   It’s hard enough for a sharp HR person (some of them do exist) to understand the needs of the hiring manager well enough to screen resumes appropriately, let alone expecting an algorithm to do so.

Someone I know recently applied for a job for which she seems to be an excellent fit.   The hiring software used by the organization sucked in her resume, formatted it to meet that software’s standards, and displayed the result.   It didn’t really communicate what she wanted communicated…she had published several articles that were very relevant to the potential employer, but whoever wrote the software had apparently never thought about ‘published articles’ as a potential hiring factor, and she had to wrestle with the software for some time to get them included.

Once a resume passes initial screening, there are also some malign trends related to the interview process itself.   In an seemingly-increasing number of cases, companies are requiring candidates to be interviewed by an unreasonable number of people…as many as 8 or 10, apparently.   Still worse, there are companies which will reject a candidate if any of the interviewers disapproves of them.   This is a guaranteed way to enshrine mediocrity and groupthink.

Employers do indeed have a real problem in dealing with the absolute flood of resumes that they get for just about any position–but need to be careful not to throw the babies out with the bathwater.   Hiring decisions are absolutely critical in any organization–‘personnel is policy’–and have huge impacts on productivity, innovation, and growth.