Comment by biztos
9 days ago
They might also ask why a bunch of static CSS inside a bunch of JavaScript is hiding inside __init__.py[0] - hopefully before trying to fix some detail of the CSS.
(I'm surprised to see it actually, since my own use of Claude has mostly yielded well-structured code. But I'm not doing proper vibe-coding, more like friendly Socratic arguing with another engineer who happens to be a robot.)
[0] https://github.com/datasette/datasette-agent/blob/main/datas...
Thanks for the prod, I've extracted that script out into a separate static file: https://github.com/datasette/datasette-agent/commit/fa505b82...
(It was in Python because there were a couple of URLs that needed to be dynamically constructed by the server, but those are output as a small window.datasetteAgentJumpConfig object instead now.)
[dead]
[flagged]
> friendly Socratic arguing with another engineer who happens to be a robot
Ha! Same! Still feels like the best way to go about it, really. I know the dream is to one day remove humans from the loop... but I'll enjoy the dialectic while it still seems the most productive!
Same, I like to call it rubber duck coding (now the duck talks back!)
Edit: Now I want an LLM connected rubber duck with a speaker/microphone that sees your screen
Reminds of me of RubberDuckGPT (rubber-duck-gpt.com):
“I won't give you answers. Instead, I'll reflect your questions back to help you think more deeply about your problems.”
Totally doable and I would buy one. Only problem is that most of the time when I'm doing "SWE" stuff I'm around other people and can't have the conversation out loud.
For my own projects, I'm very happy with an outcome that is "not faster, but better" as a result of my use of generative AI.
I still hope this will be a shared goal in at least some tech companies long-term. But the headwinds are strong. "Not better, but faster" is starting to look like a job requirement.