5 ms·

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 dis

by _def 9mo ago

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.

kioleanu 9mo ago
If you build enough things, you will also gain the experience to fix those things
lawtalkinghuman 9mo ago
> 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 9mo ago
  Right but most of the time, in my experience they keep the lights on.
  - lawtalkinghuman 9mo ago
    Keeping the lights on is fine. But if they remove a feature I rely on, I can't put it back. If they add a feature I hate, I can't remove it. If they jack the price up, I have no real solution to this. If they move features I rely on from the standard tier to the 5x more expensive pro tier, I have no real solution to this. Why, yes, this is an echo of the old argument for open source software.
    - pixl97 9mo ago
      Yep. At one point I expected the software I needed to work for a reasonable time range, possibly up to a decade. Best if you could buy it once and use it from then on. Now crap has turned into revenue sucking subscriptions, at most yearly licensing, feature flutter. And the worst is being bought up by VC/PE and milked for anything useful and thrown away.
      - withinboredom 9mo ago
        > Now crap has turned into revenue sucking subscriptions So much this. Each subscription is literally a small percentage of your revenue. You can't reinvest it ... it's just gone. Hopefully it enables more productivity ... but most likely, it is only marginal.
mdrzn 9mo ago
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 9mo ago
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 9mo ago
  If it's tied to web APIs, libraries, or OS version feature APIs that are deprecated it will suddenly stop working.
  - theshrike79 9mo ago
    Non-subscription paid software will rot the same way too, so there's no change. With a agentic llms I can just tell it to fix it. With a commercial solution I'm fucked and either have to find something else or pay for a license (or keep paying every month).

by _def 9mo ago

kioleanu 9mo ago

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

lawtalkinghuman 9mo ago

> 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 9mo ago
Right but most of the time, in my experience they keep the lights on.
- lawtalkinghuman 9mo ago
  Keeping the lights on is fine. But if they remove a feature I rely on, I can't put it back. If they add a feature I hate, I can't remove it. If they jack the price up, I have no real solution to this. If they move features I rely on from the standard tier to the 5x more expensive pro tier, I have no real solution to this. Why, yes, this is an echo of the old argument for open source software.
  - pixl97 9mo ago
    Yep. At one point I expected the software I needed to work for a reasonable time range, possibly up to a decade. Best if you could buy it once and use it from then on. Now crap has turned into revenue sucking subscriptions, at most yearly licensing, feature flutter. And the worst is being bought up by VC/PE and milked for anything useful and thrown away.
    - withinboredom 9mo ago
      > Now crap has turned into revenue sucking subscriptions So much this. Each subscription is literally a small percentage of your revenue. You can't reinvest it ... it's just gone. Hopefully it enables more productivity ... but most likely, it is only marginal.

mdrzn 9mo ago

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 9mo ago

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 9mo ago
If it's tied to web APIs, libraries, or OS version feature APIs that are deprecated it will suddenly stop working.
- theshrike79 9mo ago
  Non-subscription paid software will rot the same way too, so there's no change. With a agentic llms I can just tell it to fix it. With a commercial solution I'm fucked and either have to find something else or pay for a license (or keep paying every month).