I wonder at the end of this if it's the still worth the risk?
A lot of how I form my thoughts is driven by writing code, and seeing it on screen, running into its limitations.
Maybe it's the kind of work I'm doing, or maybe I just suck, but the code to me is a forcing mechanism into ironing out the details, an I don't get that when I'm writing a specification.
discreteevent•13m ago
Exactly. 30 years ago a mathematician I knew said to me: "The one thing that you can say for programming is that it forces you to be precise."
We vibe around a lot in our heads and that's great. But it's really refreshing, every so often, to be where the rubber meets the road.
shinryuu•5m ago
I couldn't agree more. It's often when you are in the depth of the details that I make important decisions on how to engineer the continuation.
einpoklum•6m ago
That sounds like the advice of someone who doesn't actually write high-quality code. Perhaps a better title would be "how to get something better than pure slop when letting a chatbot code for you" - and then it's not bad advice I suppose. I would still avoid such code if I can help it at all.
OptionOfT•19m ago
A lot of how I form my thoughts is driven by writing code, and seeing it on screen, running into its limitations.
Maybe it's the kind of work I'm doing, or maybe I just suck, but the code to me is a forcing mechanism into ironing out the details, an I don't get that when I'm writing a specification.
discreteevent•13m ago
We vibe around a lot in our heads and that's great. But it's really refreshing, every so often, to be where the rubber meets the road.
shinryuu•5m ago