Published: Don’t Let AI Invert The Testing Pyramid
AI has not changed a single thing about the mechanics of software delivery. The fundamental principles, including the Testing Pyramid, are still valid and necessary.
thinkinglabs.io/articles/202...
Software has always been buggy shit, but when you see stuff like this, you cant help but think this is the result of some mandated vibe coding shite
(cant wait to use my pens on NYE 2199, when I am the ripe age of 216)
Fragments: 80,000 people's opinion on AI, fixing the common gap in spec-driven development, weakening defenses against covert attacks on the U.S.
martinfowler.com/fragments/20...
New evidence suggesting AI is amplifying the already existing skills gap. Demand for experienced folks ⬆️, junior/entry level 👎
That means harder hiring, salary inflation, slower execution, and more delivery risk. Wrote about this risk only in Feb, further thoughts here:
Who needs to grow tomatoes when we've got pasta sauce?
If you're an architect or tech lead, making authoritative decisions based on your technical expertise is probably what got you to where you are. That probably still feels like the right thing to do.
That's exactly what makes it tricky.
>>>
No, AI is not coming for your developer job, regardless of the nonsense the hype mongers are pushing. (I'm talking just about developer jobs—it obviously impacts other areas.) That's not to say the layoffs aren't real, but rather that the corporations are hiding normal corporate behavior behind
1/11
Threads thread: thriller_instinct 3d Is it okay to bully 40 and 50 year olds who are on social media just for being on it, cuz like why are you here - 254 Q 3.1K G 28 746 corporateash 18h ••• My ICQ UIN is 7231680. That number is burned into my consciousness. I inadvertently learned that you could see private conversations in public chat rooms when using Telnet instead of a browser on GeoCities. I can tell you the difference in audible dial-up handshakes between 1200, 2400, 14.4 kbps modems. I needed a edu email address to join Facebook after my university was admitted. We were here at the beginning. We made social media. You wouldn't be in my Top 8. I have usernames older than you. 852 Q62 G6 72
“I have usernames older than you.”.
Holy shit
The only way to speed up an entire system is to address the entire system, especially any bottlenecks. The bottleneck is only rarely the coding. Spotify, which has gone full AI to write its code, hasn't laid anybody off because it understands these issues.
8/11
The Drake meme but for writing docs.
Watching devs suddenly discover that the ability to write was important all along...
“SaaS is dead. Everyone will just create what they need”
I think this underestimates what a PITA it is to create software.
Lots more short form video content is created today than ever before. The tools are now ubiquitous. The vast majority still just consume it.
If you run a company whose entire value proposition is the ability to see patterns, predict outcomes, and connect dots that others miss, you’d think someone in the building might have flagged that suing a small independent magazine over unflattering-but-accurate reporting would only guarantee that millions more people read it.
Love this headline and the whole first sentence 😂
«Palantir Sues Swiss Magazine For Accurately Reporting That The Swiss Government Didn’t Want Palantir»
@adfichter.bsky.social
www.techdirt.com/2026/02/27/p...
Move along now; there’s nothing to see here
Serhii Tatarintsev's post on LinkedIn: Recently, I had conversation with a candidate that completely changed the way I think about interviews. Let me explain. At first, it seemed like they are not a particulary good fit — not a lot of experience in our field, no familiarity with our tech stack. That is, until I asked one simple question: “Do you have any references or recommendations?” “How about a reference from my good friend Ben Franklin?” — candidate winked at me and dropped a neatly arranged stack of bills onto the table. Needless to say, he was hired on the spot. So, sometimes it’s not the candidates that fail the interview — it’s you interview process that fails to ask the right question that would let them shine.
Serhii Tatarintsev's post on LinkedIn: Let's talk about technical interviews. We all agree that asking engineers to reverse the binary tree on a whiteboard is an outdated approach, right? But what do we do instead? Here is my solution. I ask them to reverse a real tree in my garden. I now have a whole orchard of upside-down apple trees and a whole team of exceptionally strong engineers. Not a single bug was found in my garden since we changed our interview strategy. It just shows you that in order to stay ahead in the industry built on innovation you always have to look for novel approaches even for decade-old problems.
contest is over, y'all. my colleague already won linkedin
Out of curiosity, inside 'external' you would have the adapters implementing the ports, and within the right subfolder depending whether they are inbound or outbound. Am I assuming right?
CRUD only seems simpler because you're leaving the workflows to be assembled by each user in their heads.
Tell me you've never worked with COBOL without telling me you've never worked with COBOL.
If you're attending college now, and you're looking for a surefire career that will net you great pay for the foreseeable future, learn COBOL.
You'll make a fortune fixing all the damage AI does to banks.
Están desesperados. Hay mucho dinero invertido y cada vez menos perspectivas. Esto no está reñido con su utilidad como herramienta, pero no son ni mucho menos el reemplazo de la mano de obra que quieren vender. Solo espero que el batacazo financiero ocurra pronto, ya solo por la paz mental
Unacceptable
a 90s wooden computer desk with towers and drawers and lots of storage
this was basically the model we had. it was glorious. we've strayed so far from the light
the computer should have never left this room. we have to go back
Pattern card: Distributed Monolith (Architecture). Stats: Latency 95/100, Pain 99/100, Maintain 5/100, Resume HIGH. Quote: "Why call a method locally when you can send a synchronous HTTP request across three availability zones?". Special ability: Cascading Failure - If one service fails, the entire cluster throws 500s. Stack trace size: 400MB.
# Analysis The result of taking a spaghetti codebase and throwing it across the network. Driven by the cargo cult of "Microservices," architects often slice a highly coupled system into smaller pieces without actually establishing bounded contexts or autonomous data ownership. You haven't decoupled your domains; you've merely decoupled your deployment artifacts. By doing so, you have successfully replaced highly optimized, in-memory local function calls with unreliable network hops, JSON serialization overhead, and eventual inconsistency. **The Reality:** To deploy a single, trivial feature, four different teams must orchestrate their releases in a highly specific, coordinated sequence, essentially recreating Waterfall over a CI/CD pipeline. Local development is practically impossible unless developers are issued laptops with 64GB of RAM to run 15 interdependent containers via `docker-compose`. When a user clicks "Checkout", the system initiates a fragile, synchronous HTTP chain reaction across six different services. If just one sidecar proxy hiccups, the entire transaction collapses, leaving the database in an inconsistent state and generating a distributed stack trace large enough to trigger your logging provider's billing alerts. You traded a simple `NullPointerException` for a `504 Gateway Timeout`.
For some weekend fun:
🚨 WoB PATTERN: Distributed Monolith
"Why call a method locally when you can send a synchronous HTTP request across three availability zones?"
worstofbreed.net/patterns/dis...
#worstofbreed #SoftwareArchitecture #MaintenanceNightmare #TechHumor
It's amazing that coding agents allow you to build quickly to validate ideas. But the outcome should be treated as a throw-away prototype. A long term sustainable software requires skilled developers because of the reasons Allen exposed
Every day I am filled with hate because my heart overflows with my love of the computer. aftermath.site/ram-prices-h...
Fragments: LLMs make our days harder, an LLM reacts badly to a rejected pull request, the Promptware Kill Chain, horror and elation trying Claude Code for two weeks, Free Speech Poseurs' silence to real threats
martinfowler.com/fragments/20...
And allow me to clarify: I do not expect to provide a spec, API and go to sleep expecting the rest to be automated and deterministic. But have an inspection loop, TDD style: provide minimum spec, prompt to implement, run and verify tests, increment spec, repeat.
Of course, by no means I meant that an LLM is an abstraction like modern languages and compilers are over assembler. I meant devs operating and directing the process at a higher abstraction level: Gherkin style specs, APIs, modules...
I mean wouldn't the human be in the process of building but just a different level of abstraction?
