eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

241
active users

#codebase

0 posts0 participants0 posts today

What could possibly go wrong? #DOGE to rapidly rebuild #SocialSecurity #codebase.

Under any circumstances, a migration of this size and scale would be a massive undertaking, experts tell WIRED, but the expedited deadline runs the risk of obstructing payments to the more than 65 million people in the US currently receiving Social Security benefits.
#cobol #ssa #takeover #retirement #takedown #maga #trump

> sadly, most likely crash and burn

arstechnica.com/tech-policy/20

Ars Technica · What could possibly go wrong? DOGE to rapidly rebuild Social Security codebase.By WIRED

What a bunch of morons... 😤

#DOGE Plans to Rebuild SSA #Codebase in Months, #Risking Benefits and System #Collapse

"Social Security systems contain tens of millions of lines of code written in #COBOL, an archaic programming language. Safely rewriting that code would take years—DOGE wants it done in months.

Musk pointed to data he allegedly pulled from the system that showed 150-year-olds in the US were receiving benefits, something that isn’t actually happening..."
wired.com/story/doge-rebuild-s

WIRED · DOGE Plans to Rebuild SSA Code Base in Months, Risking Benefits and System CollapseBy Makena Kelly

#DOGE Plans to Rebuild #SSA #Codebase In Months, Risking Benefits and System Collapse

#SocialSecurity systems contain tens of millions of lines of code written in #COBOL , an archaic programming language. Safely rewriting that code would take years—DOGE wants it done in months.

> #deluded or #lying ? They couldn’t even handle building that website.

wired.com/story/doge-rebuild-s

WIRED · DOGE Plans to Rebuild SSA Code Base in Months, Risking Benefits and System CollapseBy Makena Kelly

“If you've ever maintained the same piece of software for more than a couple years, you'll understand how hard it is to pivot already-finished #tools to learn from #ParadigmShifts in the industry. Even if you try your hardest, it's very easy for the old way of doing things to be woven throughout your #codebase as assumptions.

As #JessFrazlle mentioned in her first post, this is why most #CAD software is not extensible. Most of them have assumptions about software that were true in 1990 but aren't anymore: that the #internet doesn't exist; that #GPUs don't exist; that clicking is easier than typing for most user interactions”

#software / #engineering / #API <zoo.dev/blog/api-first-approac>

ZooZoo: Why we’re building APIs firstAn introduction to why KittyCAD isn't a hardware design company, but rather a software infrastructure company for hardware design

Another thing to do with codebases: explore the non code files which tell fascinating stories about the projects, their authors, and maintainers.

Some examples of what can be found buried in source trees: READMEs, FAQs, design documents, screenshots, manifestos, rants, research papers and technical reports, archives of mailing list discussions, acknowledgments and credits, guides for contributors, and more.

registerspill.thorstenball.com

Register Spill · Things you can do with codebasesBy Thorsten Ball