The December 2022 issue of IEEE Spectrum is here!

Close bar

The other day I glanced wistfully at the new desktop computers in the electronics store. The new computers weren’t much faster than my old one, the hard drives were only a little larger, and there wasn’t much else in the way of hardware that I might use to rationalize a purchase. Why, then, did I want one anyway?

In the past, the hardware was justification enough. It got better so fast that I would lament the value that was lost during my drive home from the store. I imagined that I could hear the computer sizzling into obsolescence, right there in the backseat of my car. I couldn’t countenance the thought of going back to the store the next day, for fear that I would see a big discount on the obsolete model that I had just been such a chump to buy.

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