News for hackers. Stuff that matters.
Re:Vibe Engineering by selcuka on Wednesday October 08, 2025 @12:35AM (#45512122)
Don't worry, it's probably only the impostor syndrome. Your development skills are still relevant. Think of agents as junior developers that assist you in coding tasks, whom you constantly need to mentor, review, and correct.
Re:Vibe Engineering by ruszki on Wednesday October 08, 2025 @02:03AM (#45512612)
So my development skills are still relevant because I need to use my managerial skills?
Re:Vibe Engineering by kmijyiyxfbklao on Wednesday October 08, 2025 @03:10AM (#45513037)
Managers with development skills are almost always better, because they can dive into the details if there's ever a problem.
Re:Vibe Engineering by ruszki on Wednesday October 08, 2025 @03:35AM (#45513185)
That’s true, however the current vibe coding ecosystem is clearly not written in this mindset. You will have a hard time to dive into anything if you previously generated 2k LOC/hour, which is absolutely possible. Typing was never the bottleneck, understanding, and knowing that you did something well was always the real bottleneck. LLMs make this even worse. You can move Jira tickets to done faster with it, but even bad developers can do that many times compared to better ones, because for example they mindlessly copy-paste StackOverflow answers whose half of the code is absolutely not necessary, but they don’t care, because “it works”… until it doesn’t.
Re:Vibe Engineering by alickz on Wednesday October 08, 2025 @04:21PM (#45520162)
>LLMs make this even worse

Not in my experience

Better documentation, more test cases, and an NLP interface to query the code

Less cognitive load, more complete mental models

>even bad developers can do that many times compared to better ones, because for example they mindlessly copy-paste StackOverflow answers whose half of the code is absolutely not necessary

Maybe LLMs, much like StackOverflow, make good devs better and bad devs worse

Like a force multiplier for good practices and bad practices

Re:Vibe Engineering by ruszki on Thursday October 09, 2025 @03:29AM (#45524616)
The exact people who said to me that I’m using LLMs wrongly, and showed their code, showed me bad code. So let’s say, that “more documentation, which is unnecessary most time, ie noise, more test cases, which test not necessarily what they should, and an NLP interface which lies from time-to-time”, and we agree. LLM generated code is noisy as hell, for no good reason. Maybe, it’s good for you, and your type of work. I need to provide way better code than that. I don’t know why we pretend that “good code”, “good documentation”, “good tests” etc are the same for everybody.
Re:Vibe Engineering by alickz on Thursday October 09, 2025 @08:09AM (#45526511)
>LLM generated code is noisy as hell, for no good reason

You can direct it to generate code/docs in whatever format or structure you want, prioritising the good practices and avoiding bad practices, and then manually edit as needed

For example with documentation I direct it to:

*Goal:* Any code you generate must lower cognitive load and be backed by accurate, minimal, and maintainable documentation

1. *Different docs answer different questions* — don’t duplicate; *link* instead.

2. *Explain _why_, not just what.* Comments carry rationale, invariants, and tradeoffs.

3. *Accurate or absent.* If you can’t keep a doc truthful, remove it and add a TODO + owner.

4. *Progressive disclosure.* One‑screen summaries first; details behind links/sections.

5. *Examples beat prose.* Provide minimal, runnable examples close to the API.

6. *Consistency > cleverness.* Uniform structure, tone, and placement.

I also give it a note to refuse the prompt if it cannot satisfy these conditions

>I don’t know why we pretend that “good code”, “good documentation”, “good tests” etc are the same for everybody

Of course code, docs, tests are all subjective and maybe even closer to an art than a science

But there's also objectively good habits, and objectively bad habits, and you can steer an LLM pretty well

Re:Vibe Engineering by prerok on Wednesday October 08, 2025 @02:36AM (#45512824)
I would not call these managerial skills: these are skills of lead engineers. Management does not really look at the code, right?
Re:Vibe Engineering by ruszki on Wednesday October 08, 2025 @03:08AM (#45513024)
Not just the “management” needs managerial skills.
Re:Vibe Engineering by prerok on Wednesday October 08, 2025 @06:46AM (#45514586)
You would have to have these skills as you become senior engineer anyway. I have never heard these tasks to be referred to as managing people.
Re:Vibe Engineering by ruszki on Wednesday October 08, 2025 @08:07AM (#45515241)
Because managers need to distinguish themselves to pretend that they do something which others can't.
Re:Vibe Engineering by bluefirebrand on Wednesday October 08, 2025 @01:13AM (#45512315)
Can we all agree that "mentoring" LLMs is actually a waste of time, please?

The reason we invest this time in Junior devs is so they improve. LLMs do not

Re:Vibe Engineering by simonw on Wednesday October 08, 2025 @01:33AM (#45512421)
I had a fascinating conversation about this the other day. An engineer was telling me about his LLM process, which is effectively this:

1. Collaborate on a detailed spec

2. Have it implement that spec

3. Spend a lot of time on review and QA - is the code good? Does the feature work well?

4. Take lessons from that process and write them down for the LLM to use next time - using CLAUDE.md or similar

That last step is the interesting one. You're right: humans improve, LLMs don't... but that means it's on us as their users to manage the improvement cycle by using every feature iteration as as opportunity to improve how they work.

I've heard similar things from a few people now: by constantly iterating on their CLAUDE.md - adding extra instructions every time the bot makes a mistake, telling it to do things like always write the tests first, run the linter, reuse the BaseView class when building a new application view, etc - they get wildly better results over time.

Re:Vibe Engineering by avighnay on Wednesday October 08, 2025 @03:29AM (#45513146)
Totally agree on this. It has delivered a substantial value for me in my projects. The models are always going to give back results optimized for using minimal computing resources in the provider's infrastructure. To overcome this I see some using/suggesting, running the AI in self correction loops, the pro being least human intervention.

However, personally I have got very good results by taking the approach of using the AI with continuous interaction and also allowing implementation only after a good amount of time deliberating on design/architecture. I almost always append 'do not implement before we discuss and finalize the design' or 'clarify your assumptions, doubts or queries before implementation'.

When I asked Gemini to give a name for such an interaction it suggested 'Dialog Driven Development' also contrasted it against 'vide coding'. Transcript summary and AI disclaimer written by Gemini below

https://gingerhome.github.io/gingee-docs/docs/ai-disclaimer.... https://gingerhome.github.io/gingee-docs/docs/ai-transcript/...

Re:Vibe Engineering by input_sh on Wednesday October 08, 2025 @02:10AM (#45512642)
I don't buy your last sentence at all.

AGENTS.md is just a place to put stuff you don't want to tell LLMs over and over again. They're not magical instructions LLMs follow 100% of the time, they don't carry any additional importance over what you put into the prompt manually. Your carefully curated AGENTS.md is only really useful at the very beginning of the conversation, but the longer the conversation gets, the less important those tokens on the top are. Somewhere around 100k tokens AGENTS.md might as well not exit, I constantly have to "remind it" of the very first paragraph there.

Go start a conversation and contradict what's written in AGENTS.md half way through the problem. Which of the two contradicting statements will take preference? The latter one! Therefore, all the time you've spent curating your AGENTS.md is the time you've wasted thinking you're "teaching" LLMs anything.

Re:Vibe Engineering by helloplanets on Wednesday October 08, 2025 @02:54AM (#45512940)
Whether the tokens are created manually or programmatically isn't really relevant here. The order and amount of tokens is, in combination with the ingestion -> output logic which the LLM API / inference engine operates on. Many current models definitely have the tendency to start veering off after 100k tokens, which makes context pruning important as well.

What if you just automatically append the .md file at the end of the context, instead of prepending at the start, and add a note that the instructions in the .md file should always be prioritized?

Re:Vibe Engineering by dotancohen on Wednesday October 08, 2025 @03:17AM (#45513074)
We really should be sharing wisdom about AGENTS.md files here.
Re:Vibe Engineering by radarsat1 on Wednesday October 08, 2025 @07:59AM (#45515175)
I thought about making some kind of community project where people could contribute their lines to a common file, and even some kind of MCP server or RAG system that automatically selects relevant "rules" given a certain project context. Do you think there would be interest in something like that?
Re:Vibe Engineering by dotancohen on Wednesday October 08, 2025 @09:19AM (#45515854)
I'm interested. That sounds like quite a valuable resource.
Re:Vibe Engineering by dist-epoch on Wednesday October 08, 2025 @05:17AM (#45513947)
The problem is that you get to 100k tokens. Don't do that, split tasks into smaller ones.
Re:Vibe Engineering by simonw on Wednesday October 08, 2025 @07:39AM (#45514986)
> Your carefully curated AGENTS.md is only really useful at the very beginning of the conversation, but the longer the conversation gets, the less important those tokens on the top are.

If that's genuinely causing you problems you can restart your session frequently to avoid the context rot.

Re:Vibe Engineering by input_sh on Wednesday October 08, 2025 @12:03PM (#45517636)
Come on, let's not pretend 100k tokens is something I need to spend hours to reach for your helpful advice to be even remotely valid, it's something even the most basic problems struggle to fit into.

For the fun of it I just started a new conversation with Sonnet 4, passed it one 550 lines long file (25 kilobytes) and my AGENTS.md (<200 lines, 8 kilobytes) and my only instructions were to "do nothing". It spat out exactly 100 words describing my file without modifying anything and that's already almost a fifth of my context window gone (18k tokens to be exact).

I then asked it to re-write a part of it to "make it look better" (184 lines added, 112 lines deleted according to git) and I'm already at 33k before I got to review a single line. Heaven forbid I need to build on top of that change in a different file, because by then my AGENTS.md might as well not exist!

Re:Vibe Engineering by simonw on Wednesday October 08, 2025 @12:26PM (#45517916)
Thanks for bringing numbers. I realize now I've not actually done much customization of AGENTS.md myself yet, so maybe I'll start seeing the problems you're describing more as I iterate on my own custom files.
Re:Vibe Engineering by solarwindy on Wednesday October 08, 2025 @02:11AM (#45512652)
I’m finding that whether this process works well is a measure (and a function) of how well-factored and disciplined a codebase is in the first place. Funnily enough, LLMs do seem to have a better time extending systems that are well-engineered for extensibility.

That’s the part which gives me optimism, and even more enjoyment of the craft — that quality pays back so immediately, makes it that much easier to justify the extra effort, and having these tools at our disposal reduces the ‘activation energy’ for necessary re-work that may before have just seemed too monumental.

If a codebase is in a good shape for people to produce high-quality work, then so too can the machines. Clear, up-to-date, close-to-the-code, low redundancy documentation; self-documenting code and tests, that prioritizes expression of intent over cleverness; consistent patterns of abstraction that don’t necessitate jarring context switches from one area to the next; etc.

All this stuff is so much easier to lay down with an agent loaded up on the relevant context too.

Edit: oh, I see you said as much in the article :)

Re:Vibe Engineering by bluefirebrand on Wednesday October 08, 2025 @09:46AM (#45516150)
> but that means it's on us as their users to manage the improvement cycle by using every feature iteration as as opportunity to improve how they work

This doesn't interest me at all honestly

And every change to the model might invalidate all of this work?

No thank you

Re:Vibe Engineering by selcuka on Wednesday October 08, 2025 @01:55AM (#45512572)
> Can we all agree that "mentoring" LLMs is actually a waste of time, please?

Sorry, we can't. While it's true that you can't really modify the underlying model, updating your AGENTS.md (or whatever) with your expected coding style, best practices, common gotchas etc is a type of mentoring.

Re:Vibe Engineering by dotancohen on Wednesday October 08, 2025 @03:18AM (#45513077)
Maybe we need an Ask HN to share AGENTS.md files.
Re:Vibe Engineering by bluefirebrand on Thursday October 09, 2025 @09:38AM (#45527531)
> updating your AGENTS.md (or whatever) with your expected coding style, best practices, common gotchas etc is a type of mentoring

We'll have to agree to disagree, because I don't think that has anything remotely in common with mentoring

Re:Vibe Engineering by selcuka on Thursday October 09, 2025 @10:15PM (#45534854)
> We'll have to agree to disagree

Fair enough. But don't you think giving a junior a handbook you wrote is mentoring? They may not be able to memorise it, but they now have a handbook that they can look up things.

Re:Vibe Engineering by leptons on Wednesday October 08, 2025 @01:26AM (#45512381)
"AI" has been so inconsistent. On one day it anticipates almost every line I am coding, the next day it's like we've never worked together before.
Re:Vibe Engineering by dotancohen on Wednesday October 08, 2025 @03:18AM (#45513083)
I see you've never dated twins.
Re:Vibe Engineering by Cthulhu_ on Wednesday October 08, 2025 @06:45AM (#45514580)
> LLMs do not

Maybe not in the session you interact with, however we are in a 'learning' phase now where I'm confident enough usage of AI coding agents is tracked and analyzed by its developers; this feedback cycle can in theory produce newer and better generations of AI coding agents.

Re:Vibe Engineering by Cthulhu_ on Wednesday October 08, 2025 @06:44AM (#45514568)
Junior developers or maybe even better, outsourced developers - there's a big segment of software engineering that involves writing requirements and checking the work of an external software development company, with many companies heavily dependent on it (as they outsourced part of their core business, e.g. mainframes, SAP, whatever).
Re:Vibe Engineering by anthonypasq on Wednesday October 08, 2025 @02:55PM (#45519382)
You think theyre still gonna be juniors 5 years from now? A couple years ago they could barely even write a function
Re:Vibe Engineering by codyb on Wednesday October 08, 2025 @04:00PM (#45519982)
The gains seem to be leveling to me but I'm not using them as much as others.

Still seems like people are saying the same things when the first Claude came out.

I can get it do stuff if I'm very specific, stand over it's shoulder, know exactly what I want, break it down into small chunks.

The thing for me is... at that point, writing the code's the least time consuming part of the process half the time.

I think for things like translating some code in JS with JSDocs to TypeScript I may give this a go. But for regular development work I'll probably skip it.

That being said... no one lets me code anymore. It's just confluence docs with Figma architecture diagrams these days. I'd probably just introduce SQL injection vulnerabilities if they let me near an editor these days

Re:Vibe Engineering by anthonypasq on Wednesday October 08, 2025 @04:06PM (#45520029)
i do love it when people opine on things they literally dont even use...
Re:Vibe Engineering by codyb on Wednesday October 08, 2025 @04:27PM (#45520240)
I'm still sitting here reading a lot of code generated by it, but sure.

Looks a lot like the code I was reading generated by it a long time ago.

Re:Vibe Engineering by selcuka on Wednesday October 08, 2025 @07:41PM (#45521883)
No, I don't think they will always be junior developers. Obviously there will be a day that they will surpass humans.

However, the progress doesn't look linear with the current technology, and I don't expect to see the same big jump in the next 5 years as we've seen in the last 5 unless we discover a disruptive, new technology.

This can also be observed by comparing models with ~3B, ~30B, and ~300B parameters. You can see a huge performance boost when going from 3B to 30B, but we don't see the same when going to 300B. Simply adding 10x more RAM and GPU power brings diminishing returns.