• 0 Posts
  • 22 Comments
Joined 7 months ago
cake
Cake day: March 18th, 2026

help-circle






  • I can not tell you how tired of seeing these vibe coded projects I am.

    You didn’t give nearly enough of a shit to write the application, why should I give enough of a shit to use it? Could you explain, in detail, line by line, what the happy path of a standard web request is in this thing? Could you walk me through the specific engineering decisions that were made and why? Could you point to the specific regions of code that reflect those engineering decisions?

    I’m beyond exhausted with these things and honestly I’ve gotten to the point where I’d like for us to ban non-codeberg repos



  • You joke but that’s basically the conclusion of both the newer agent studies and the older Xerox park study on peripheral use. Language and logic are stored in an easier to access location in the brain than the kinds of skills used in architecture and planning.

    To be clear, I’m no rube. I recognize that these are powerful tools. But I suppose my take here is that if an LLM is necessary to get rid of a lot of the boilerplate and setup for a task that indicates we should explore how we’re doing the task.

    What I want to see is using these tools not to delegate our problem solving but finding ways to enhance and accelerate it and I don’t think writing spec sheets is the answer.





  • To quote the research paper conclusion…

    Conclusion We evaluate the impact of context files on coding agent performance for four common coding agents on SWE-BENCH and the novel CTXBENCH, built from recent GitHub issues and less popular repositories containing developer-written context files. We find that all context files consistently increase the cost and number of steps required to complete tasks. LLM-generated context files have a marginal negative effect on task success rates, while developer-written ones provide a marginal performance gain, neither statistically significant. Our trace analyses show that instructions in context files are generally followed and lead to more test- ing and broader exploration; however, they do not function as effective repository overviews. Over- all, our results suggest that context files don’t improve coding agent performance, and should only contain specific additional instructions beyond what is already available in the codebase. This high- lights a concrete gap between current agent-developer recommendations and observed outcomes, and motivates future work on principled ways to automatically generate concise, task-relevant guid- ance for coding agents.

    That sounds like “Agents.MD doesn’t work” to me.

    Am I missing something?


  • This. This 1000%.

    Software is not a mass-produced commodity that has to be distributed as fast as possible. People already have a limited attention span for the features of already existing software so speed running even more does not create value.

    At some point we’re going to have to rekon with the fact that creating, reviewing, and provisioning aren’t the real bottlenecks.

    Humans using the software is the bottle neck. Humans trusting the software is the bottleneck. Humans building communities and cultures around specific tools and methodologies is the bottleneck.

    At the end of the day you’re user base isn’t going to be “AI” agents. It’s going to be people.