A monthly overview of things you need to know as an architect or aspiring architect. Unlock the full InfoQ experience by logging in! Stay updated with your favorite authors and topics, engage with ...

At last year’s annual conference of the National Association of State Chief Information Officers (NASCIO), Julia Richman, then the deputy executive director for the Colorado Office of Information ...

Imagine launching a new digital service only to face a breach due to outdated code or an unpatched dependency. Enterprises face this more often than they admit. In today’s economy, technical debt is ...

Ask any development team about technical debt and you're likely to get a nod of recognition--followed by a shrug. It's a familiar term, but too often treated as a theoretical concept rather than a ...

Phil Goldstein is a former web editor of the CDW family of tech magazines and a veteran technology journalist. He lives in Washington, D.C., with his wife and their animals: a dog named Brenna and two ...

The United States has long struggled with managing its financial debt—borrowing beyond its means, deferring payments and accumulating obligations that eventually come due. The same holds true for ...

Clinton Austin is the director of digital outreach for the Space Force Association and a business account manager with CDW•G. Standing up new IT infrastructure on the foundation of an old one can ...

With tech layoffs at an all-time high, it's crucially important that companies identify inefficiencies and costs. While layoffs have been happening across departments, according to consulting firm ...

Addressing technical debt is essential for Federal Agencies to modernize their networks effectively. Key drivers of this technical debt include outdated devices, incomplete configurations, and legacy ...

Aging hardware, outdated software and legacy infrastructure put undue stress on IT teams, but technical debt doesn’t have to last forever. Though the buzz phrase “technical debt” might be new to some, ...

Nobody sets out to build a mess. Every firmware project I’ve walked into started with good intentions. Somebody drew an architecture diagram on a whiteboard. There were clean module boundaries. Maybe ...