The code is the documentation. There's no need for most of this stuff.
638 karma · joined April 7, 2020
The code is the documentation. There's no need for most of this stuff.
All this stuff is LLM rube goldberg machines. It just pollutes context.
I barely use AGENTS.md/CLAUDE.md these days. And where they remain, it's super basic high level stuff.
I'm honestly still kicking myself in the ass on many projects where I did something similar to this. I kept tons of markdown docs and decision docs. Now those things are just causing problems because they got stale. Even after having sessions of reconciling documentation, the LLM just gets confused.
There's always been vendor lock-in. Someone has to implement technologies to the standards, those are most of the time commercial interests.
Apache vs nginx, rhel vs debian, spring vs j2ee, etc. etc.
I think it's good for the young crowd to get into self-hosting. You learn more fundamentals that way, for sure. But I'm not looking to move stuff into self-hosted.
I get unlimited scalability in AWS. I can standup and run an app for $0-$5/month depending on how I want to build it. That app will have unlimited scalability, redundancy, automated backups, etc. It's not worth dealing with the headaches of managing things myself.
Most everything is the way it is today for good reason, it's just that the youngsters haven't had to learn those reasons themselves.
Have LLMs just made it too easy to make new projects?
Like as a deployed component in our customer facing app stack? Not being used in that context that I'm aware of. I think there's a couple use cases being worked on though.
Are devs/engineers using MCPs to do their work? Yeah. Datadog MCP, Atlassian MCP, Gitlab MCP, backstage mcp, and we have our documentation behind an MCP. All used daily.
Isn't that how our monetary system works though? Inflation means the numbers WILL always go up.
For personal projects I never used them.
It was never that hard to type a couple extra sentences and it always felt like people were using an LLM to create most of these skills/plugins... and if the LLM can generate them already then what good is it to keep more garbage in context?
Can't tell you how much garbage AI tooling is being built within my org. Whole teams spinning their wheels basically rebuilding claude code because execs are obsessed with "dark factory". Individuals building plugins/skills/mcps that are duplicated or just plain wrong (why do I see so many skills/plugins telling our agents to use main branch when we've always used master???).
I've yanked MOST tools OUT of my claude code/opencode/codex. MCPs to centralize auth to our knowledge base, jira, gitlab. Then a singular short simple markdown file in each project/repo. When brainstorming, maybe I'll create a one off .md that I'll delete once the thing is built/implemented.
I'm tired.
Added a couple spots in Seattle (where it's exceptionally hard to get any food below $10)
No suggestions, just happy to see something that's NOT an AI tool. Even happier that I'll get some use out of this. Maybe add somewhere on the site/app where I can input suggestions if I were to have any later?
If you're making valuable tools, anthropic, openai, or one of the other big players in the space will hire you/buy you out and then they will release the tool themselves.
I'm getting really tired of everyone doing their own special rain dances and then acting like they made it rain.
We built a "fire and forget" agent that's supposed to complete whole jira tasks or that we're supposed to be able to call from slack. You put a ticket in to "make random.md document" and it creates a ton of unit tests and makes "notrandom.md" and says "success". Tons of engineers pulling plugins/skills/etc and injecting them in places they don't belong, lots with blatantly wrong info. People making whole frameworks and tools around their AI workflows, but they're worthless, anything that made sense gets released a week after they finish building from anthropic/openai/etc.
It's ai psychosis from c-level down.
I'm tired.
I personally don't think it's possible and I haven't written a line of code since Sept 2025.
There's an AI psychosis going on right now, especially among the execs or management class, and we all gotta nod our heads in agreement and burn through tokens.
I pay around $.12/kw and get 4 miles per kw. So my "energy" costs are $.03/mile. I have a Mazda cx50 as well, it gets about 20-22mpg, with the gas prices here in Seattle that's around $.30/mile. Even where gas is cheaper that's still $.20/mile. Literally 10x the cost to run a gas car vs an EV.
I'm honestly shocked at how many people have EVs and rely on charging stations. I mean, I think it's a low number, but the fact that it's more than zero is shocking to me.
For most things, you either buy cheap junk or you pay exorbitant prices for decent or high end quality. So I almost always opt to DIY so that I can get quality or exacting specifications without breaking the bank.
It's probably the result of our K shaped economic recovery as well as PE invading so much of our lives, but I was wondering if anybody else feels this way or is going down the path of DIYing more and more in their everyday life?
Everybody is using LLMs/AI. All the time. It's in every facet of your life. Just because you didn't input the prompt, doesn't mean you're not consuming the end product of LLMs all day, everyday, on websites like this one, reddit, tiktok, instagram, facebook, etc.
Addressing the article, if you're hyperfocused on whether people are using AI and only consider AI use a chatbot... well, you're not honestly covering all the AI use out there. And reading the other stats, it seems like this article is trying to paint a narrative. Why is the Datos stat only considering "Desktop use" for instance.
Not to mention their stats are actually astounding and DON'T show what the headline is trying to assert. 1/3 of people using AI regularly is a FUCK TON of people in a VERY short span of time to uptake a new technology.
I start the project in godot, then I talk to an agent to define my game and give details. I tell it to have a conversation with the end goal to be building a CLAUDE/AGENTS/GEMINI markdown file for future agents to help build the game.
I made a [single player top down naval game](https://www.youtube.com/watch?v=FQUTbeQ8-oA) and an online multiplayer game (that I'd like to keep to myself for now).
I mostly used free assets for the artwork. I made some myself in aseprite. I utilized LLMs a tiny amount to generate some assets, but typically those are more of a jumping off point than game ready art assets. This has been what's slowed me down the most in making games.
I only use the cli tools; claude code, codex, gemini cli (which is being phased out for antigravity cli soon)
I've generally had the best luck and enjoy working with claude the most, though that may be because that's the model we use at work (from aws bedrock, we pay per token and always have). Gemini and codex have flip flopped on 2nd place, though right now I'd lean Codex.
On my personal stuff I typically use codex or gemini because those two I have subscriptions, claude I still pay per token but through anthropic API like 90% of the time and 10% of the time through bedrock.
And yes, right now you still need the architectural and system design knowledge because the LLM will fuck that up. We'll all find out if that continues being needed in the future. From what I understand about LLMs and how they work, I doubt it, but also, yeah, I doubted it would've gotten this far when I think back 2+ years ago.
Also, maybe I should be clear, I pretty much never one-shot things. My sessions with claude or other cli tools always starts with a bit of a conversation until we converge on a good plan, claude builds the code, we discuss some more, then we iterate.
For personal projects, only one thing could I actually show - vaicayo.com
This app was originally started pre-llm. I just wanted a centralized place for my wife and I to organize our vacations. I built out the basic crud for that a long time ago and we used it, but then llms got popular. I first integrated it into the app, now I could get it to generate vacation plans completely with the llm. It did okay.
Somewhere between 3-6 months after building out llm features claude code released or I became aware of it enough to start using it.
I rebuilt the whole thing. So what was once a spring boot app running in AWS ECS with alb + cloudfront (and yeah, some sqs+lambda python processes, s3 buckets for storage, aurora rds for db) is now a super lean apigw + lambda + dynamodb stack with a svelte frontend. I went from paying $20ish a month to $0. I also built a flutter app for android and ios that utilizes the same backend as the frontend webapp with feature parity. It's not really a production app, but it could handle it fine, it's completely cloud native and hands off to operate. And let me be clear about the rebuild, it's not a 1 for 1, I think all that I kept was the domain model.
For features, it's mostly just a crud app. You plan your vacation in it. Outside of that there's the ability to take pictures with the phone app that auto-sync (there's a bit of complexity here, the phone app only syncs pics when it's on wifi unless you change settings to allow syncing on cell network, images are cached locally with a ttl, uploads will run in the background and queue up, uploaded images automatically resize/compress and generate thumbnails from an s3 event lambda). The other more complex item is email ingestion, when I get a reservation email I forward it to the app and it automatically processes it (the only place I use an LLM in the app right now). If it can't discern what the email is or which vacation it goes to it goes in a travel inbox so the user can route it to the right vacation and object type. Oh I guess the paywall is a little complex. I don't advertise this thing but I have left user registration open if anybody ever wanted to use it. I did lock the email parsing behind a paywall and I limit photo uploads for free accounts.
So frontend, backend apis, flutter app for android and ios all built 100% by llm.
For code quality, the frontend is okay, the backend is pretty clean but could use some things split out into domains, and the flutter app has some work to do (recently found a couple code smells). But there's no issues adding features, shipping, etc. I literally finished adding some of the photo syncing features in the flutter app last night.
Other than that, I have created 5+ other personal projects that I wouldn't have without an LLM. I've made 2 godot games, a private scribbl.io clone with a few extra features that myself and my coworrkers play as a "happy hour" on fridays, tons of ci/cd build stuff and terraform (using my own personal modules, so I guess that's not 100% llm coded if you consider the modules), and then a couple other simple apps.
There's a big difference between the two and LLMs are increasing the chasm. The Software devs are crying out because the LLMs can already do their full job. Software engineers are happy because the LLMs are removing a large chunk of the job that's low value.
Software dev using an LLM is gonna produce "slop"
Software engineer using an LLM is going to have an increase in productivity depending on how they're using the LLM tools.
"Software Engineers" are embracing LLMs and getting shit done same as before.