My bet is that promptgrammers will be so common they'll become standard full-stack engineers, and the few experienced programmers that still know software engineering from the ground up will become expensive gurus sought for critical tasks.
The elite gurus will get paid handsomely, while promptgrammers will be paid less since they've become a less-skilled commodity, and the company has to pay for the expensive tokens they'll avidly consume.
I've seen someone jump from Wordpress to deploying internet-facing APIs because 'they have PHP experience', and the holes in their knowledge were filled blindly by an LLM. I have also argued with a seasoned developer about how their code didn't need linting because LLMs 'already follow best practices'.
The future doesn't look bright when LLMs allow future generations to feign required knowledge.
It's less a matter of being more expert than AI, and more a matter of being socially and legally accepted for certain roles. It seems likely that AI will be rejected for certain tasks on a matter of principle.
I doubt I'd want a human doing anything in the future, like what, surgery? I'd want a robot. Really anything. It's like no one needs nails made by blacksmiths, no one needs some maybe tired or distracted person performing surgery on them.
Or just tell them to integrate them. Which I guess takes some knowledge/experience to even ask for. Then again, LLM know it too; in fact, currently, if you let them set up a project, they overengineer the heck out of it by integrating more "best practices" at once that's reasonable.
It remains to be seen. Most of the effort of a normal decent software engineer, up until now, is not in "writing code" but in "writing code that is correct, understandable and maintainable going forward". We are now in a phase of rapidly losing our ability to understand programs. On this trajectory, programs will soon become as impenetrable as the LLMs themselves. We'll start finding out whether that matters or not soon.
Ultimately it will probably come down to liability, though. If someone receives the wrong dose of a drug due to a software error, whose fault is it? If you want it to be my fault, then I'll want to understand the software. Loads of people would take on the liability without fully understanding it, though. The future doesn't look good, but we'll just have to wait and see.
I always liked and thought DW was one of the largest publishers in Germany but learned from a German friend that it was not a major public media organization and many don't know about it there.
It's the thing aimed at overseas; the German news here in Australia on SBS are also DW. Like you can't really get France 24 inside France, or NHK World inside of Japan, or CNN International within the US without some extra hoops
I see that with Opus 5, it started thinking like crazy in the last few days , I don't think my workflow is that complicated, still it gets into thinking mode and stays there
from https://huggingface.co/convaiinnovations/laya
> The policy reports a distribution; exploration adds zero-mean Gaussian noise to the logits; the reward is a strictly proper scoring rule (log + spherical, plus ranked probability score for ordinal questions). Expected reward is maximised only by reporting honest probabilities.
I am happy for the team's success but I am sad and anxious for what may become of the DuckDB. It is my favorite tool. Like other comments mentioned, DuckDB is open source and MIT license so I hope it will survive and evolve further the way it did.
duckpgq is great. I'd say the tl;dr is duckpgq if you have tables you want to traverse like a graph sometimes, latticedb when graph traversal is the primary mechanism of querying.
One of the motivating use cases for me was experimenting with agentic memory. I use latticedb as the backing data store. Finding related memories is traversing the graph (kind of like graph RAG).