Top
Best
New

Posted by ltratt 16 hours ago

We should be more ambitious with the software we build(danluu.com)
502 points | 432 commentspage 7
tensor 12 hours ago||
I’ve been using the latest agentic frameworks and have come to realize that the discourse around vibe coding and slop really needs more nuance.

There is a gulf of difference between someone who doesn’t understand how to program “vibe coding” software and an experienced software developer using ai to write code with heavy direction, review, and best practices.

Today both would be said to be “vibe coded” but we really need to differentiate them. Also, if everything I’m hearing from people is true, it sounds like most corporate code is now completely ai written in the latter way I described. It’s interesting we don’t hear commercial software being called slop yet. Maybe it’s coming.

In any case, ai is far more capable than I realized. Not sure what to make of it.

theturtletalks 14 hours ago||
I'm building an open-source Shopify for every vertical and built a software factory to do it. I envisioned this before LLMs, but LLMs are finally making it possible!
youngtaff 5 hours ago||
I think we should be more ambitious with the font size we use…
Lerc 14 hours ago||
>every time I see pgrust discussed on a news aggregator, most people dismiss it as vibeslop garbage because almost all of these rewrite projects are slop.

I understand being predisposed to expect a poor quality half arsed effort for projects like this. I don't really have a problem with that. There is a lot of crap out there.

What I find rather offensive is when people declare something to be poor quality and half arsed before they have taken a good look at it.

It's one thing to think something is probably crap so I'm not going to bother even looking. It is something completely different when you think something is probably crap so you tell people that it is crap without checking.

0conclusive-dem 11 hours ago||
this feels reasonable. for communities like r/selfhosted there has been an influx of new projects, many of which initially get dismissed. this more generous attitude can likely go a long way.

unfortunately though pgrust appears to be at best misleading, at worst vibeslop: https://github.com/ClickHouse/ClickBench/pull/2165 hacknews thread isn’t much prettier either https://news.ycombinator.com/item?id=50205816

ciupicri 12 hours ago||
Because it's hard to trust something. After all that's why you trust a brand more than others without trying all the products every single time. You can thank all the AI slop and kool aid promotion for the lack of confidence.
verdverm 11 hours ago||
> On looking into this, the accusations of nefarious cheating seem to be false

I think the claim is more that the Ai cheated, not Malis, and that this is evidence of eyes free coding.

I'd still like to see the actual commit history and the community getting to do their own investigation. The squashed mega commits with 1000s of files (400k files in the first commit) does not lend itself to transparency. Transparency is often the best cure to accusations. Not providing transparency upon controversy will be seen as a cover up.

han2 10 hours ago||
archived; easier to read: https://nonograph.com/we-should-be-more-ambitious-with-the-s...
generalizations 11 hours ago||
Better late than never.

Some of us have been taking this approach for literally years now.

MattDamonSpace 11 hours ago|
“Late”

ChatGPT isn’t 4yo yet. We’re just getting started

giovannibonetti 11 hours ago|
Many startups can now work in ways that were only fathomable in Big Tech before. Do you want a build system like Bazel for your monorepo? You can have it. Do you want to rewrite your app in a faster language? Sure, go ahead. Do you want to have native apps in all platforms? Yes, please.
verdverm 10 hours ago|
> Do you want a build system like Bazel for your monorepo?

I did something like this before Ai, with CUE + Dagger wrapped in a small Go binary. One problem I have seen with Ai generated projects is that they hit a limit due to conditional complexity. They have a strong tendency to add more code (local optimizations, deep if-else nesting) for edge cases, rather than stepping back to think about how to simplify problem and code.

giovannibonetti 10 hours ago|||
Funny thing, here in my company we're doing something similar, with CUE in a small Go library. You might be interested in it [1]. It generates a lot of boilerplate infrastructure code from the reference Cue files.

[1] https://github.com/bonisoft3/bayt

verdverm 10 hours ago||
Being one of CUE's biggest fans, I will definitely be interested!

I have another thing in hof that is closer to this, also CUE + Dagger

https://github.com/hofstadter-io/hof/tree/_next/examples/env

https://github.com/hofstadter-io/hof/tree/_next/lib/env

I'm gearing up for a major rewrite into a new project, based on a bunch of learning and a desire to remove a ton of cruft that accumulated over 10+ years. I still debate if I want to wrap existing tools (tf, helm, etc...) or go for a full sail replacement. Dagger handles a lot of the tooling earlier in the CI process, mainly thinking CD here. Argo-* is our bain lately...

You might find the code gen aspects of hof interesting, I opted for Go's text/template, which you can also use from CUE if you wanted to have more literate (imo) code gen in your project.

mxey 3 hours ago|||
You can cut out the middle man and use https://github.com/marxarelli/masse, a CUE frontend for BuildKit.

However I don’t think anything using BuildKit is as fine grained as Bazel.

More comments...