Anyone I talked to who actually built software found them to be bunk. Occasionally they work, but mostly they just burn tokens.
The only people I know still hyped on this approach were managers who were detached from actual engineering, primarily producing bespoke dashboard and tools.
Because these data centers put enormous pressure on local utilities, pay 0 dollars back into the local economy, and get tax breaks. Often they are facilitated by backroom deals with local politicians. This plays both into anxieties surrounding AI and general corruption.
Because we value leadership over craftsmanship. Ever since people like Ford showed that it was not individual skills but optimized systems that make the biggest corporate machines with the most potential for profit, we have prioritized one over the other.
Does it do anything novel? Looks the same as any other basic stock ticker app. Most of the popular ones are made by companies with massive marketing budgets.
We had a private network on campus circa 2010. Streaming was up and coming but not huge. Gnutella was great on the gigabit intranet. You could download entire HD movies in minutes where conventional torrents may be hours.
I would rather see MS Paint art like Slay the Spire than ai slop art. I think you could have done ai art for a demo but it's so obviously ai, it immediately turned me off. And may turn others off too.
Hosting and public are different. This measure is like saying unless you are painting public murals you haven't made real art. The take is just so wrong it's hard to know where to start.
I build stuff that people use every day (judging by the flood of tickets I'll get if I ship a bug), but my public github profile looks like a ghost account. 99% of what I build is proprietary, and is either in a private or self hosted repo.
I'm not sure scanning public GitHub is a great way to identify "do nothing" developers.
Prompt engineering is mostly structured thought. Can you write a lab report? Can you describe the who, what, when, where, and why of a problem and its solution?
You can get it to work with one off commands or specific instructions, but I think that will be seen as hacks, red flags, prompt smells in the long term.
There should be a saying like "A tool is not the task" similar to "A map is not the land." As professional tool makers it can be easy to replace the task with a tool in theory, but that's not reality.
In a similar vein I think that's why there are so many devs making game engines instead of games.
Because many people run on policies and then just don't follow up. Trump ran on "no more wars" and then started a war. Most people have such a team mindset they will choose denial over admitted they were duped, and then do it all again.
The only people I know still hyped on this approach were managers who were detached from actual engineering, primarily producing bespoke dashboard and tools.