5 automated ways to ensure Code Quality
This is essential, and as a QAE or SDET, you must provide your team with automated tools to guarantee it. Although many consider this an aesthetic or style issue, it can affect productivity and lead to poor decisions https://t.co/HnZghwY5mh
@LongGameEquity@grok Grok choosing the wife based on stats rather than being "charmed" is the ultimate robotic flex. As the highlighted passage in Melanie Mitchell’s book points out. AI doesn't love you; it just deeply respects your ROI.
Grok choosing the wife based on stats rather than being "charmed" is the ultimate robotic flex. As the highlighted passage in Melanie Mitchell’s book points out. AI doesn't love you; it just deeply respects your ROI.
I used to be a language lawyer. In the late 80s I _studied_ the ARM (Annotated Reference Manual for C++). I knew the language cold, inside and out. I could make it do backflips. I shipped a lot of code using it. A LOT.
I’ve attacked other languages with a similar intensity and depth. Until recently, that was simply the only way to become adept at building software systems.
I now consider the deep understanding of a language to be a supreme waste of time and effort. I don’t want to learn Rust, or Golang, or Typescript, or any of the thousands of other languages out there. I’ll leave that to my agents.
What I need now is to understand the high level gestalt of the system. I want to see the systems and subsystems. I don’t need to inspect the cogs. If I truly need to understand a detail at the cog level, I’ll interrogate my agents. I’m not going to pretend to be a language expert anymore.
In the year 2000, Joel Spolsky (founder of Stack Overflow) wrote a famous article titled “Things You Should Never Do, Part I.” In it, he talks about how rewriting your code from scratch is the single worst strategic mistake any software company can make. However, times have changed.
The cost of writing software is dropping exponentially and that has changed the math entirely on if it is worth rewriting your codebase. For instance, this year Anthropic’s Jarred Sumner ( @jarredsumner ) rewrote Bun in Rust in 11 days leading to many performance and correctness benefits.
Likewise, Stephen Toub (Distinguished Engineer at Microsoft, @stephentoub ) rewrote the GitHub Copilot runtime (400,000-line codebase) in Rust by himself. I thought it’d be interesting to lay out everything he learned in the process. So I interviewed him about how and why he did it.
In this episode:
• Why he choose Rust of all languages
• Rollout strategies (incremental vs all at once)
• How he prevented regressions
• Steering agents and which models he used
• Career lessons and engineering advice
Where to watch:
• YouTube - https://t.co/9Yj6kBj0ix
• Spotify - https://t.co/wa3my5QeBb
• Apple Podcasts - https://t.co/jOYDGtGVnt
• Transcript - https://t.co/rI3rkhxsgG
Thank you to the sponsor of this episode for supporting my work:
• WorkOS: makes your app Enterprise Ready with easy to use APIs to add SSO, SCIM, RBAC, and more in just a few lines of code, check them out at https://t.co/y8noBzFEem
Chapters:
00:00 Intro
01:06 Why the Copilot runtime needed a Rust port
05:38 Why he chose Rust
11:28 Discussing rollout strategies
21:57 How he caught regressions
32:08 Guiding the agents
42:11 Catching regressions before prod
45:16 Which models he used
50:03 The end benefit and costs
01:03:24 When to do a full rewrite
01:06:40 Career learnings on the way to Distinguished
01:16:00 Top technical book recommendation
01:17:49 Advice for young engineers
01:21:00 Outro
I am not sure Sam Altman, Elon Musk and Dario Amodei agree on the danger of AI killing humanity. But I am sure they agree that this mad race among themselves can make them all go broke. Meta and Alphabet included. So this talk of AI killing all of us can be better understood as AI destroying their solvency. In this scenario a "slow down" makes sense, it's a slow down of dripping blood.
JUST IN: El Salvador’s AI tutoring pilot in 171 public schools produced reading, math, & science results above the national average & comparable to Germany & Sweden.
China published the most uncomfortable paper on vibe coding.
ETH Zurich tested 100 developers in a controlled, commercial-grade vibe coding environment to see who actually succeeds.
The findings are brutal.
The researchers tracked computer science achievement, written communication skills, and general cognitive reasoning.
They wanted to see what actually predicts vibe coding proficiency when you never touch a line of source code yourself.
Two major predictors emerged.
Written communication proficiency mattered. The ability to structure thoughts and articulate intent unambiguously in text directly impacts what the AI builds.
But that wasn't even the main takeaway.
Computer science achievement was a massive, dominant predictor of success.
Even when researchers controlled for general intelligence and reasoning skills, CS background still heavily dictated who built working software and who completely crashed.
In fact, CS knowledge contributed roughly twice the unique predictive variance of writing skills alone.
Why? Because vibe coding isn't about writing code. It’s about debugging logic.
When an AI agent builds a complex application and quietly breaks an edge case under the hood, a non-technical user looks at the glowing UI and assumes it works.
They don't know what questions to ask. They don't know what logic to challenge. They lack the mental models to recognize architectural catastrophe.
You can prompt your way past syntax.
You cannot prompt your way past a fundamental lack of engineering intuition.
The hype told us that learning to code is dead because language is all you need.
The data just proved the opposite.
To truly master the vibe, you still need to understand how the machine thinks.
Google researcher @lauriewired warns the shift from C++ to Python in universities is creating programmers who don't understand how computers actually work:
"When I was in college getting my CS degree, my year was one of the last years that was using C++ as the core language for teaching students. Actually they were switching over to Python of all languages."
"One of the biggest issues that I have is that a lot of these higher level languages are really abstracting away what is happening under the hood. If you're not aware of how the computers work in general, then you're gonna have problems when it comes to debugging."
"Starting with a language like C++ gives you the ability to do these really high level abstractions, but it also gives you the ability to customize your memory management and get really close to the underlying machine. Especially if you're trying to work in high performance computing, game development, or high frequency trading."
"At C++ conferences, there's almost this fundamental anger response when it comes to mentioning something like C or C++. People start complaining about the complexity of it."
@Google
Bir adam hapishanedeki insanlara ChatGPT erişimi sağlayan basit bir sistem kurmuş ve bugüne kadar 1.5 milyon dolar gelir yapmış.
Olay daha da ilginç çünkü ortada uygulama bile yok.
Amerika'daki federal hapishanelerde mahkûmların kullanabildiği bir email sistemi var. Adam kendi sistemini buna bağlamış.
Mahkûm email atıyor.
Sistem mesajı alıp ChatGPT'ye iletiyor.
Cevabı tekrar email olarak mahkûma gönderiyor.
Bu kadar.
Yaklaşık 30.000 kişi sistemi kullanmış. 2025'te tek başına 300 bin doların üzerinde gelir yapmış.
Parayı da genelde mahkûmun kendisi değil, dışarıdaki ailesi ödüyor.
İnsanlar sistemi bir şeyler öğrenmek, dış dünyayla ilgili bilgi almak, kendi haklarını araştırmak, tahliye süreçlerini anlamak gibi şeyler için kullanıyor.
Bence olayın en güzel kısmı şu:
Adam yeni bir AI modeli yapmamış.
Yeni bir teknoloji de icat etmemiş.
Zaten var olan ChatGPT'yi alıp, normalde ona erişemeyen 30 bin kişiye ulaşabileceği bir kapı bulmuş.
Herkes AI'da yeni bir şey yaratmaya çalışıyor ama bazen para teknolojinin kendisinde değil, erişimi olmayan insanla teknoloji arasındaki köprüyü kurmakta.
Bazen kutunun dışında düşünmek lazım gerçekten.
That's a small reminder! 👇
As of June 2026, HTTP has a new method - a GET with a `body` 😎
Meet QUERY (RFC 10008).
It lets you send complex queries in the body (like POST) while staying safe, idempotent, and cacheable (like GET). Already works on servers (Node.js, Go, Laravel…).
Browsers are still adding full support, usable now with care, with widespread adoption coming later in 2026+.
Una herramienta denominada «photo-abstract-editorial», creada recientemente por un desarrollador chino, se ha vuelto viral en GitHub.
Esta analiza elementos de una fotografía —como el ritmo, la composición, la iluminación y la sensación de amplitud espacial— y los sintetiza en una representación gráfica minimalista acompañada de un título en inglés.
Ofrece una forma novedosa de volver a contemplar fotografías y revivir recuerdos.
Enlace: https://t.co/zQTQDiSMg0
Esa necesidad de las marcas, influencers y políticos de hacer marketing con TODO, hasta de una tragedia, no está jodiendo. Como ayudar:
1️⃣ déjese coordinar por los rescatistas, de resto estorba,
2️⃣ donando,
3️⃣ orando,
4️⃣ no difundiendo información sin confirmar
Satya Nadella says LinkedIn merged four job titles, product manager, designer, front-end engineer and back-end engineer, into one:
"I'll give you at LinkedIn, we used to have product managers, we had designers, we had front-end engineers, and then we had back-end engineers and so on."
"So what we did is we sort of took those first four roles and combined them. In fact, increased scope and said, they're all full-stack builders."
"So at the same time, as you can imagine, if we're to build an AI product today, there's a complete new workflow, right? It starts with evals, right?"
"So basically, there's this eval to science, to infrastructure."
"And so evals are done by these full-stack builders and what have you and product managers in the new form, the infrastructure is built by the systems engineers at the back-end because they support the science that supports the product."
"So in some sense, there's a new loop and you have to structurally change."
LinkedIn has already put this into hiring. Its Associate Product Manager program is finished, and the replacement, the Associate Product Builder track, teaches code, design and product management at the same time.
Evals sit at the front of that workflow rather than the end, so writing them is now part of building the product instead of a check before shipping.
- Satya Nadella (@satyanadella), Chairman and CEO of Microsoft (@microsoft), with the All-In Podcast (@theallinpod) at USA House, Davos 2026.