I’m guilty of using this approach too and noticed that an (obvious?) side-effect is that I get fewer wonderful, human, “aha” moments with my colleagues.
I mentioned this at a stand-up and only then did others think about it and notice the same of themselves.
This, to me, is one of the major downsides of all this: less collaboration, more individualism
I think that's true. One caveat: If you're a solo coder like me, you almost never get to talk about implementation details with anyone who (a) understands or (b) gives a flying fuck. I'm more likely to have a meaningful convo about code structure with someone on a laptop sitting next to me at the coffeehouse. So sometimes a stand-in bot to bounce your ideas off of can illuminate corners you're missing, even if it's in some ways no operating just as a chat with yourself.
> This, to me, is one of the major downsides of all this: less collaboration, more individualism
Or put another way, it's replacing collaboration and human connection with your team with a subscription service that isolates you, makes you emotionally and cognitively dependent on the service while making your performance numbers look good. I really don't like the sound of that.
Using a cheap model, I usually spend < $1-$2 per day (on API billing) using it a model like.
- here's the problem I'm trying to solve:
- here's my initial plan for the design:
- is there anything I'm not thinking about or my plan is missing?
It'll occasionally pop out a suggestion that I like more than my original plan, or it'll give me some new angles to think through the original plan.