Moving on from 18F

Role and impact of 18F / USDS

• Described as a cross-government digital services group: designers, engineers, PMs helping agencies build/buy tech, improve services, and reduce contractor dependence.
• Many commenters see 18F/USDS as the “correct answer” to agencies lacking in-house IT capacity and to duplicated, low-quality systems.
• Visible wins mentioned: better-quality federal websites and login.gov as a modern, more secure, cheaper alternative to fragmented legacy logins.

Reasons and reactions to dismantling 18F

• Strong consensus in the thread that “cost-cutting” is a pretext; cuts target a tiny budget slice while defense and other big spends remain untouched.
• Many frame the move as part of a broader “starve the beast” strategy: defund, let systems fail, then privatize and extract profit.
• Several see this as deliberate retribution and loyalty-purging rather than efficiency, and as part of a larger “coup” or procurement capture effort.

DOGE practices and legality concerns

• The article’s account of meetings with people who would not give full names or roles alarms many: seen as a major security, insider-threat, and compliance red flag.
• Commenters note existing lawful processes for reductions in force that are being bypassed, especially for probationary staff.
• Some advise not resigning (if possible) to preserve due-process rights and potential legal claims; others note that this assumes an executive willing to obey courts, which is viewed as uncertain.

Debate over partisanship and political framing

• Dispute over calling the president “far-right”: some say it’s an accurate, non-partisan descriptor; others argue US left/right labels are fuzzy.
• One line of criticism: the author is portrayed as partisan for serving under prior administrations but resigning now; defenders counter that current dismantling is unprecedented.
• Broader “both sides vs one side worse” argument about moneyed influence and corruption remains unresolved.

Effectiveness and criticisms of 18F

• Supporters point to concrete improvements and future cost savings, especially compared to “beltway bandit” contractors.
• Critics cite Inspector General reports: financial losses, billing problems, non-billable time, misstatements around login.gov compliance, and internal mismanagement.
• Even some supporters admit 18F/USDS only captured a small share of federal IT work and say deeper procurement and budgeting reforms are needed.

Civil service, procurement, and governance issues

• Multiple comments describe federal budgeting, DFAS, and the FAR as fundamentally broken, encouraging fraud and contractor gamesmanship.
• There’s concern that removing mission-oriented civil servants and watchdogs while empowering loyalists will erode the safety net and public trust, with potential for civil unrest.
• One proposal: mandatory public service to build empathy for government work; others are skeptical that compulsion actually creates empathy.

Views on Musk and tech culture in government

• Many argue Musk is not seeking efficiency but obedience, drawing parallels to the Twitter/X takeover (rapid layoffs, hostility to internal expertise, rebranding).
• Some attempt a more charitable “steelman,” suggesting he may sincerely believe his handpicked technologists are superior.
• Commenters warn that “move fast and break things” is especially harmful in domains where stability, legality, and continuity of service are paramount.

HN and discourse dynamics

• Several note that political posts, especially those involving Musk, are frequently flag-killed on HN, with disagreement over whether that is desirable.
• Alternative venues (Reddit, fediverse) are mentioned but criticized as echo chambers.