I've been a professional full stack dev for 15 years and dabbled for years before that - I can absolutely code and know what I'm doing (and have used cursor and just deleted most of what it made for me when I let it run)

But my frontends have never looked better.

100% this. I've gotten to where when people try and rope me into their new million dollar app idea I tell them that there are fantastic resources online to teach yourself to do everything they need. I offer to help them find those resources and even help when they get stuck. I've probably done this dozens of times by now. No bites yet. All those millions wasted...

Claude code can make something that works, but it's kinda over engineered and really struggles to make an elegant solution that maximises code reuse - it's the opposite of DRY.

I'm doing a personal project at the moment and used it for a few days, made good progress but it got to the point where it was just a spaghetti mess of jumbled code, and I deleted it and went back to implementing each component one at a time and then wiring them together manually.

My current workflow is basically never let them work on more than one file at a time, and build the app one component at a time, starting at the ground level and then working in, so for example:

Create base classes that things will extend, Then create an example data model class, iterate on that architecture A LOT until it's really elegant.

Then Ive been getting it to write me a generator - not the actual code for models,

Then (level 3) we start with be UI.layer, so now we make a UI kit the app will use and reuse for different components

Then we make a UI component that will be used in a screen. I'm using flutter as an example so It would be a stateless component

We now write tests for the component

Now we do a screen, and I import each of the components.

It's still very manual, but it's getting better. You are still going to need a human cider, I think forever, but there are two big problems that aren't being addressed because people are just putting their head in the sand and saying nah can't do it, or the clown op in the post who thinks they can do it.

1. Because dogs be clownin, the public perception of programming as a career will be devalued "I'll just make it myself!" Or like my rich engineer uncle said to me when I was doing websites professionally - a 13 year old can just make a website, why would I pay you so much to do it. THAT FUCKING SUCKS. But a similar attitude has existed from people "I'll just hire Indians". This is bullshit, but perception is important and it's going to require you to justify yourself for a lot more work.

2. And this is the flip side good news. These skills you have developed - it's is going to be SO MUCH FUCKING HARDER TO LEARN THEM. When you can just say "hey generate me an app that manages customers and follow ups" and something gets spat out, you aren't going to investigate the grind required to work out basic shit. People will simply not get to the same level they are now.

That logic about how to scaffold and architect an app in a sensible way - USING AI TOOLS - is actually the new skillset. You need to know how to build the app, and then how to efficiently and effectively use the new tools to actually construct it. Then you need to be able to do code review for each change.

Mmmmmm no, Claude definitely is. You have to know what to ask it, but I generated and entire deadman’s switch daemon written in go in like an hour with it, to see if I could.

It's further than you think. I spoke to someone today about and he told me it produced a basic SaaS app for him. He said that it looked surprisingly okay and the basic functionalities actually worked too. He did note that it kept using deprecated code, consistently made a few basic mistakes despite being told how to avoid it, and failed to produce nontrivial functionalies.

He did say that it used very common libraries and we hypothesized that it functioned well because a lot of relevant code could be found on GitHub and that it might function significantly worse when encountering less popular frameworks.

Still it's quite impressive, although not surprising considering it was a matter of time before people would start to feed the feedback of an IDE back into it.

idk ive seen some crazy complicated stuff woven together by people who cant code. I've got a friend who has no job and is trying to make a living off coding while, for 15+ years being totally unable to learn coding. Some of the things they make are surprisingly complex. Tho also, and the person mentioned here may do similarly, they don't ONLY use ai. They use Github alot too. They make nearly nothing themself, but go thru github and basically combine large chunks of code others have made with ai generated code. Somehow they do it well enough to have done things with servers, cryptocurrency, etc... all the while not knowing any coding language.

Might be satire, but I think some "products based on LLMs" (not LLMs alone) would be able to. There's pretty impressive demos out there, but honestly haven't tried them myself.

It appears you may have accidentally a word

Yeah, I've been using it heavily. While someone without technical knowledge will surely allow AI to build a highly insecure app, people with more technological knowledge are going to propel things to a level where the less tech savvy will have fewer and fewer pitfalls to fall into.

For the past two months, I've been leveraging AI to build a CUE system that takes a user desire (e.g. "i want to deploy a system with an app that uses a database and a message queue" expressed as a short json) and converts a simple configuration file that unpacks into all the kubernetes manifests required to deploy the system they want to deploy.

I'm trying to be fully shift-left about it. So, even if the user's configuration is as simple as my example, it should still use CUE templating to construct the files needed for a full DevSecOps stack - Ingress Controller, KEDA, some kind of logging such as ELK stack, vulnerability scanners, policy agents, etc. The idea is the every stack should at all times be created in a secure state. And extra CUE transformations ensure that you can split the deployment destinations in any type of way, local/onprem, any cloud provider, or any combination thereof.

The idea is that if I need to swap out a component, I just change one override in the config and the incoming component already knows how to connect to everything and do what the previous component was doing because I've already abstracted the component's expected manifest fields using CUE. So, I'd be able to do something like changing my deployment from one cloud to another with a click of a button. Or build up a whole new fully secure stack for a custom purpose within a few minutes.

The idea is I could use this system to launch my own social media app, since I've been planning the ideal UX for many years. But whether or not that pans out, I can take my CUE system and put a web interface over it to turn it into a mostly automated PaaS. I figure I could undercut most PaaS companies and charge just a few percentage points above cost (using OpenCost to track the expenses). If we get to the point where we have a ton of novices creating apps with AI, I might be in a lucrative position if I have a PaaS that can quickly scale and provide automated secure back ends.

Of course, I intend on open sourcing the CUE once it's developed enough to get things off the ground. I'd really love to make money from my creative ideas on a socialized media app that I create, am less excited about gatekeeping this kind of advancement.

Interested to know if anyone has done this type of project in the past. Definitely wouldn't have been able to move at nearly this speed without AI.