hottake for post-ai clarity
monkyyy
crazymonkyyy at gmail.com
Fri Jun 5 22:26:06 UTC 2026
Im moving on from believing ai can be schizo-meta-programming, my
new bench mark for ai success isnt "how few lines of 'code' I
write" its "how few lines of code there exists *total*". **Its
not good enough that I can rant out a 10 line spec and it turns
into 100000 lines of go slop,** even tho I dont care about how
"incorrect" my tools behave at all, in fact its better the worse
it uses spec bugs and hacks I love my dlang compiler bugs(please
add more); the code is still there and I would have to read it
and understand its shortcomings to know what to blame for errors.
There are some regions I believe ai can match the best
programmer, bash scripting the 1000th version of script, the
10000th version of the website.
Use ai to learn, use ai to search, use ai to glue together tools,
use ai called from apps, use ai to structure blog posts; but it
can not and will not remove your problem solving and defining the
problem to being a small type and/or api to mostly abstract a
problem space.
Line-number maxxing is back, the industry has unlearned it, its
dumb. Apparently it isnt only about programmer time, being even
more of an extremist line-number-minimalist then I was last year
was correct and ai is hard to use to do that and you definitely
cant vibe code to less lines of code currently.
ai is verbose, it just keeps adding lines of code; it cant not
lay a foundation. And then 100000 lines of code is 100000 lines
of code and you cant actually make rapid progress ever again.
Show me how ai can consistently simplify code? Or fix an api?
More information about the Digitalmars-d
mailing list