The December 2022 issue of IEEE Spectrum is here!

Close bar

A Wider Welcome Mat

Achieving a diverse workplace should be more than a token gesture--and it may be easier than you think

6 min read

Engineering is no longer the all-white, all-male bastion it used to be. In the United States, about 20 percent of all engineering master's degree recipients are women, up from 2 percent in 1975. And African-American, Latino, and American Indian students now make up 11 percent of U.S. engineering graduates, according to the National Action Council for Minority Engineers (NACME), in White Plains, N.Y.

That said, the numbers of women and minorities who study engineering and work as engineers still don't reflect society as a whole. First-year enrollment of minority students intending to major in science and engineering actually declined significantly between 1992 and 1998--proof that creating true diversity in the workplace remains an uphill climb. And it's only going to get steeper; according to U.S. Census Bureau projections, minorities are expected to make up close to 40 percent of college student bodies by 2020. How many of them will choose engineering?

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