Contemplating a Dead Computer

As computers get better and better, does our attachment to them get less and less?

3 min read

It was my early morning ritual. Having pushed the button to boot my computer, I turned my attention to the waiting pleasure of steaming coffee. After a few delicious sips, I glanced at the monitor. Strangely, it was black. I pushed the button again. To my distress, this had no effect on the monitor or on the absolute quiet of my PC. I unplugged the PC, waited, and tried again, to no avail.

How could this be? Had the computer died in its sleep? It had worked flawlessly for a year, including the night before. Perhaps that first jolt of electricity in the morning had—like a too-strong cup of coffee—arrested its frantic little heartbeat.

Keep Reading ↓Show less

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

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
A plate of spaghetti made from code
Shira Inbar

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less