The General Services Administration (GSA) is effectively dismantling 18F, its renowned digital services agency. While not explicitly shutting it down, the GSA is absorbing 18F into its Technology Transformation Services (TTS) and eliminating the 18F brand. This move comes as the GSA reorganizes TTS into two new offices, one focused on acquisition and the other on enterprise technology solutions, with former 18F staff being distributed across TTS. GSA Administrator Robin Carnahan stated the goal is to streamline and consolidate services, claiming it will improve efficiency and service delivery across government. However, the announcement sparked concern among many about the future of 18F's distinct agile approach and its potential impact on the agency's ability to deliver innovative digital solutions.
The dataset linked lists every active .gov domain name, providing a comprehensive view of US federal, state, local, and tribal government online presence. Each entry includes the domain name itself, the organization's name, city, state, and relevant contact information including email and phone number. This data offers a valuable resource for researchers, journalists, and the public seeking to understand and interact with government entities online.
Hacker News users discussed the potential usefulness and limitations of the linked .gov domain list. Some highlighted its value for security research, identifying potential phishing targets, and understanding government agency organization. Others pointed out the incompleteness of the list, noting the absence of many subdomains and the inclusion of defunct domains. The discussion also touched on the challenges of maintaining such a list, with suggestions for improving its accuracy and completeness through crowdsourcing or automated updates. Some users expressed interest in using the data for various projects, including DNS analysis and website monitoring. A few comments focused on the technical aspects of the data format and its potential integration with other tools.
Summary of Comments ( 4 )
https://news.ycombinator.com/item?id=43221549
HN commenters express skepticism about the claimed cost savings from eliminating 18F, pointing out that government often replaces internal, innovative teams with expensive, less effective contractors. Several commenters highlight 18F's successes, including Login.gov and cloud.gov, and lament the loss of institutional knowledge and the potential chilling effect on future government innovation. Others suggest the move is politically motivated, driven by a desire to return to the status quo of relying on established contractors. The possibility of 18F staff being reabsorbed into other agencies is discussed, but with doubt about whether their agile methodologies will survive. Some express hope that the talented individuals from 18F will find their way to other impactful organizations.
The Hacker News post "GSA Eliminates 18F" has generated several comments discussing the news of 18F's absorption into the GSA's Technology Transformation Services (TTS). Many commenters express concern and disappointment about this move.
A recurring theme is skepticism about the GSA's ability to effectively manage and nurture the innovative spirit of 18F. Several comments suggest that 18F's unique culture and agile approach to government technology projects will be stifled by bureaucratic processes and a lack of understanding within the larger GSA organization. One commenter draws a parallel to a previous attempt to integrate 18F, which they claim was reversed due to cultural clashes.
Some commenters express worry about the potential loss of talented individuals from 18F, predicting an exodus of skilled employees who were drawn to 18F's specific mission and working environment. The potential impact on ongoing 18F projects is also a concern, with some speculating about delays or outright cancellations due to the restructuring.
A few comments offer a more neutral perspective, suggesting a wait-and-see approach to judge the actual consequences of the merger. They acknowledge the potential downsides but also entertain the possibility that the GSA might successfully integrate 18F without compromising its effectiveness. One commenter mentions the potential benefits of closer collaboration with other TTS teams.
A couple of commenters question the information presented in the Nextgov article, suggesting that it might not accurately portray the situation. They point to the lack of official announcements and the possibility of misinterpretations.
Several comments delve into the historical context of 18F's creation and its role in modernizing government technology. They highlight 18F's achievements and its unique position within the government.
Finally, some comments express broader concerns about the challenges of implementing technological change within government agencies and the cyclical nature of these kinds of restructuring efforts. They lament the perceived short-sightedness of such decisions and their potential to hinder progress in government IT.