“Why AI Has Failed to Take Your Job Since 1976” Worth watching 👇 youtube.com/watch?v=mDzQsCHJ… What’s your take? 🤔

We are so back. I don't want to be mean, but shouldn't we be more LEAN? What is the goal? What is the biggest contraint? Do we know what is the most important? Do we really need it right now? Do our customer get more value? Were costs reduced? Are we making more money?

Think we need some more concrete measures. Feelings can be misleading. If AI-assisted coding improves people's productivity, it must show up in some numbers somewhere, I suppose

I've tried for years to draw layers vs hexagon, this is the best I've been able to manage on my side:

It's interesting that agentic coding requires more and better engineering, not less. What’s largely missing from today’s “programmers will be replaced” narrative is: writing the initial version of a product or feature was never the hard part. Most of the work (and most of the costs and tokens) comes after that first version is shipped. And this is exactly where software design and architecture start to matter. A lot.

kind of related? a paper by @CarloPescio about the issues with a one-line FP solution to the 'Water collected between towers' programming challenge: Programming as if the Domain (and Performance) Mattered drive.google.com/file/d/0B59…

Hey @philip_schwarz sorry to bother you, I remember you had a slide deck based on a talk about how compressing some algorithm to a single line of code for flex was obfuscating the communication of intent. Do you happen to remember which deck it was?

🌟🌟🌟Modularity Skills for Claude Code🌟🌟🌟 Last week I quietly released my Balanced Coupling-based Claude Code plugin. Today it hit 100 GitHub stars, so time to make it official 🎉 The plugin tackles architectural and design challenges that existing tools don't and comes with two skills: /modularity:review analyzes your codebase for architectural / design issues and produces actionable recommendations for improving its modularity. /modularity:design processes functional requirements and designs a modular architecture, complete with architecture documentation, module design docs, integration contracts, and test scenarios. Based on my own testing and feedback from others, it produces relevant and actionable results. The part I'm still working on: its subdomain identification abilities. But hey, that's the hardest part of DDD anyway. To its defense, it compensates by asking tons of questions to understand your business context. If you installed the plugin last week, make sure to update, as there were some usability improvements. Thanks, @alexeiled! 🔗Link to the repository with installation and usage docs is in the first comment P.S. Sharing is caring 😉

Zamiast czytać o tym, jak AI "zmieni HR", dałem się zrekrutować botowi. 🤖 30s na odpowiedź i brak feedbacku. W nowym ITea Morning pokazuję nagranie z rozmowy i analizuję, jak działają dzisiejsze techniczne filtry rekrutacyjne. Sprawdźcie tutaj: youtu.be/eBWZzyITgPA

ReSharper 2026.1 has just been released! 💡 New Monitoring tool window for runtime insights 🆕 Expansion into @code 🧠 Expanded C# support with new inspections and upcoming features ⚡ Improved Out-of-Process stability ⭐ And much more! Click here for details: jetbrains.com/resharper/what…

The Release Candidate build for ReSharper 2026.1 has just landed!🎉 This blog post tells you everything you need to know about the upcoming release: blog.jetbrains.com/dotnet/20…

Does he know we had IDEs for more than 20 years now and a clipboard for even longer?

Someone builds a project management tool with Claude Code over a weekend. Ships it. Tweets "just replaced Jira." The app works. One user, happy path, localhost. Then two people edit the same record simultaneously, and the data is silently corrupted. They don't know what an optimistic lock is. They never needed to before. The prototype is maybe 1% of what makes software actually work. The other 99% is what you find after real users show up: race conditions, failed transactions, sessions expiring at the wrong moment, a payment webhook that fires twice and charges someone double. AI didn't cover any of that. It built exactly what you asked for. And the confidence is the worst part. "Just need to adjust a few things before we go live." The few things you need to adjust are the product. That's like laying a foundation and telling people you basically built the house. Vibe coding works. For personal tools, throwaway scripts, and prototypes you'll never put in front of paying users, it's genuinely fast and good enough. I use it. But there's a hard ceiling, and it shows up the moment the stakes get real. Agentic engineering is a different discipline. You're not prompting for code. You're decomposing problems, designing system boundaries, writing specs precise enough that the agent doesn't go sideways. You review everything it builds, because it will make mistakes that only look wrong if you know what correct looks like. You guide it. You catch what it misses. If you don't know what a distributed transaction is, the agent won't save you. It'll generate something broken with complete confidence, and you won't know until production. The hard part of software was never writing the first 200 lines. It never was.

We merged an early C# 15 preview feature into .NET 11 preview 3: unions. Adds union declarations (`union Pet(Cat, Dog, Bird) { ... }`) and union types (attributed with `[Union]`). They can be treated by pattern matching/switch expressions as a closed set for exhaustiveness.

#AI can generate microservices in seconds. But it usually forgets timeouts, retries, and circuit breakers. Next week I’ll run a live demo where we generate services with AI and then break them by injecting latency. No slides. Just a terminal. buff.ly/pGTsQx7

ReSharper 2026.1 EAP 7 is here! This build introduces the Monitoring tool window, bringing runtime performance monitoring previously available in @JetBrainsRider. Observe key runtime metrics all in one place to better understand how your application behaves as it runs. Available with a dotUltimate subscription. Download the build here: jetbrains.com/resharper/next…

New tale: talesfrom.dev/blog/the-ambig… in which we see developers and architects interpreting diagrams. #objectorienteddesign #functionalprogramming #empathydrivendesign #domaindrivendesign #softwarearchitecture #softwaredesign #collaborativesoftwaredesign

i cannot believe how much better 5.3 is than 4.6. after some internal testing results show its 15.2% better

New article: AI-generated tests as ceremony. blog.ploeh.dk/2026/01/26/ai-…

New tale: talesfrom.dev/blog/cocoa-fro… in which a team tries to analyze a business workflow and fails to communicate with each other. What is COCOA? How does it compare to: Ports & Adapters, Vertical Slices (and others)? What can software engineers learn from enterprise architecture?