Mike Villas's World

The augmented-reality wonderland of Pyramid Hill and Fairmont High School is taking shape today

11 min read

About The Big Picture , there isn't much doubt. Sensing, monitoring, networking, and computing technologies of incredible variety and profusion will converge over the next 10 to 20 years to give us--and those who would keep tabs on us--incredible powers of observation. But exactly how it will change our lives, we can only imagine.

Some fear a simple eruption of technology-based Orwellian repression. Others anticipate the emergence of a hyperengaging form of existence based on really cool toys that (caveat emptor) spy on us every now and then. We'll drift casually in and out of augmented reality and have dizzying access to an unceasing torrent of information.

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