News for hackers. Stuff that matters.

A comment on U.S. National Park Service API. Parent comment

Re:U.S. National Park Service API by fritzo on Monday January 22, 2024 @09:32AM (#39089898)
A healthy diet of steady underfunding leads to humble, stable systems. We should start worrying when a team is temporarily overfunded, building out complexity in excess of their long term maintenance capability.
[ Parent | on HN ]
Re:U.S. National Park Service API by driscoll42 on Monday January 22, 2024 @10:17AM (#39090330)
Is it healthy? At one point the team was funded enough to create the api, and now it can only maintain it. What if it was never funded enough to create the api in the first place? I realize there's a risk of building complexity, but don't mistake "healthiness" for "inability".
[ Parent | on HN ]
Re:U.S. National Park Service API by droopyEyelids on Monday January 22, 2024 @11:40AM (#39091536)
This is a really interesting point and I see a lot of truth in it. But the language is imprecise- underfunding would lead to a decaying system.
[ Parent | on HN ]
Re:U.S. National Park Service API by pstuart on Monday January 22, 2024 @09:38AM (#39089953)
Emphasis on healthy.
[ Parent | on HN ]