The conversation

SyntafHNSource author
Lessons learnedExperience excerpt · English

At my company we have a local development CLI our devX team built, it allows for agents to interact …

… At my company we have a local development CLI our devX team built, it allows for agents to interact with standing up, tearing down and managing local stacks for our software suite. When I receive customer feedback about a broken button, or a poor UX experience, I simply start up a prompt: /metal user X reported an issue on the trial balance page, they encountered a blank page when using the inception to date filter. We need to investigate the root cause, spin up a new stack, and resolve the bug. Then off to the next task, maybe some few hours later I'll check back in on the session and I'll see: > PR created: https://github.com/company/repo/pull/12758295 > QA URL: http://localhost:8400/<url> > Summary of root cause and fix: lorem ipsum lorem ipsum After a quick QA session I validate the fix, confirm that our claude reviewer has approved the PR and merge the PR to deploy. The mental burden of switching to this task is quite low, orders of magnitude lower than it would be 25 years ago.

Original discussionProgrammers need to start meditating now168 source comments · at import
2

What was this responding to?

Parent context · original excerpt

SE
senfiajHN

>> I’m clearly much more productive now. I’m doing five things at once very effectively, switching between multiple agent sessions from morning to night. Joel Spolsky disagrees here: https://www.joelonsoftware.com/2001/02/12/human-task-switche...

Full original

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 2

Direct replies available in this import. Original-language excerpts.

SK
skydhashHN

This behavior is how you get: > user X reported an issue on the trial balance page, they encountered a blank page when using the inception to date filter. It’s whack-a-mole with bugs.

Full original
FE
feanaroHN

What is also lower is your understanding of the change. So yes, if you are now essentially only doing the final mile of paper pushing for the LLM, then the mental burden is lower but so is the assurance of what has just transpired. Whether this mode of working is going to be long-term viable is going to depend on how important it is for you to be aware of what has happened for the system in question, how viable the economics are for the LLM usage at this level of assurance and how much ownership you exert over the LLM used or another similarly powered one (because otherwise the LLM can be taken away from you, leaving you at the mercy of a third party with goals that do not align with your own).

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.