The December 2022 issue of IEEE Spectrum is here!

Close bar

The Codemaker

Eric Hahn has been an executive, an entrepreneur, and an investor. But he’s happiest of all to call himself a programmer

15 min read
The Codemaker
Photo: TImothy ArchIbald

Eric Hahn, a geeky 12-year-old in middle school in East Hampton, N.Y., wanted a computer in the worst way. It was the early 1970s, and computers were owned by corporations and schools, not by kids, but Hahn had to try to get one. He wrote a letter to C. Gordon Bell, then the brash vice president of research and development for the mighty Digital Equipment Corp., at the time the world’s largest maker of minicomputers.

The object of Hahn’s desire was a Digital PDP-8/a minicomputer. It may be hard to remember what it was like to get excited about a computer the size of a microwave oven with 4 kilobytes of main memory and a 12-bit word length. But this was at a time when men’s sideburns were big, women’s shoes were high, and Donny Osmond and the Carpenters ruled the airwaves.

Keep reading...Show less
{"imageShortcodeIds":[]}

This article is for IEEE members only. Join IEEE to access our full archive.

Join the world’s largest professional organization devoted to engineering and applied sciences and get access to all of Spectrum’s articles, podcasts, and special reports. Learn more →

If you're already an IEEE member, please sign in to continue reading.

Membership includes:

  • Get unlimited access to IEEE Spectrum content
  • Follow your favorite topics to create a personalized feed of IEEE Spectrum content
  • Save Spectrum articles to read later
  • Network with other technology professionals
  • Establish a professional profile
  • Create a group to share and collaborate on projects
  • Discover IEEE events and activities
  • Join and participate in discussions

IEEE President’s Note: Looking to 2050 and Beyond

The importance of future-proofing IEEE

4 min read
Photo of K. J. Ray Liu
IEEE

What will the future of the world look like? Everything in the world evolves. Therefore, IEEE also must evolve, not only to survive but to thrive.

How will people build communities and engage with one another and with IEEE in the future? How will knowledge be acquired? How will content be curated, shared, and accessed? What issues will influence the development of technical standards? How should IEEE be organized to be most impactful?

Keep Reading ↓Show less

The Device That Changed Everything

Transistors are civilization’s invisible infrastructure

2 min read
A triangle of material suspended above a base

This replica of the original point-contact transistor is on display outside IEEE Spectrum’s conference rooms.

Randi Klett

I was roaming around the IEEE Spectrum office a couple of months ago, looking at the display cases the IEEE History Center has installed in the corridor that runs along the conference rooms at 3 Park. They feature photos of illustrious engineers, plaques for IEEE milestones, and a handful of vintage electronics and memorabilia including an original Sony Walkman, an Edison Mazda lightbulb, and an RCA Radiotron vacuum tube. And, to my utter surprise and delight, a replica of the first point-contact transistor invented by John Bardeen, Walter Brittain, and William Shockley 75 years ago this month.

I dashed over to our photography director, Randi Klett, and startled her with my excitement, which, when she saw my discovery, she understood: We needed a picture of that replica, which she expertly shot and now accompanies this column.

Keep Reading ↓Show less

Learn How Global Configuration Management and IBM CLM Work Together

In this presentation we will build the case for component-based requirements management

2 min read

This is a sponsored article brought to you by 321 Gang.

To fully support Requirements Management (RM) best practices, a tool needs to support traceability, versioning, reuse, and Product Line Engineering (PLE). This is especially true when designing large complex systems or systems that follow standards and regulations. Most modern requirement tools do a decent job of capturing requirements and related metadata. Some tools also support rudimentary mechanisms for baselining and traceability capabilities (“linking” requirements). The earlier versions of IBM DOORS Next supported a rich configurable traceability and even a rudimentary form of reuse. DOORS Next became a complete solution for managing requirements a few years ago when IBM invented and implemented Global Configuration Management (GCM) as part of its Engineering Lifecycle Management (ELM, formerly known as Collaborative Lifecycle Management or simply CLM) suite of integrated tools. On the surface, it seems that GCM just provides versioning capability, but it is so much more than that. GCM arms product/system development organizations with support for advanced requirement reuse, traceability that supports versioning, release management and variant management. It is also possible to manage collections of related Application Lifecycle Management (ALM) and Systems Engineering artifacts in a single configuration.

Keep Reading ↓Show less