Earlier quoted context omitted.
But there's a difference. Being opposed to AI-generated art/music/writing is valid because humans still contribute something extraordinarily meaningful when they do it themselves. There's no market for AI-generated music, and AI-generated art and writing tends to get called out right away when it's detected. People want the human expression in human-generated art, and the AI stuff is a weak placeholder at best. For s…
Ok, I’ll bite. What’s there to learn that you can tie directly to an increase of productivity? I can say “learn how to use vim makeprg feature so that you can jump directly to errors reported by the build and tool” and it’s very clear where the ROI. But all the AI hypers are selling are hope, prayers, and rituals.
Eight more months of agents
111–120 of 250 posts
Re: Eight more months of agents
#112Earlier quoted context omitted.
It doesn’t matter how fast you run if it’s not the correct direction.
Good LLM wielders run in widening circles and get to the goal faster than good old school programmers running in a straight line
Re: Eight more months of agents
#113> To me that statement is as obvious as "water is wet". Water is not wet. Water makes things wet. Perhaps the inaccuracy of that statement should be taken as a hint that the other statements that you hold on the same level are worthy of reconsideration.
The good old classic technically correct and completely besides the point observation.
Re: Eight more months of agents
#114Earlier quoted context omitted.
Ok, I’ll bite. What’s there to learn that you can tie directly to an increase of productivity? I can say “learn how to use vim makeprg feature so that you can jump directly to errors reported by the build and tool” and it’s very clear where the ROI. But all the AI hypers are selling are hope, prayers, and rituals.
I’m not an AI hyper, I just don’t code manually anymore. Tickets take about as much time to close as before, but the code shipped now has higher test coverage, higher performance, better concurrency error handling, less follow-up refactor PRs, less escapes to staging/prod and better documentation; some of it is now also modeled in a model checker.
Re: Eight more months of agents
#115> To me that statement is as obvious as "water is wet". Water is not wet. Water makes things wet. Perhaps the inaccuracy of that statement should be taken as a hint that the other statements that you hold on the same level are worthy of reconsideration.
The good old classic technically correct and completely besides the point observation.
Re: Eight more months of agents
#116> By far the greatest IDE I have ever used was Visual Studio C++ 6.0 on Windows 2000 Visual C++ 6 was incredible! My favourite IDE of all time too.
Re: Eight more months of agents
#117"Using anything other than the frontier models is actively harmful" - so how come I'm getting solid results from Copilot and Haiku/Flash? Observe, Orient, Decide, Act, Review, Modify, Repeat. Loops with fancy heuristics, optimized prompts, and decent tools, have good results with most models released in the past year.
Re: Eight more months of agents
#118Earlier quoted context omitted.
It doesn’t matter how fast you run if it’s not the correct direction.
Good LLM wielders run in widening circles and get to the goal faster than good old school programmers running in a straight line
There are people I work with who are deep in the AI ecosystem and it's obvious what tools they're using It would not be uncharitable in any way to characterize their work as pure slop that doesn't work, buggy, untested adequately, etc.
The moment I start to feel behind I'll gladly start adopting agentic AI tools, but as things stand now, I'm not seeing any pressing need.
Comments like these make me feel like I'm being gaslit.
Re: Eight more months of agents
#119Earlier quoted context omitted.
Curious what kind of agent did you build? I'm building a programming agent myself, it's intentionally archaic in that you run it by constantly copy-pasting from-to fresh ChatGPT sessions (: I'm finding it challenging to have it do good context management: I'm trying to solve this by declaring parts of code or spec as "collections" with an overview md file attached that acts like a map of why/where/what, but that can'…
Send an DM on twitter to @edfixyz (one of my account) and I'll reply with a link to the website tomorrow to give you a sense. Can't share a link here, it will kill my backend.