Comment by cuuupid

Open in a window
Comment

Comment by cuuupid

I was not a fan of Direct File (I think it could have been much better!) but it was objectively in the success bucket:

- ~$50M all-in to build which sounds egregious but is small for a government project

- mostly good outcomes

- ~4y to pilot which also sounds egregious for a single moderate-complexity web app but again is practically lightspeed for a government project

People blame it getting shuttered on Trump but this is both a misread and a fundamental misunderstanding of how the government operates. The entire federal government is deliberately paced and primarily driven by a combination of politicals, regulation, budget, Congressional policymaking, and program staffing. The hammer on this was always going to fall,

[1] Congress has maintained a "buy over build" policy since literally the Cold War. Ironically the first policy here (1965) was to buy computers from ADP instead of custom-building them. The most impactful "buy commercial" policy (1996) was also IT focused. This was literally codified in several parts of the FAR, and if we're going to be blaming admins, the Trump admin has actually weakened the FAR with the RFO and would be on the other side of this issue.

[2] This policy is also the foundation upon which IT contractors like Palantir are built, if you've ever wondered "wtf do they do" they are a commercial contractor that builds custom software for government. So agencies get their custom stuff, Congress is happy they bought commercial, and the only loser is the taxpayer who overpaid a factor of 3-5x. To their credit, Palantir is a huge improvement on the status quo, because they charge by use cases and outcomes, whereas traditional SI's operate on a staffing model and a combination of high wrap rates and perverse incentives with billable hours creates horrible outcomes and ballooning costs. Anyways, there are a lot of commercial vendors that this work "could have" gone to and didn't. It would also have been really easy for them to shop this out because this was shaped really well for GSA MAS or STARS III.

[3] When you build things internally with e.g. 18F, one agency is typically the "customer" and pays the other agency (afaik 18F program is nested under the White House). So this really sucks when they walk away; 18F earned a reputation for building things through pilot, blogging about it, puffing their cheeks in the media, sending a bill to the agency, and then running off to the next shiny thing as engineers tend to do. As an agency you save a bit of money initially but now you are left with something nobody knows how to maintain, you have to hire contractors to do it, which by nature has to be a staffing contract, and then the wrap rate alone wrecks you. This happens all the time with commercial vendors, usually when they are outsized or don't get renewed, but obviously upsetting when it happens internally.

[4] The author of this piece was part of the team and so as you'd expect this piece is exceptionally biased. The reality is that the IRS self-assessed the maintenance as low and everybody who reports on this treats this as fact when it was not a GAO estimate, which is what carries any actual weight, it was internal IRS estimates and a single independent that mainly assessed call center volume not the actual system. Not only does their reputation precede them here, but their own spend on buildout (~$30M on contractors to help) contradicts the low maintenance narrative. We may never see a GAO estimate here, but the contract would almost certainly go out to TrussWorks, all government contracting data is public and you can look up for yourself how much TrussWorks typically charges the IRS whether directly or thru ATI's vehicles as subawards.

Replies cuuupid · 2026-08-17
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. The list is kept in this browser only.

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Open the marked story in a window.
]
Open the next story in the list in place of the one in front. Back returns to it.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Open several stories to compare them, and switch between them from that bar. A window's Next story link reads on down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Pins, hidden stories, filters and layout are kept in this browser only.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.