HN

Comments (60)

• Menu

  noelwelsh
  I wish people would describe in more detail the tasks they use LLMs to code. My experience is that simple components in an existing architecture are fine, but anything requiring architectural considerations quickly becomes a mess. On my projects (e.g. a ui framework), running multiple agents in parallel would just increase the speed at which it can stuff up the project.
• Menu

  gnunicorn
  Interestingly, despite it being much more detailed and a lot more process and procedure than what I currently do - which is more akin to the version 0 described, but in parallel - we come up at the same final problem: reviews and quality assurance.I sign off the code I merged, part of company policy but also just to be sure it is actually decent. But reviewing has become the real draining bottleneck: even stacked PRs, if that total 5-6k lines is not a 5min job. Even if I brainstormed and set the plan, that's really the part that doesn't scale right now for me in this. But the author is very shy about that: either the changes arent that big in the end or they trust the process enough to review in a more casual manner. Being equally untrusting I can't do that ...
• 2001zhaozhao
  Good writeup. I think the main difference in my workflow is that I skipped the sandboxing part and accepted the coding agent having access to the entire 24/7 dev machine, so I'm still running on worktrees. Also, the "idea enrich" steps in my workflow are less formal - I tend to write most details in a feature spec myself. I also do my workflow on my own self-hosted custom interface which comes with a kanban board for project tracking, so I don't need Github. The rest of the workflow looks pretty similar.
• saint-evan
  *siiiighhh... Slop automation. Removing self from loop, automating brainstorming. It's madness. No way that code is any good, shippable beyond 2 users or even maintainable beyond auto-slapping on more slop. Sad.
• brcmthrowaway
  More Yegge tier psychosis.
• pydry
  >Automating myself out of development>I want to start by saying that I’m neither an AI-fanaticKind of like saying you are a fanatic before saying you aren't.I don't think theres too much here (e.g. "spec driven development") I haven't seen elsewhere.
• anon
  undefined
• Menu

  general1465
  I am completely calm regarding AI and development.First nobody sane want to give their domain IP to OpenAI/Anthropic. That's why local AI will eventually prevail and flourish because people who actually have some IP will have no problem to buy 10k+ EUR machine to run some pretty good models on it. However if your main job is just doing CRUD stuff, then you are screwed.Secondly hallucination is really Achilles heel of every LLM. Sure you can recreate an application which exists in thousand of variations on the internet, but the moment you will try to go more into domain knowledge you will start struggling more and more.Try to make CAN driver for ESP32, easy it is probably going to work. Try to make CAN driver for STM32F7xx now the AI will start having a problem but probably will be able to produce something what is working after a lot of debugging. Now let's make CAN driver for MPC5555. AI will start writing fairy tales about registers which do not exist. All of processor above have reference manuals and sometimes example git repositories available on open internet.
• Menu

  yieldcrv
  I don't know if I’m overly critical but there’s gotta be a middle ground between totally AI pilled people that otherwise have no talents, and control freak veteran developers who cant let goMy current process is also using Github projects in a normal scrum style way, with many tickets written or fleshed out and state managed by the LLM, and it doubling as the memory systemCompletely leapfrogging all these other open and closed source concoctions and being more effectiveBut its effective enough that I don’t need OP’s final form state of still approving everythingAuto-mode is fine. Worktrees are built into Claude Code now. I just tell it to classify tickets as sequential or parallel possible and spawn subagents to tackle all of the tickets in the todo listThey all get their own context window its pretty perfect nowin the meantime I work in a couple tabs of Claude Design for different flows of any client side app. My philosophy has been that devs could pick up graphic and UI/UX design easily, its just still a full time job to make variations of layouts and portray their states.UI/UX is not a full time job anymore.And I use Claude chat to flesh out aspects of the overall ideaI think you may be overcomplicating your workflow in the concluding state.Overall I agree that planning and intention is now most of the time, before a 10 subagent precision strike is initiated
• chattermate
  [flagged]
• flo_r
  [dead]
• uuuuunnnuuu
  [dead]
• yuuuuuwuu
  [flagged]
• uyhgbbhakusho
  [flagged]
• uyhgbbhakusho
  [flagged]
• Supermancho
  [flagged]