The December 2022 issue of IEEE Spectrum is here!

Close bar

When we decided to let Spectrum Online visitors interact with six years of data from our annual R&D 100 report [see ”The R&D 100,” in this issue], we turned to IEEE member Michael Tamburro and his colleagues at Agile Partners in New York City. We didn’t find Tamburro through his company’s Web site or a request for proposal. We found him in the kitchen.

IEEE Spectrum’s editor, Susan Hassler, interviewed Tamburro for Spectrum Online’s Geek Cooking podcast back in July [/radio?01.07.07&segStart=2]. As he recounted, he started cooking in his dorm room at Cornell University, exploring the complex world of Italian cuisine while honing his engineering skills. When he and colleagues Jack Ivers and John Berry founded the software company Agile Partners in 2002, Tamburro was well into perfecting the recipe from his Italian grandmother (his nonna) for a pasta-based dessert called cruspola.

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