u/aisatsana__

AI makes ad hoc operational work so easy that we stop building the tools around it. Why write a script when you can just ask Claude or Copilot to restart the canary? Why build a dashboard when ChatGPT can summarize today’s deploy status in 15 seconds? Because that 15-second conversation, repeated by 50 engineers 20 times a day, stops being convenience and starts becoming a tax.

It’s 2026, and AI agents are taking over more and more of our busywork. I personally rely on them for a lot of boring, but increasingly complex tasks. We do hear about security, staying safe, and the term prompt injection gets thrown around. But that can sound technical; devs are supposed to solve that, with code and stuff, right? Or it can sound doomery; it’s just AI naysayers protesting progress! 

I like a good challenge, so I decided to construct some prompt injection attacks to see how hard it is to put them to use and what kind of a threat they pose. I invite you to join me in this mini red teaming exercise, let’s hack the planet some LLMs. 🙃

We recently run into quite nasty edge case with Debezium + PostgreSQL failover. Everything looked healthy after failover, connector was running, database was fine, no obvious errors. But problem was replication slot on new primary could start ahead of offset stored by Kafka Connect. Basically you can end with situation where Debezium thinks it should continue from one LSN, while Postgres already lost part of WAL it needs. And connector can look “healthy” while you actually have a gap in CDC. We tested few approaches with Patroni and PostgreSQL 16, and also looked into what changes with PG17 failover slots.

While testing a Kotlin microservice backed by MS SQL, I found several places where convenience had quietly become a liability. Fortunately, there was no production incident; most issues were detected during internal testing. It is always better to learn on someone else’s mistakes, this article will help you learn on mine

At Devoxx UK in London, we caught up with Eoin Woods - co-author of three software architecture books and former CTO of Endava, to find out why beautifully designed systems still break in production.

P.S. posting again with the different flair. Originally, I've put "conference" flair (because this conversation took place at DevoXX, UK) but mods removed it suggesting me to change the flair. Hope it work this time.

Larger pull requests bring more bugs. Stephen Poletto, Field CTO at Span, used his CTO Craft Con talk in Toronto to argue that the AI tooling wave has arrived with a familiar problem attached: organizations are reaching for the most legible metric available rather than the most meaningful one. The result is a rerun of every previous failed attempt to quantify developer productivity, but this time with a pretty substantial compute bill.

U normalnim zemljama ove stvari subvencioniše država, ali da. Hajde da pomognemo deci

Članak: Srbija ne može da izdvoji €2.000 za najbolje fizičare, pa posle ‘zašto mladi odlaze?’

Tim srednjoškolaca koji je izborio plasman na Međunarodni turnir mladih fizičara (International Young Physicists’ Tournament – IYPT) u Cirihu još nema obezbeđena sredstva za put i boravak u Švajcarskoj. Zbog toga su Turnir mladih fizičara Srbije i Udruženje mladih fizičara “Spinor” pokrenuli kampanju za prikupljanje sredstava.

We asked developers to spill their little dirty secrets, the lies they tell their managers and what actually creates tension in teams. One theme that kept coming up was the gap between how software development looks from the outside and what it actually looks like in practice.