3 ms·

Surprisingly, for some people, the goal is the goal, and they don't care much about the journey.

by PurpleRamen 9mo ago

bandrami 9mo ago
What's the model for integration and maintenance in that case, then? Just re-create the app every time?
- Ntrails 9mo ago
  hey claude, my users have told me that their boot.ini file is missing, was that us?
- PurpleRamen 9mo ago
  Just vibe it, let AI take the lead; follow the flow, enjoy the ride and check the result. Be the manager the bot needs; those annoying details don't have to be your concern any more.
- ben_w 9mo ago
  Ask your manager how they get humans to do those things, and copy that process. So, get a bug tracker, track those bugs, tell Claude to pick tasks off it etc. I'm not claiming this actually works, I've not tried it, I don't know how good it is for large brownfield projects, but that's the general sentiment I see.
  - jermaustin1 9mo ago
    I've tried it. It can work. My prompt was "Use the gh commandline tool to get the issues for the current repository, and work on them in order, with bugs taking priority." Elsewhere there are steps for how to develop: 1. Create new branch for the feature you are working on; 2. implement the feature fully, thinking hard when you need to (toolcall think(low, med, high) switches the reasoning level); That said, it also failed a lot.
cpursley 9mo ago
I think the journey means different things to different people. Not everyone is interesting in building their own power generation plant, mining silica and forging their own chips, writing a programming language from binary. I’d love to do that stuff if I didn’t have bills to pay, but sure am quite glad to skip through the knarley JavaScript implementation details and focus on the parts I know well (backend, data modeling, translating domain specific knowledge into product) and get something to market.

3 ms·

Surprisingly, for some people, the goal is the goal, and they don't care much about the journey.

by PurpleRamen 9mo ago

Surprisingly, for some people, the goal is the goal, and they don't care much about the journey.

bandrami 9mo ago
What's the model for integration and maintenance in that case, then? Just re-create the app every time?
- Ntrails 9mo ago
  hey claude, my users have told me that their boot.ini file is missing, was that us?
- PurpleRamen 9mo ago
  Just vibe it, let AI take the lead; follow the flow, enjoy the ride and check the result. Be the manager the bot needs; those annoying details don't have to be your concern any more.
- ben_w 9mo ago
  Ask your manager how they get humans to do those things, and copy that process. So, get a bug tracker, track those bugs, tell Claude to pick tasks off it etc. I'm not claiming this actually works, I've not tried it, I don't know how good it is for large brownfield projects, but that's the general sentiment I see.
  - jermaustin1 9mo ago
    I've tried it. It can work. My prompt was "Use the gh commandline tool to get the issues for the current repository, and work on them in order, with bugs taking priority." Elsewhere there are steps for how to develop: 1. Create new branch for the feature you are working on; 2. implement the feature fully, thinking hard when you need to (toolcall think(low, med, high) switches the reasoning level); That said, it also failed a lot.
cpursley 9mo ago
I think the journey means different things to different people. Not everyone is interesting in building their own power generation plant, mining silica and forging their own chips, writing a programming language from binary. I’d love to do that stuff if I didn’t have bills to pay, but sure am quite glad to skip through the knarley JavaScript implementation details and focus on the parts I know well (backend, data modeling, translating domain specific knowledge into product) and get something to market.