Login
You're viewing the mastodonapp.uk public feed.
  • Oct 23, 2026, 9:51 AM

    For years, it’s been common knowledge among grant writers for open source tech that putting maintenance of existing code in a proposal can tank the whole thing.

    Funders, do you hear us now? Are you going to remember this week and let go of the new shiny object fixation?

    💬 18🔄 206⭐ 255

Replies

  • Oct 23, 2026, 12:04 PM

    to really blow some minds bring up the fact that software needs to be hosted somewhere.

    💬 1🔄 4⭐ 17
  • 💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • 💬 0🔄 4⭐ 10
  • Oct 23, 2026, 10:25 AM

    @akareilly Not always but a lot do.

    It's not remotely unique to software. International aid is plagued by rich people and corporates who want to build a new village school but wouldn't dream of paying for an existing one to have more books and teachers.

    💬 1🔄 2⭐ 23
  • Oct 23, 2026, 12:03 PM

    @etchedpixels

    I read a lot of William Easterly’s work on the subject and it resonates if you work outside of international development, too.

    💬 1🔄 0⭐ 4
  • Oct 23, 2026, 6:46 PM

    @akareilly @etchedpixels Similarly, your average mayor or governor loves to be photographed cutting the ribbon to open a new bridge or highway. Paying to maintain existing infrastructure doesn't give them that satisfaction.

    💬 1🔄 1⭐ 4
  • 💬 0🔄 0⭐ 1
  • 💬 0🔄 0⭐ 0
  • Oct 23, 2026, 11:23 AM

    @akareilly Isn't this like the public sector grants system, where it's vastly easier to get "project funding" than "core funding"?

    It's not so much that funders want something shiny and new, it's more that they want to fund something with a definite timescale, ie end date, rather than something that goes on forever.

    💬 1🔄 2⭐ 7
  • 💬 1🔄 1⭐ 1
  • Oct 23, 2026, 6:08 PM

    @wronglang @TimWardCam@c.im @akareilly I will, as the situation warrants, point people who think like this to Richard Feynman's appendix to the Rogers Commission report into the first space shuttle disaster. This specifically falls under how the shuttle's design process used a lot of new, untested, complicated technology. In addition to this the management had an entirely incorrect understanding of redundancy and safety controls.

    💬 1🔄 0⭐ 0
  • Oct 23, 2026, 6:43 PM

    @retrofan64 @wronglang

    It was also unusually cold and the launch should not have gone ahead.

    An old tree in our yard died during the freeze. I can’t emphasize enough how damned cold it was that week compared to previous launch day conditions.

    Bureaucrats who didn’t understand the technology made decisions they were not qualified to make. Sound familiar?

    💬 1🔄 0⭐ 2
  • Oct 23, 2026, 9:39 PM

    @akareilly @wronglang

    Bureaucrats who didn’t understand the technology made decisions they were not qualified to make. Sound familiar?

    Yes. Exactly why I mentioned it here. The launch would not have gone ahead if they understood that "three o rings" doesn't mean "triple redundancy". That was also why I mentioned Feynman's part of the report because he tore into the institutional/managerial incompetence which, again, was the context in which I brought this up.

    But yes. It was cold.

    💬 0🔄 0⭐ 0
  • Oct 23, 2026, 11:26 AM

    @akareilly my bet? absolutely not.

    many people think maintenance (not just code, but replication, database updating, signal refinement etc) is a silly waste of time. until it slaps them in the face. but even when the pillars of the internet are burning, they've got a new response: why do we need to pay for maintenance when "AI can do it?"

    💬 1🔄 0⭐ 4
  • 💬 0🔄 0⭐ 6
  • 💬 0🔄 0⭐ 1
  • 💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Oct 27, 2026, 6:10 PM

    @akareilly just 15 minutes ago, my professor explained that "dynamic programming" isn't a new paradigm of programming like OOP or anything really all that fancy or technical at all. They only chose the term so that it would wow the socks off of a govt bureaucrat enough to give them funding to do research on it.

    And from things i've heard, yep, that just about checks out lmfao

    💬 0🔄 0⭐ 0
  • Oct 23, 2026, 12:16 PM

    @akareilly doesn't it depends what the grant is for? If it is for Research and Development, then the funder's position is understandable. If you think that more money needs to be sent towards maintenance of existing code, that needs requests to go at senior level in the organisation to refocus priorities. Also consider semantics. Perhaps you could 'repurpose' code instead of maintaining it? Maintenance costs as part of overheads on R&D grants?

    💬 0🔄 0⭐ 0
  • Oct 23, 2026, 1:30 PM

    @akareilly Even in a lot of corps - they'll continually lay off IT staff, but then bring in contractors to build new projects and deploy new magic shiny software/appliance of the day, but then hand it over to IT to support it at the end of the project... Then IT gets hit with more layoffs. Rinse repeat, and nobody seems to understand why all these shiny new projects aren't stable and doing anything.

    💬 1🔄 1⭐ 6
  • 💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Oct 23, 2026, 4:14 PM

    @akareilly That is not limited to open source. Any lab older than 20 years I've been to has at least one corner if not a whole room of old/unmaintained equipment that could be fixed for a fraction of the cost of new shiny things. But: New shiny things ("invest") is covered by grants, fixing old things ("repairs") is not.

    That's why, for a long time already, I am convinced that this grant system is just an elaborate covert subsidy system.

    💬 0🔄 0⭐ 4
  • Oct 23, 2026, 5:17 PM

    @akareilly @pathunstrom I really want to dunk on people but my enthusiasm is deflated somewhat by realizing that we have 2 audiences; those who benefit from maintenance and fund nothing (95%) and those who benefit from maintenance but fund only new features (4%). seems unfair to dunk on the latter. (the 1% who DO fund maintenance we are eternally grateful to but it’s not nearly enough)

    💬 1🔄 1⭐ 6
  • 💬 0🔄 0⭐ 1
  • 💬 0🔄 0⭐ 0