| ▲ | giancarlostoro 11 hours ago |
| This is also how some of us use Claude despite what the haters say. You dont just go “build thing” you architect, review, refine, test and build. |
|
| ▲ | gnfargbl 11 hours ago | parent | next [-] |
| It's how most of us are actually going to end up using AI agents for the foreseeable future, perhaps with increasing degrees of abstraction as we move to a teams-of-agents model. The industry hasn't come up with a simple meme-format term to explain this workflow pattern yet, so people aren't excited about it. But don't worry, we'll surely have a bullshit term for it soon, and managers everywhere will be excited. In the meantime, we can just continue doing work with these new tools. |
| |
| ▲ | card_zero 11 hours ago | parent | next [-] | | This is an opportunity to select some stupid words that you would like to hear repeated a million times. The process is like patiently nurturing a well-contained thing, so how about "egg coding"? | | | |
| ▲ | giancarlostoro 10 hours ago | parent | prev | next [-] | | I havent quite dealt with "teams of agents" yet outside of Claude Code itself spawning subagents, but I have some ideas as to how to achieve it in a meaningful way without giving a developer 10 claude code licenses, I think the real approach that makes more sense to me is to still have humans in the loop, but have their respective agents sync together and divide work towards one goal, but being able to determine which tasks are left to be worked one and tested. I do think for the foreseeable future you will need human validation for AI. | |
| ▲ | mr_mitm 10 hours ago | parent | prev | next [-] | | I thought the term was "agentic engineering" | | |
| ▲ | giancarlostoro 10 hours ago | parent | next [-] | | I like "spec driven development" but I honestly don't care what you call it, just let me build things and leave me alone. :) | | |
| ▲ | newswasboring 9 hours ago | parent [-] | | SDD is more like a subset. There are different ways to manage context in agentic engineering | | |
| ▲ | giancarlostoro 6 hours ago | parent | next [-] | | I guess, I just know I force my agent to use a ticketing system like Beads (I made my own). | |
| ▲ | DANmode an hour ago | parent | prev [-] | | > SDD Don’t do that! On a two-day-old term?! No wonder we’re called gatekeepers. | | |
|
| |
| ▲ | simonw 10 hours ago | parent | prev [-] | | Yeah that's the top contender at the moment. I think it's pretty good. |
| |
| ▲ | gf000 9 hours ago | parent | prev | next [-] | | https://youtu.be/JV-wY5pxXLo?si=ga-9Gg8IZfU6g8Tg It's vibe engineering | | | |
| ▲ | viraptor 10 hours ago | parent | prev [-] | | I'm not sure there's going to be a term, because there's no difference from normal, good quality engineering. You iterate on design, validate results, prioritise execution. It's just that you hand over the writing code part. It's as boring as it gets. |
|
|
| ▲ | latexr 11 hours ago | parent | prev | next [-] |
| > how some of us Operative word being “some”. The issue is that too many aren’t doing it that way. > You dont just go “build thing” Tell that to the overwhelming majority of posters discussing vibe coding, including on HN. |
| |
| ▲ | danielvaughn 11 hours ago | parent | next [-] | | Sure, but they're going to be stuck writing software for yesterday's problems. As our tools become more powerful, we're going to unlock new problems and expectations that would be impossible or impractical to solve with yesterday's tooling. | | |
| ▲ | coldtea 9 hours ago | parent [-] | | >Sure, but they're going to be stuck writing software for yesterday's problems As long as they get paid for it (or have fun, if it's a personal project), they couldn't care less about that. Tomorrow's problems are overrated. |
| |
| ▲ | tonyedgecombe 11 hours ago | parent | prev [-] | | I suppose to some extent those people have always existed. The ones who would choose the most expedient solution. The difference now is they can get much further along. |
|
|
| ▲ | philipallstar 10 hours ago | parent | prev [-] |
| > despite what the haters say Thinking people who disagree with you hate you or hate the thing you like is a recipe for disaster. It's much better to not love or hate things like this, and instead just observe and come to useful, outcome-based conclusions. |
| |
| ▲ | simonw 10 hours ago | parent | next [-] | | LLMs really do attract haters in the classic sense though. You'll find them in almost every thread on here. | | |
| ▲ | jcgrillo 10 hours ago | parent [-] | | They also attract grifters, frauds, conmen, snake oil peddlers, and every stripe of bullshit artist. I'm someone you probably would view as a hater, but I truly don't hate LLMs. I hate the lies. Projects like this are interesting, I wish there was a lot more of this and a lot less of the "trust me bro" stuff. |
| |
| ▲ | giancarlostoro 10 hours ago | parent | prev [-] | | Look at any HN thread that has a project that uses AI in any way, shape or form. People quickly remark that it is slop, without even reviewing the code. If that's not blind hatred of AI, I don't know what is. There's a huge distinction between Vibe Coding, and actual software engineers using AI tooling effectively. I vibe code for fun sometimes too, nothing wrong with it, helps me figure out how the model behaves in some instances, and to push the limits of what I understand. | | |
| ▲ | mghackerlady 9 hours ago | parent | next [-] | | Vibe Coding is like porn for programmers. It probably isn't good for you, and you'd probably be better off actually doing the thing yourself, but it feels good and satisfies our desires for instant gratification | | |
| ▲ | giancarlostoro 9 hours ago | parent [-] | | Well, take for example, I have ideas I've had for years but no time for because by now the requirements are insane. I want to build a backend that could survive nuclear fallout type stuff. I braindump to Claude, watch it churn out my vision for the last 12 years, its insane. There's other things too though: my ADD and my impostor syndrome don't matter to Claude, Claude just takes it all in, so as I keep brain dumping, it keeps chugging along. I don't have to worry a bout "can I really do this?" it just does it and I can focus on "what can I do to make it better" essentially. For me it's beyond "porn coding" its basically fulfilling my vision that's been locked away for years but I've had no time to sit down and do it fully. I can tell Claude to do something, my kid comes up and asks me to go draw with them and I can actually just walk away and look at the output and refine. | | |
| ▲ | mghackerlady 7 hours ago | parent [-] | | I never said it doesn't have use cases (much like porn a lot of the arguments against are just fear mongering) just that it isn't as good as the real thing. I myself like yapping to an LLM about ideas to see how feasible they actually are before taking a crack at it |
|
| |
| ▲ | Sohcahtoa82 4 hours ago | parent | prev [-] | | > People quickly remark that it is slop, without even reviewing the code. I absolutely hate how "slop" has lost its meaning. "AI slop" was supposed to mean poor-quality content that's obviously AI-generated. But the anti-AI crowd has co-opted it to mean any AI-generated content, regardless of quality. EDIT: Or even the quantity of AI. Expedition 33 had a ton of critical acclaim and ended up winning tons of awards, yet once it was discovered that AI was used to generate some placeholder art, of which NONE of it was actually used in the final product, some people started labeling the game as AI slop. It's utterly ridiculous. So now, we can't have conversations about AI slop without starting off with making sure everyone is on the same page on what the term even means. EDIT: "Vibe coding" is suffering a similar fate. If I use AI to write some code, and I examine the code to make sure it doesn't have any obvious bugs or security issues, is that still vibe coding? |
|
|
