Please create an account to participate in the Slashdot moderation system

typodupeerror

Submission+-How Much Time Does Needless Red Tape Add to Coding Changes?

theodp writes: In what will likely have both government and private sector software developers nodding knowingly, Newsweek reports that a change to reposition a logon button on an IRS web page — originally estimated to take at least 103 days to deploy — was instead completed in 71 minutes after DOGE worked with an IRS engineer to cut through the red tape.

A DOGE post on X explains: "On the http://irs.gov/ website, the 'log in' button was not in the top right on the navbar like it is on most websites. It was weirdly placed in the middle of the page below the fold. An IRS engineer explained that the *soonest* this change could get deployed is July 21st... 103 days from now. This engineer worked with the DOGE team to delete the red tape and accomplished the task in 71 minutes. See before/after pictures below. There are great people at the IRS, who are simply being strangled by bureaucracy."

So, does this strike a chord with those of you who have to jump through the hoops of various oversight boards at your organization? How much time do well-intentioned but needlessly onerous requirements of Agile, Risk, Audit, Compliance, Security, Architecture, Governance, Change Control and other groups add to coding changes?
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

How Much Time Does Needless Red Tape Add to Coding Changes?

Comments Filter:

Did you know that if you took all the economists in the world and lined them up end to end, they'd still point in the wrong direction?

Working...
close