Met him years ago during his tenure as development lead for the original Athlon. It was interesting to hear him talk about the methodological differences between AMD and Intel. The team he led was much smaller than any that Intel could muster. Their approach was to use as much design automation as possible and skip most of the time and resource consuming manual tweaks. Consequently this would allow them to aggressively introduce new architectural innovations.
Any insider who can help to figure out whats really happening at AMD? They just released a brilliant solution for future of computing, fixed GF and IP issues with rivals and why to resign now?
Serious conflict with board or another nice magazine story ? :)
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 ...