I've never heard of this guy. He's "self employed"
The article lacks any real detail and it just a guy patting himself on the back.
638 karma · joined April 7, 2020
I've never heard of this guy. He's "self employed"
The article lacks any real detail and it just a guy patting himself on the back.
Once the LLM tells me "Okay, it's done, everything works" I always as it to do a thorough review, I tell it to split up the work among sub-agents with each one taking on a specific responsibility (look for code smells, look for bad architecture, review the data access model, DUPLICATE CODE, testability and unit testing, etc.)
After a certain number of revisions and reviews you'll come to accept the shortcomings it comes back. Usually there will be specific design decisions you made that the LLM keeps bringing up, once the review only brings that up and maybe some other minor issues it's time to move on.
I don't overly rely on markdown files and directions. I don't rely on tooling around it either. I just don't trust the LLM when it says "all done", tests pass, and deployment works. I make it to multiple reviews and iterations even when it thinks it's done.
The chasm between "Software Developer" and "Software Engineer" is getting wider. Articles like this and the comments under it give away who is an Engineer and who is just a coder.
I'm not even sure what it's trying to say. It's just someone patting themselves on the back.
When I go out to eat, I'd love to know what people's favorite dishes are so that I know what to try. This plugin I made is specifically for that. This is just a small hobby project, but I thought I'd share some details and how I built it in this modern LLM age of building software.
And although I may not write code without LLMs these days, I do (currently) write all the blog posts and create all the content myself.
I flip between models all the time. Makes little difference. Sometimes one model is faster or better than another but there's no rhyme or reason why.
I don't look at benchmarks.
It's a non-deterministic tool. A lot of the shit going on with LLMs just doesn't make sense to me. All the tooling around like MCPs, they're all just putting stuff into context. So to me the tools aren't really robust and they make little difference.
Lots of AI psychosis going on these days. And I say that as somebody that hasn't written a line of code since Sept 2025
Custom scalers? Running prometheus, grafana, etc?
These people are professional amateurs. They don't know what they don't know so they post stupid posts like this and all the other know-nothings upvote it and comment likewise.
Seriously, there's nowhere online for good software engineering discussion.
I've been holding Hacker News in too high of esteem for too long I think. Most people on here are amateurs at best. The complaints about AWS/Cloud and LLMs are getting too loud. Did the industry pull in too many inexperienced during covid and now we're witnessing the backlash or something?
I've been doing this a long time. Running hardware, running VPS in the cloud, and running on AWS. I'll never go back to hardware/on-prem.
Reddit died quite a while ago and I was holding on to Hacker News, but with all the anti-LLM posts and the anti-cloud fud I see on here it's obviously not here either any more.
What is going on that all the "engineering" users are anti-engineering, against change and advancement?
You guys posting this shit have to realize you're working on podunk garbage coding projects right? If you're finding AWS overly complex this is sounding more like a YOU problem.
Those of you saying on-prem is better, you're saying a lot more about yourself, your experience (lack of) and the project you're working on than you're saying about cloud.
Like holy fuck, how can you hate lambda? It's STUPID simple wtf???
I'm honestly surprised how many people have subscriptions and are expecting anthropic to eat the cost lol
I think Acadia is a great National Park, especially for the East coast. But I moved to Seattle a few years back and only more recently got out to Orgas Island. It's insane how similar it is to Acadia.
The East coast just doesn't have as many untouched lands as the West. West coast parks, pretty much all the parks West of the Mississippi, are next level. If you're accustomed to that then none of the East coast parks are going to wow you.
That does seem very powerful now that I've had some time to think about it.
I don't know, to me it seems like the LLM cli tools are the current pinnacle. All the LLM companies are throwing a ton of shit at the wall to see what else they can get to stick.
You just prompt the llm to change the plan.
Here's the rub, I can spin up multiple agents in separate shells. One is prompted to build out <feature>, following the pattern the author/OP described. Another is prompted to review the plan/changes and keep an eye out for specific things (code smells, non-scalable architecture, duplicated code, etc. etc.). And then another agent is going to get fed that review and do their own analysis. Pass that back to the original agent once it finishes.
Less time, cleaner code, and the REALLY awesome thing is that I can do this across multiple features at the same time, even across different codebases or applications.
I built a skribbl.io clone to use at work. We like to play eod on Friday as a happy hour and when we would play skribbl.io we would try to get screencaps of the stupid images we were drawing but sometimes we would forget. So I said I'd use claude to build our own skribbl.io that would save the images.
I was definitely surprised that claude threaded the needle on the task pretty easily, pretty much single shot. Then I continued adding features until I had near parity. Then I added the replay feature. After all that I looked at the codebase... pretty much a single big file. It worked though, so we played it for the time being.
I wanted to fix some bugs and add more features, so I checked out a branch and had an agent refactor first. I'd have a couple context/sessions open and I'd one just review, the other refactored, and sometimes I'd throw a third context/session in there that would just write and run tests.
The LLM will build things poorly if you let it, but it's easy to prompt it another way and even if you fail that and back yourself into a corner, it's easy to get the agents to refactor.
It's just like writing tests, the llms are great at writing shitty useless tests, but you can be specific with your prompt and in addition use another agent/context/session to review and find shitty tests and tell you why they're shitty or look for missing tests, basically keep doing a review, then feed the review into the agent writing the tests.