[_def]

I get that this is tempting but it just means you'll slowly get dependent on things that will eventually break in ways you will have no capacity to fix. And disaster recovery is most certainly a manual task.

[lawtalkinghuman]

> you'll slowly get dependent on things that will eventually break in ways you will have no capacity to fix

If the commercial provider charging you $10 a month breaks it, you also have no capacity to fix it.

Your options are: send them an email, or unsubscribe and use something else.

[hahahahhaah]

Right but most of the time, in my experience they keep the lights on.

[mdrzn]

Why wouldn't I be able to fix these things? If I managed to build a thing from scratch (with Opus 4.5), I don't see why I wouldn't be able to fix it and maintain it in the future (maybe with Opus 4.7 or even better future models?).

[theshrike79]

Why would they "eventually break"?

In what situation would a simple script or helper app just suddenly rot away and stop working?

Of course it's POSSIBLE to vibe together a massive monstrosity of an everything-app, but that's not what the author is doing here (nor me).

[figers]

If it's tied to web APIs, libraries, or OS version feature APIs that are deprecated it will suddenly stop working.

[kioleanu]

If you build enough things, you will also gain the experience to fix those things