alt Hacker NewsI have a suspicion that Twitter laying off so much of the software staff was very influential for people with hiring abilities. The company didn't crash, and they (relatively slowly) began shipping new features again. I think that coincided with the pandemic-era overhiring, and we've been working against that combo ever since.
Every now and then, I actively try to make an LLM replace my tasks, and fully do greenfield projects I would accept- I don't see it. It's very good, no doubt. But I have or have been given the project parameters, and just like with a junior, failures in communication inevitably lead to breakdowns in execution.
Replies
I hate to be "that guy" but you're crazy if you don't see AI being able to do greenfield projects you'd accept.
I mean, in your defense, last year I think you would have been right, but right now? Codex rocks, as does Claude. I am literally making money shipping a greenfield project to a customer right now. I'm basically a cheap consultant that is incrementally adding features to make something exactly what they want for way cheaper than it would be to do it the old way.
There are hiccups, outages, things to fix etc. but the customer is happy with the output, and the reduced price means they get bespoke solutions rather than some BS one size fits all SaaS app. Then my job is maintenance and effectively "ITSM." Which kind of sucks in some ways, I miss writing real code for real projects, but this is the future going forward. If you want something for your business, you'll generate it rather than pay for it and for now at least, getting beyond localhost requires someone who knows a bit about computers or is willing to learn. Most small businesses aren't willing to learn.
Now, to your point. Is the code all that clean? Nope (and in your defense sometimes I read through the codebase and shudder)... but who cares? Like, for awhile I would go through and frantically edit it, but why? It worked. Not only that, but there's going to be a new model in 3 months or whatever that can clean it up and make it less shitty. I've literally done that a couple times since I started doing this in January.
The customer ain't reading the code. They don't care as long as the the functionality works - that's what counts. The gazillion tests I have keep it stable as I push code, and the CI/CD pipeline removes a ton of the ass pain I'd have without it.
The biggest thing I'm worried about when it comes to clean code and good design is trying to make sure I keep the token count down on these projects so I can actually do meaningful work without burning through a week's worth of tokens in a single day. That, and I like to try to keep a sort of architectural bird's eye view on what's happening...
Like, I'm not sure what niche of the industry you're in, but for the stuff I'm using it for, stuff is working really well with LLMs.
It does your job, but not completely autonomously so you don't see it?
It requires a lot of guidance, luckily, I mean thank god otherwise we would be goners. The job itself hasn't become easier, but it did change. If you come across failures you update the spec, the guard rails, whatever you use to guide it. It's not a "it produced bad code and now it's forever useless" type of situation.