Hacker News
Cursor now has a mobile app for guiding your coding agent on the go
smalltorch
|next
[-]
Agentic coding sorta works for me because you can stop and test each iteration and pinpoint where something has gone wrong.
Example: I ask for a tweak, it give me 20 lines, I test for the intended behavior and keep working on those 20 lines until I'm happy with the reliability/effects of it.
But that loop itself requires a environment in which the final product will be running and takes up most the time in my expirence.
Schiendelman
|root
|parent
|next
[-]
smalltorch
|root
|parent
|next
[-]
I could see the use case for the planning stage of the build though if your out and about and have a good idea.
If you could actually build and test locally I think I would have different thoughts. For instance, if I'm building a utility script for the CLI and can run it locally it makes sense not to whipout the desktop in some scenarios.
Schiendelman
|root
|parent
[-]
ericmcer
|root
|parent
|previous
[-]
I understand the feasibility of this and sometimes in my lazier moments I skim the code changes and trust automated/manual testing to validate changes, but to just like... you don't even see what it did?
Schiendelman
|root
|parent
[-]
I honestly think good technical product managers have a huge leg up on engineers in this world.
guywithahat
|root
|parent
|previous
[-]
There's also a lot to be said about planning modes which don't write anything, but rather just generate text files to be implemented later when I can watch over the repo more closely.
preommr
|next
|previous
[-]
It's so far from the days of you should try git because it's distributed, or intellij because it has great intellisense, or vscode cuz it's fast - where the value proposition was obvious and understandable.
caste
|next
|previous
[-]
ofjcihen
|next
|previous
[-]
devsda
|next
|previous
[-]
__natty__
|next
|previous
[-]
grim_io
|next
|previous
[-]
Not for me, thanks.
But since the loopmaxxers are neither prompting nor reading anymore, it kinda makes sense.