> and chucking out a significant chunk of work they've done
It is unclear how much of the actual work they've done is being "chucked out".
18F did work for various federal agencies, and whatever code 18F wrote for its client agencies would still be in possession of those agencies.
What happens to that code going forward – whether it continues to be maintained by other resources, or whether it just gets archived – is going to be an agency-level decision. Probably some will be kept, others will be thrown out – keeping or abolishing 18F is a separate decision from keeping or abolishing the agency-level projects/initiatives 18F was working on. (And even if 18F had survived, probably some of that code would eventually have been thrown out anyway, since government IT projects frequently end up failing and being cancelled, and 18F involvement is no guarantee against that outcome.)
Obviously, if those projects are going to be kept, removing 18F resources is going to cause a delay to the project – but maybe other resources will be found. It also depends on what percentage of the project resources were from 18F. If a project was 18F-heavy, it may take a big hit, if 18F's contribution was smaller, the negative impact might be smaller.
18F was funded out of the Acquisition Services Fund (ASF), managed by the Federal Acquisition Service (FAS) within GSA. FAS is legally obligated to spend ASF funds on federal technology modernization projects. Without 18F, FAS will have to find some other mechanism to spend those ASF funds on technology modernization. So, while of course there will be a delay, agencies which were relying on 18F may still end up getting help from GSA TTS for their modernization projects. I wouldn't be surprised if ASF funds were redirected towards DOGE, and DOGE was then tasked with working on those projects.
It is unclear how much of the actual work they've done is being "chucked out".
18F did work for various federal agencies, and whatever code 18F wrote for its client agencies would still be in possession of those agencies.
What happens to that code going forward – whether it continues to be maintained by other resources, or whether it just gets archived – is going to be an agency-level decision. Probably some will be kept, others will be thrown out – keeping or abolishing 18F is a separate decision from keeping or abolishing the agency-level projects/initiatives 18F was working on. (And even if 18F had survived, probably some of that code would eventually have been thrown out anyway, since government IT projects frequently end up failing and being cancelled, and 18F involvement is no guarantee against that outcome.)
Obviously, if those projects are going to be kept, removing 18F resources is going to cause a delay to the project – but maybe other resources will be found. It also depends on what percentage of the project resources were from 18F. If a project was 18F-heavy, it may take a big hit, if 18F's contribution was smaller, the negative impact might be smaller.
18F was funded out of the Acquisition Services Fund (ASF), managed by the Federal Acquisition Service (FAS) within GSA. FAS is legally obligated to spend ASF funds on federal technology modernization projects. Without 18F, FAS will have to find some other mechanism to spend those ASF funds on technology modernization. So, while of course there will be a delay, agencies which were relying on 18F may still end up getting help from GSA TTS for their modernization projects. I wouldn't be surprised if ASF funds were redirected towards DOGE, and DOGE was then tasked with working on those projects.