Jack Ganssle

Jack G. Ganssle is a lecturer and consultant on embedded development issues. He conducts seminars on embedded systems and helps companies with their embedded challenges. Contact him at jack@ganssle.com. His website is www.ganssle.com.


's contributions
    • No, it won't be public till later in May.

    • Yes, Marcus tells me their ISP is having trouble this week. I know he and his people are working furiously to get it back up.

    • I walked into the house today and my wife told me her sister-in-law had called from the car, but suddenly, while talking, sideswiped a car, on a high bridge over a river. 5 minutes later she called again: now she was still on the bridge, still driving, following the other car and a cop to a safe spot!

    • Whoops - I screwed up. The TSI Speech+ calculator was based on the TMS1000, not the HP-35. Jack

    • For some reason I remember Goldwater's callsign - K7UGA. When he ran for president my dad had a bumpersticker that read AuH20.

    • Dan - I'll pass this on to Susan.

    • Alex - you're right! Thanks. Jack

    • I just learned that the 8X300 was used in more than 30% of fixed disk controllers for a while. So it did have some decent market share. Thanks for the correction, Eric.

    • UPDATE: A reader sent me this link (http://www.infoage.org/html/tiros1-2.html ). A group of volunteers are maintaining and improving the 60 foot dish antenna that received TIROS's signals. Fascinating site, and a worthy place to support.

    • Patrick, Good point. But I disagree about English. It's notoriously imprecise. It's like C - a tiny change greatly alters the meaning. Consider: Eats, shoots, and leaves. Vs Eats shoots and leaves. (Think panda bears) One reason we have so many problems with software is the code is derived from an imprecise English-language specification. I suppose the alternative is formal methods, but they probably won't make many inroads in the near future. Jack