I use speckit, and while I like the spec/clarify/plan/task/analyze/implement loop (although it can get a bit overwhelming at times), I don’t like that I have to start with writing a spec and implement it to begin with. I am looking for a more of a design phase before the spec phase, where I can talk about the overall application architecture, and then start writing specs for implementing pieces of it.

For instance, let’s say I want to build a github repo provisioner that 1. creates repos with desired setup, and 2. bulk edit repos with secret updates, yaml updates, etc. I don’t want to build both the features at the beginning. I want to first build only the create portion, and then do the bulk edit feature later on. With speckit, I can do this by only telling it to create the spec for the build portion, but later if I want to build the bulk edit portion, the whole application might need to be changed in important places, because it wasn’t a ‘planned’ feature when it was first designed. I want instead to have a design phase where I describe and maintain a doc with the whole application, and when I start the spec for the create portion, the agent can understand that this create portion is only part of a bigger application and can design/implement the create portion accordingly.

Have you come across a situation like this? how do you handle your big applications? Please advise.

  • nieceandtows@programming.devOP
    link
    fedilink
    arrow-up
    7
    arrow-down
    4
    ·
    4 days ago

    It is ‘leava all coding to agents’, but at least it’s ‘leave most of the design control to me’. I was, and still am, and old style programmer yelling at AI to get off my lawn, but like any new technology, I’m trying to do my best to learn and make best use of it so that I grow as a developer even though it is meant to ‘save money for the company’. It’s here whether I like it or not, so I’making sure I don’t lose my job because of it, while still being employable when it inevitably crashes to the ground.

    • Azzu@leminal.space
      link
      fedilink
      arrow-up
      4
      ·
      3 days ago

      It’s interesting that so many people are able to do this. For me, I’d just rather lose my job than do something I fundamentally disagree with. If I didn’t, I would just be so extremely unhappy that I couldn’t function anyway.

      Not bashing you, just pondering the differences.

      • nieceandtows@programming.devOP
        link
        fedilink
        arrow-up
        2
        ·
        3 days ago

        That would work if there is such a thing as justice in this world. The reality is that companies don’t give a shit, and you’ll be jobless clutching to your ideals. My compromise is that ok I’ll use AI and deliver stuff for you, but I’ll only do it in a way that benefits me as well. I won’t lose my identity as a python developer to use your ai.

    • QuizzaciousOtter@lemmy.dbzer0.com
      cake
      link
      fedilink
      arrow-up
      12
      ·
      4 days ago

      Lemmy might not be a good place to ask about AI unfortunately. Most people here HATE it.

      I’m 100% with you on this. I don’t love AI but I’m not going to let myself be pushed out of the field by people who cannot program, just because I don’t like something new.

      • nieceandtows@programming.devOP
        link
        fedilink
        arrow-up
        4
        ·
        3 days ago

        Glad to know there is somebody else sharing my feelings on this. Even with ai critical comments, there’s still some great comments here. I cross posted this to experienced_devs and there a bunch of useful comments there as well.