1. create a skeleton clone of frontend A, named frontend B, which is meant to be the frontend for backend project B, including the oAuth configuration
2. create the kubernetes yaml and deployment.sh, it should be available under b.mydomain.com for frontend B and run it, make sure the deployment worked by checking the page on b.mydomain.com
3. in frontend B, implement the UI for controller B1 from backend B, create the necessary routing to this component and add a link to it to the main menu, there should be a page /b1 that lists the entries, /b1/xxx to display details, /b1/xxx/edit to edit an entry and /b1/new to create one
4. in frontend B, implement the UI for controller B2 from backend B, create the necessary routing to this component and add a link to it to the main menu, etc.
etc.
All of this is done in 10 minutes. Yeah I could do all of this myself, but it would take longer.
With adults usually having no more than 2-3 hours of free time per work day, this allows you to productively program in your free time without fully burning out.
Also, my company pays for claude and does not give a shit what I do with it.
Talk to any model about deep subjects. You ll understand what I am saying. After a while it will start going around in circles.
FFS ask it to make an original joke, and be amused..
so like your average human
> FFS ask it to make an original joke, and be amused..
let's try this one on you - say an original joke
oh, right, you dont respond to strangers prompts, thus you have agency, unlike an LLM
If an average human has seen and read all that is written till now, I bet that they can hold the conversation going for quite a long time...
>say an original joke
I asked an LLM if it had a good night with sweet dreams, It said, "I don't sleep and I only dream when I work!"
It works because people have answered similar questions a million times on the internet and the LLMs are trained on it.
So it will work for a while. When the human generated stuff stops appearing online, then LLMs ll quickly fall in usefulness.
But that is enough time for the people who might think that it going to last for ever to make huge investments into it, and the AI companies to get away with the loot.
Actually it is the best kind of scam...
EDIT: Another thought. Thus it seems that AI companies actually have an incentive to hinder developements, because new things mean that their model is less useful. With the widespread dependence on AI, they might even get away with manipulating the population to stagnate.
But by some subset of definitions my calculator is intelligent. By some subset of definitions a mouse is intelligent. And, more interestingly, by some subset of definitions a mouse is far more intelligent than an LLM.
My pocket calculator is not intelligent. Nor are LLMs.
Yes, I have worked in small enough companies in which the developers just end up becoming the default IT help desk. I never had any formal training in IT, but most of that kind of IT work can be accomplished with decent enough Google skills. In a way, it worked the same as you and the LLM. I would go poking through settings, run tests to gather info, run commands, and overall just keep trying different solutions until either one worked or it became reasonable to give up. I'm sure many people here have had similar experiences doing the same thing in their own families. I'm not too impressed with an LLM doing that. In this example, it's functionally just improving people's Googling skills.
I don't think conflating intelligence with "what a computer can do" makes much sense though. I can't calculate the X digit of PI in less than Z, I'm still intelligent (or I pretend to be).
But the question is not about intelligence, it's a red herring, it's just about utility and they (LLM's) are useful.
Any standard of intelligence devised before LLMs is passed by LLMs relatively easily. They do things that 10 years ago people would have said are impossible for a computer to do.
I can run claude code on my laptop with an instruction like "fix the sound card on this laptop" and it will analyze what my current settings are, determine what might be wrong, devise tests to have me gather information it can't gather itself, run commands to probe hardware for it's capabilities, and finally offer a menu of solutions, give the commands to implement the solution, and finally test that the solution works perfectly. Can you do that?