The December 2022 issue of IEEE Spectrum is here!

Close bar

On stage, the dashing tenor Roberto Alagna pours out his love for the dark-eyed soprano Anna Netrebko, and she responds in kind. As the star-crossed lovers in the Metropolitan Opera's Roméo et Juliette , the pair sing with a fiery passion that would melt a stone.

But a few hundred meters away, sitting in a truck parked outside the Met's loading dock, television engineer Mark Schubin isn't moved. He's intently monitoring a huge bank of monitors and audio/video equipment, checking that the voices and instruments are all within range, that the audio and video feeds are open, and that everything technological about the otherwise gloriously overwrought performance is calm, quiet, and normal.

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