Everyone has an opinion on AI right now, and a lot of them are noise. Some say it will annihilate us. Some say it will save us. Both camps get a lot of airtime and neither seems to explain much.
I’ve been thinking about this for a while and I wanted to put some order into it. Not a prediction. Just what I see when I look at who is talking, what they are actually doing, and why the two rarely match.
I see three patterns.<\/p>\n\n\n\n
Oppenheimer led the Manhattan Project that built the bombs dropped on Hiroshima and Nagasaki. He saw the damage, got shaken, and told Truman to exercise restraint. In private.
Then the USSR got the bomb. Only then did he argue the super bomb should never be built. Still in private. Still classified.<\/p>\n\n\n\n
He went public in 1953. Eight years after Hiroshima. That is the Oppenheimer everyone remembers, and it is the last version of him, not the first.
Eight years of knowing, and saying nothing where it counted. By then his legacy was the thing at stake, not the bomb.
I have huge respect for scientists who build things and push them far. But no one will make me believe that when you are developing something, its dangers are not clear to you. These people are visionaries. That is the whole point of them. A visionary sees where the thing goes.<\/p>\n\n\n\n
The pattern I see is the same one today. They become vocal about the dangers of AI only after collecting millions of dollars for making AI come true. At no point before did they judge that the dangers they saw needed to be said out loud. It feels strange to me.<\/p>\n\n\n\n
People tell me AI companies ignore safety because of profit. I don’t buy it. Most of them are still burning capital rather than making money. OpenAI lost over twelve billion dollars in a single quarter this year. That is not a business cutting corners for margin. That is something else.<\/p>\n\n\n\n
I think it’s the space race, the race to the poles, the arms race. It is not about profit but more about who gets there first, never stopping for one second to ask whether it’s relevant, or whether it should be done at all.
Look at how the race is funded. Silicon Valley pours millions into anything that moves, drops it, counts the loss, and writes the next cheque. Losses are not a failure of the model, they are the model. China runs state-directed money on a twenty-year clock, most of it into early stage, against targets set in a five-year plan. Russia isn’t chasing the frontier at all, it’s building something it can control and keep running under sanctions. Different clock, different measure of winning.<\/p>\n\n\n\n
The Americans say they won the space race because they put men on the moon, and it was an incredible achievement. But winning a race means beating your competitor. The moon was never the Soviets’ main business. They were racing a different race, and they were far more interested in what you could do from orbit.
That is the danger of the till-the-end-no-matter-what. The blindness to anything that isn’t the race. Believing it’s life or death to win, never stopping to see that no one is racing them, and that most of the time they are running full speed at a concrete wall with no brakes.<\/p>\n\n\n\n
For them AI is a friend. They want it in every home, always listening, always watching, always ready with advice and counsel. <\/p>\n\n\n\n
Some have had virtual girlfriends and boyfriends. Some simply believe everyone should. They fund humanoid robots, push brain chips, always-on devices, more and more human-machine contact, blurring the border between man and machine as far as it will go. Every so often one of them goes public to say the model is conscious, or that AI will understand you better than people do, that AI is your friend. <\/p>\n\n\n\n
This is Pygmalion and it is hubris. Pygmalion fell in love with the creature he carved. Hubris is forgetting there is a limit, and that crossing it has always had a price. One is loving your creation. The other is overreach. These people are doing both at once, and overreach has never once ended well. <\/p>\n\n\n\n
Humans have a long history of trying to create something because they never got over the fact that they didn’t make themselves. So they chase the dream, obsess over it, and never once stop to ask whether the thing they are chasing is a very bad thing to catch.<\/p>\n\n\n\n
Regulating AI is legitimate. The people doing the loudest regulating are not always the ones with the credibility to do it. <\/p>\n\n\n\n
Every technology humans ever invented came with trade-offs, and the trade-offs are what triggered the rules. The industrial revolution brought cheaper goods and more purchasing power, and it brought pollution and waste. The digital revolution put intelligence in a box and expanded what we could create and calculate, and it also gave us social media, online harassment and propaganda at scale. Railway safety, workers’ rights, checklists in cockpits. All of it written after the damage. <\/p>\n\n\n\n
AI is one of the few times we did it the other way round. Europe passed its AI Act before the catastrophe. China made labelling of AI-generated content mandatory before anyone was forced to. For once the rules arrived ahead of the tragedy. And then the deadlines moved. The high-risk rules that were meant to apply in 2026 now apply in 2027 and 2028. Too burdensome, not ready, bad for competitiveness. <\/p>\n\n\n\n
Here is what I think we should do instead. Treat AI as a strategic and sovereign matter, the way we treat energy, transport and defence. Build and deploy the systems we have judged safe, on our own timetable, and keep the guardrails and the common sense that come with anything strategic. Not a world where AI has the last word. A world where AI stays the tool it is and should remain. That is the line for me. AI decides nothing on its own. A human validates and signs.<\/p>\n\n\n\n
So yes, raising concerns about AI moving too fast is legitimate. What isn’t legitimate is excusing your own recklessness by pointing at a competitor who was never racing you.<\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Everyone has an opinion on AI right now, and a lot of them are noise. Some say it will annihilate us. Some say it will save us. Both camps get a lot of airtime and neither seems to explain much.I’ve been thinking about this for a while and I wanted to put some order into…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_newsletter_tier_id":0,"footnotes":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false,"jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false}}},"categories":[1],"tags":[],"class_list":["post-390","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","jetpack-related-posts":[{"id":13,"url":"https:\/\/archicode.be\/index.php\/2019\/02\/14\/mvas-dead-long-live-microsoft-learn\/","url_meta":{"origin":390,"position":0},"title":"MVA’s dead, long live Microsoft Learn","author":"Hakim","date":"February 14, 2019","format":false,"excerpt":"I've been a regular user of Microsoft virtual academy for quite some time now and when I heard the news about it being decommissioned I felt a bit nostalgic. This is where I learnt WCF and tons of other stuff, and the content was ever growing at the time and\u2026","rel":"","context":"In "Misc"","block_context":{"text":"Misc","link":"https:\/\/archicode.be\/index.php\/category\/misc\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":159,"url":"https:\/\/archicode.be\/index.php\/2020\/06\/24\/feature-flags-using-azure-feature\/","url_meta":{"origin":390,"position":1},"title":"Feature flags using Azure feature","author":"Hakim","date":"June 24, 2020","format":false,"excerpt":"Feature flags are very useful when you develop an application and while you don't want users to use the feature that isn't really ready, you don't want to stay on a side branch for too long as merging and rebasing from the main branch can become quite the chore. Enter\u2026","rel":"","context":"In ".NET"","block_context":{"text":".NET","link":"https:\/\/archicode.be\/index.php\/category\/net\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":162,"url":"https:\/\/archicode.be\/index.php\/2020\/06\/30\/blazor-server-side-or-web-assembly\/","url_meta":{"origin":390,"position":2},"title":"Blazor : server-side or Web assembly","author":"Hakim","date":"June 30, 2020","format":false,"excerpt":"Blazor is amazing. But if you are wondering which of Web Assembly of Server-Side would suit your project, here's an attempt to explain and help","rel":"","context":"In ".NET"","block_context":{"text":".NET","link":"https:\/\/archicode.be\/index.php\/category\/net\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":287,"url":"https:\/\/archicode.be\/index.php\/2023\/05\/28\/infrastructure-as-code-and-source-controle\/","url_meta":{"origin":390,"position":3},"title":"Infrastructure as Code and source controle","author":"Hakim","date":"May 28, 2023","format":false,"excerpt":"For those who don't what is this about, Infrastructure as Code is a set of files when executed with the right tool, will create resources such as storage account, databases, virtual network etc. It is mostly associated with the cloud. As I've been working lately with Terraform, I really enjoyed\u2026","rel":"","context":"Similar post","block_context":{"text":"Similar post","link":""},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":340,"url":"https:\/\/archicode.be\/index.php\/2023\/11\/15\/single-responsibility-principle-clearn-architecture\/","url_meta":{"origin":390,"position":4},"title":"Single Responsibility Principle (Clean Architecture)","author":"Hakim","date":"November 15, 2023","format":false,"excerpt":"When talking about patterns, almost everyone can name the SOLID pattern (Single Responsability, Open\/Close, Liskov Substitution, Interface Segregation and Dependency Inversion). The Single Reponsibility is one of the most important principle for clean code but it's also very important for clean architecture. Let's explore this The SRP states that a\u2026","rel":"","context":"Similar post","block_context":{"text":"Similar post","link":""},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/archicode.be\/wp-content\/uploads\/2023\/11\/8a4f15b6-f5a9-4579-a2aa-6b95d588c817.jpg?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":137,"url":"https:\/\/archicode.be\/index.php\/2020\/06\/09\/publish-a-xamarin-app-to-app-center-with-azure-pipeline\/","url_meta":{"origin":390,"position":5},"title":"Publish a Xamarin app to App Center with Azure Pipeline.","author":"Hakim","date":"June 9, 2020","format":false,"excerpt":"I've been working on an android app with Xamarin lately and I wanted to deploy it to App Center automatically so I can install it on my mobile to test it as I hate manual deployment. I knew that App Center had a connector to azure devops repositories so you\u2026","rel":"","context":"In "Uncategorised"","block_context":{"text":"Uncategorised","link":"https:\/\/archicode.be\/index.php\/category\/uncategorised\/"},"img":{"alt_text":"","src":"\/wp-content\/uploads\/2020\/06\/image-2-1024x1018.png","width":350,"height":200},"classes":[]}],"_links":{"self":[{"href":"https:\/\/archicode.be\/index.php\/wp-json\/wp\/v2\/posts\/390","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archicode.be\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/archicode.be\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/archicode.be\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/archicode.be\/index.php\/wp-json\/wp\/v2\/comments?post=390"}],"version-history":[{"count":1,"href":"https:\/\/archicode.be\/index.php\/wp-json\/wp\/v2\/posts\/390\/revisions"}],"predecessor-version":[{"id":391,"href":"https:\/\/archicode.be\/index.php\/wp-json\/wp\/v2\/posts\/390\/revisions\/391"}],"wp:attachment":[{"href":"https:\/\/archicode.be\/index.php\/wp-json\/wp\/v2\/media?parent=390"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/archicode.be\/index.php\/wp-json\/wp\/v2\/categories?post=390"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/archicode.be\/index.php\/wp-json\/wp\/v2\/tags?post=390"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}