TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

The Government's Computing Experts Say They Are Terrified

10 点作者 throwworhtthrow4 个月前

1 comment

throwworhtthrow4 个月前
This is getting aggressively flagged (last attempt to discuss this article: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=42972899">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=42972899</a>)<p>However I&#x27;d like discuss an aspect of it that I haven&#x27;t seen mentioned before:<p>How unpleasant is it for a developer to write code for ancient systems day-to-day, systems like the ones DOGE is blitzing now? (I&#x27;ve never had the misfortune of working on a 50 year old codebase.) I imagine it takes quite a while to get familiar with it, and the DOGE team is probably only working with a surface understanding. Maybe they aren&#x27;t even trying to work within the code codebase and deployments. Certainly not with an eye for future maintenance. Would future delveopers&#x27; productivity be made materially worse if someone had, say, hurriedly proxied some part of the system through nginx to crudely hack certain API calls?<p>Regardless of whether the DOGE work is legal or with honest intentions, won&#x27;t this mad dash of changes potentially make all future development on these even more burdensome?
评论 #42973982 未加载