Backend ⚡ Java/Kotlin, PostgreSQL, Cloud. 🛠️ Recovering overengineer.
Brno 🇨🇿
Joined May 2009
- Tweets28.2K
- Following585
- Followers2K
- Likes30.8K
Pinned Tweet
What is the first thing you should do when starting a new PostgreSQL project that will save you countless headaches?
filip-prochazka.com/blog/new…
Filip Procházka retweeted
Devs a year ago: "Code is a liability. PR's that delete 100 lines of code >> PR's that add 1,000 lines"
Devs now: "This ai slop canon can produce 50,000 lines of unreviewed code a day and you'll destroy this company's future if you delay it from merging"
Filip Procházka retweeted
thank you for the hard work, Claude, but i would have appreciated at least calling it "our laptop"
Filip Procházka retweeted
this whole "i'll build my own" wont last another 3 months
for decades bros can't even keep their copyright footer text updated, imagine keeping 5 apps running
never
Filip Procházka retweeted
Hard to overstate how big of a deal this is.
tl;dr — ANY unpatched Linux server with even a single TCP port exposed to the internet (say for HTTP or SSH) and MPTCP active (default for many Go web servers) is vulnerable to complete takeover.
What a disaster atlasum.net/blog/cve-2026-98…
Filip Procházka retweeted
So much rhetoric about monorepos being bad for agents primarily from people who have no idea how git works clearly.
`git log -- folder_in_mono_repo`
wow look at that perfect history for only one app in a monorepo.
Anyone who has literally ever tried to ship software quickly across a microservice mesh that inevitably arises from separate repos knows how insane this is to choose.
"What if deploying required sequencing eight separate steps and required writing code in 8 different places both forward and backwards compatible?"
Please. Just use a monorepo and make a monolith, extracting services only when failure characteristics and other boundaries *truly* require it.
who thinks monorepos are good for agents
they absolutely are not, it's a completely wrong pattern for agents, it ruins their ability to navigate history because it removes the project specific container
there's zero benefit from monorepos now that we have agents, only downsides
monorepos were solving a different problem that's no longer even relevant
Filip Procházka retweeted
The 10-year database architecture cycle:
2015: SQL is obsolete. Schemas are too rigid. Put everything in NoSQL JSON documents.
2018: Wait, we need to join users and orders. Let's write a 400-line nested loop in JavaScript to join them in RAM.
2021: Wait, if the server crashes halfway through the loop, we lose money. We need ACID transactions.
2026: Quietly puts everything back in PostgreSQL and never speaks of it again.
Filip Procházka retweeted
Don't even ping me for review until:
> lint, types and tests all pass
> CI is fully green
> zero open comments or nits
> the diff is lean, almost no code comments
> the agent reviewers have reviewed and approved
> there's proof it works, not just "done"
Then you can ask me to review and merge.
Filip Procházka retweeted
every product i use should just be a headless mcp, that feeds into an agent, where i never have to think about anything underneath.
except for our product, of course.
in our product, customers love the ui and love us very much.
we're special that way.
I'm honestly asking myself the same for some time now.
But most tests AI writes are the worst of the worst, equivalent to what low-skill devs wrote to pass artificial coverage % gates - huge test methods mocking everything, etc. - awful....
Filip Procházka retweeted
i spent my whole four-decade career as a software engineer watching parts of my expertise replaced by tooling. AI is no different. the real question is: what has it left?
i could list lots of things but i'll make it simple:
LLMs cannot say:
"Leave it with me, i'll get back to you when it's resolved".
"I don't think that's a good idea and here's why".
"We tried that before and here were the issues".
and that matters a lot. we hear from people who think that removing the humans is simple because "now it's just architecture and infrastructure" but frankly these people either live in a bubble or a too narrow minded to understand what they have been delegating to humans all these years.
and the SMEs who think they can just build systems in their down time? sure bro. when your primary role is finding customers you're really going to prioritise a prompting session ahead of finding customers or keeping your accreditations active.
people who pump out a game only they've played and now thing they are game creators when their games are circa 1980s in complexity.
people whose entire software "engineering" experience is that of a ticket monkey who only had a job because the repetitive rote translation of rules to code couldn't be scaled without employing lots of humans.
be careful of opinions from:
- people who stand to gain from AI adoption (they don't care if their words are true, they just want you to spend money seeing if they are).
- people who work in closed environments. i.e. people who punt a single product/library etc. to a receptive audience (web browsers fall into this). a market that pulls is not the same as a market that requires you to push.
- people who just run benchmarks and waffle shit about LLMs all the time, have no skin in the game, and haven't shipped a thing in their lives.
- people selling books, courses, and pumping their social media numbers for payouts
yes, shit is happening, but it's not over. it's just a correction. the necessary human bloat of the past 10-20 years is probably over, not the discipline and certainly not software engineering.
Over the coming years, more and more people will see parts of their expertise replicated by AI, and many of them are going to be extremely upset about it and shame you for thinking it's neat.
The software profession is in the middle of this right now, and it's pretty ugly. It's coming to a lot of other professions soon.
I'm curious whether they’ll take it as badly as some programmers have, or if we’re just an unusually sensitive bunch 😅