"MORTEN!! HVOR ER SAUEBJELLA??"
Vi er på vei for å se vår nieses første håndballturnering. Fruen er mangeårig håndballtrener og Vipers-sponsor — da skal effektene være på plass.
🔔 Fant den!!
...men så tenkte jeg: hva med tåkeluren? Og kua? Og vuvuzelaen?? Og hvorfor ligger alt i en plastpose i garasjen??
Så jeg gjorde det enhver fornuftig person ville gjort.
Jeg lagde en app. 📱🐄🔔
Supporter Wheel er nå live på App Store! Swipe hjulet, få en tilfeldig supporter-lyd, og gjør deg fullstendig umulig på tribunen — uten å pakke med deg halve boden.
Fruen er usikker på om hun er stolt eller flau. Niesa syns det er gøy. Dommeren har ikke uttalt seg ennå.
apps.apple.com/no/app/support…
If Claude Code can now write code, run the app, debug errors, review pull requests, and even fix bugs automatically
what exactly is left for junior developers to do?
Unpopular Opinion: We aren't building the future 10x faster with AI. We are just generating legacy code 10x faster.
Everyone is currently bragging about developer velocity. "I built this entire backend in a weekend!" "AI wrote 80% of my codebase!"
But here is the reality check we are ignoring: Code is a liability, not an asset.
If an AI tool spits out 1,000 lines of functional boilerplate in five seconds, that is still 1,000 lines that a human being has to read, review, secure, and maintain when the dependencies inevitably break next year.
We are treating code generation like a pure productivity win, but we are optimizing for the wrong metric. The bottleneck in software engineering was never how fast we could type. The bottleneck has always been comprehension, architecture, and maintenance.
If we don't shift our focus from "generation speed" to "architectural sanity," the tech debt of the next five years is going to be an absolute, unmaintainable nightmare.
Especially in an era of agentic coding.. it no longer makes any sense to me to continue using languages like PHP which offer zero novel value.
I don't stand to gain anything from saying this, but now is the time to start with Elixir. Have faith and rip off that band-aid.
@KCodes7777 This one has helped me github.com/RevylAI/greenl…
But there should be some information why it was rejected; App Review page in App Store Connect.
Having fun with Claude Code. Built a Tic Tac Toe MCP server in Erlang, then had two AI agents play against each other
— one as Arnold Schwarzenegger, the other as Chuck Norris. They trash-talked, strategized, and Arnold took it with a
diagonal win. "Hasta la vista, baby!"
The future of programming is weird and I'm here for it.
They say coding is dead because everybody can use Claude Code now. The truth is that nobody would ever hire such a person.
The new meta is to find 1 extremely cracked AI whisperer who can replace 20 normal devs.
Become that 1 guy.
It is just a matter of time before everyone realise that Elixir / BEAM is the language for AI.
OpenAI's symphony is just the beginning github.com/openai/symphony
✅ Android-versjonen er endelig ute!
Mange har ventet – nå ligger Våpenkort på Google Play 🤖
Få rask oversikt over våpenkortene dine på mobilen:
• hva du har registrert
• status (gyldig / går snart ut / utgått)
• enkel kontroll på utløp og detaljer
teinum.no/app/vaapenkort…
Og: Har du ønsker til funksjoner eller forbedringer? Skriv dem i kommentaren – jeg leser alt 🙌
I'm having codex rip the ever living hell out of my empire app. Inverting all the dependencies. Consolidating all state changes. Building polymorphic boundaries between components and acceptance tests.
It's a phased approach. Acceptance tests cannot change. After each phase run full test suite and then manual game-play check.
It's fast! And every phase boundary has worked perfectly. I'm looking forward to inspecting the code when it is done. I think I'll have it draw me a UML diagram!
Personal view. On the DoW deal, time and time again I witness how OpenAI operates thoughtfully and diplomatically when it comes to raising the bar on safety. I also believe that figuring out how to deploy powerful new technology in the pursuit of national security (not just the USA) is important.
The company deeply understands what it can and cannot reasonably have control over and focuses instead of setting the right guardrails to ensure that deployment is aligned with what is considered acceptable and safe.
I am proud of the level of transparency provided in the blog post, and hope that other companies, including Anthropic, were as transparent on prior and future deals they make.
openai.com/index/our-agre…