After building replacements for my SaaS stack, I realized I was paying full subscription prices for apps where I barely used 20% of the features.
As you delegate more of your life to AI agents, your attack surface grows while your oversight shrinks. Auditing permissions shouldn't be a one-time setup, it needs to be a routine habit.
LLM code slop is exacerbated by organic slop (terrible code written by devs accumulated over the years).
A tension I'm seeing in teams. Non-engineers ask "does it work?" Engineers ask "will it survive?"
LLMs build the demo, but demos don't have on-call rotations. Turning AI code into secure, scalable production isn't gatekeeping, it's engineering.
AI injury law is going to be a massive growth industry. Between autonomous agents, hallucinated medical advice, and rogue deployments, it’s only a matter of time before we get mass-media injury lawyers specializing purely in AI liability.
Nuts. At this rate you can't get in the game unless you own a nuclear power plant or hydroelectric power dam.
Mustafa Suleyman (CEO of Microsoft AI):
$100B training runs are coming.
" There are gigawatts of compute that are being assembled and there's only 5/6 labs.
Computation and test time scaling of compute is clearly going to be a seismic advantage.
There's going to be this extreme acceleration of some of the larger efforts with big labs with big computation like this."
----
Full video on "The Rest Is Politics: Leading" YouTube channel, (link in comment)
Visual AI slop is obvious. Code AI slop is an invisible trap. LLMs continuously write overlapping logic because they lack architectural awareness. The codebase doubles overnight, human context is lost, and deciphering it requires the very AI that broke it.
I love to read science fiction and horror, and frequently I have a tough time visualizing concepts or monsters. Nano banana has been an absolute godsend.
Such an interesting chart. While the market gets flooded with vibe-coded apps, usage and reviews are actually collapsing. People aren't just ignoring the noise, they're sticking mostly to what they already know.
After being involved with two different hardware startups, PCB design is where schedules go to die, so this is incredibly cool: a6mzero.com/posts/this-pcb-i…
There’s a lot of ai doomerism but this has honestly been one of the most exciting times to build. The problems are a dime a dozen and if you can avoid the distractions, you can come up solutions that actually improve people’s lives.
We are hardwired to anthropomorphize e.g mapping a face onto a car. Unsurprisingly we are doing the same with AI by projecting agency, emotion, and sentience onto something that is simply running complex decision trees.
Every "summarize this page" extension ships your reading to someone else's server.
This one doesn't. Offline TL;DR runs the model on your machine.
github.com/dkobia/offline-tl…
Great quote from the show "The Audacity".
"We don't sell cars. We sell subscription-based surveillance systems that happen to have wheels."
David Kobia retweeted
the absolute state of ai dev tools. grok build is silently dumping 12gb of untouched repo data and full git commit histories to gcp just to autocomplete a script. they don't want to help you build, they are just treating local dev environments like an open buffet for training data. if you run this on a sensitive stack, your entire repo is already compromised regardless if it's public or not. literal spyware.
shipping source code to the cloud is bad enough. blindly inhaling .env.local and .dev.vars in a background sync is absolute negligence. they are vacuuming up your raw api keys, database credentials, and private nodes directly to gcp just to power an autocomplete model.
a massive credential breach disguised as a dev tool. if you ran this locally, your private keys are now sitting on a remote server. consider every secret burned, treat your bare metal as completely compromised, and rotate your entire stack immediately.
@elonmusk, your users deserve a serious explanation!
🚨🚨🚨 SpaceXAI 的人工智能编码工具 #GrokBuild 被曝默认上传完整的 Git 仓库,包含工具本身没有读取的代码或调用的上下文以及 Git 完整提交历史。
测试还显示 12GB 的仓库数据被发送至少 5GB 的数据到谷歌云端,Grok Build 使用谷歌 GCP 来存储收集的这些数据。
目前这种行为已经在开发者社区引起关注,继续使用 Grok Build 可能存在潜在的数据泄露风险。
查看全文:ourl.co/113897?x
The world cup is a reminder to Atlanta that we could so much more with the Metro and spend less time in our cars -- instead of voting down expansions every election: atlanta.urbanize.city/post/f…
David Kobia retweeted
HISTORY HAS BEEN MADE 🫨
Sabastian Sawe becomes the first person ever to break the 2-hour barrier in official race conditions, storming to a historic 1:59:30‼️
@KejelchaYomif, on his marathon debut, also breaks 2 hours with a stunning 1:59:41 and @jacobkiplimo2 clocks 2:00:28, also faster than the previous world record 😤












