batu

Founder @haxx_studio / Design engineer

[Dip Wheeler @DipWheeler]

"you're 8 months behind on chipotle klarna payments because you've been saving up for the spacex ipo?"

[batu @batudal]

We’re not debating whether AI matters.

We’re ignoring who’s going to pay the cost of finding out.

And right now, that bill is being quietly charged to the growth of an entire economy.

#AIStocks #AIHype #TechCommunity

[batu @batudal]

The US grew 2% last year.
1.3% of that came from AI-related stocks.

More than half the growth of the world’s largest economy is riding on a financial bet.

That’s not a tech sector. That’s an entire economy going all in. 🧵

[batu @batudal]

The technology is real. Probably one of the most important of our lifetime.

But Jamie Dimon put it well: cars changed the world, TV changed the world. Most people who invested in them at peak hype didn’t do well.

[batu @batudal]

The biggest threat to web security in 2026 isn’t just hackers. It’s the collision of two trends most companies still underestimate:

🔴A generation of developers shipping code without security fundamentals.
🔴AI dramatically accelerating offensive cyber capabilities.

We’re already seeing the effects. Supply chain attacks are scaling. AI can scan, probe, and exploit faster than human teams ever could.

This isn’t an “AI problem.”
It’s a cybersecurity problem.

AI can absolutely strengthen defense. But until security education, tooling, and standards become embedded across the ecosystem, breaches will keep accelerating.

At @haxx_studio, that’s exactly how we build.
Security isn’t a feature.
It’s the standard.

[batu @batudal]

AI companies don't need to be profitable. They just need the press to act like they are.

[batu @batudal]

Mind-Blowing Growth" is the headline @WSJ gave to an optimistic projection for a company that is, right now, losing money.

[batu @batudal]

While we celebrate hypothetical profits with undisclosed math, here's what's actually happening:
→ Microsoft canceled its internal Claude Code licenses. Token billing got too expensive. For Microsoft. → Uber burned through its entire 2026 AI budget in four months. → AI software prices up 20-37%. GitHub killing flat-rate plans.

[Timothy Ash @tashecon]

Was at BBVA Turkiye conference in London and everyone’s mobile phone pinged at the same time as the CHP news hit the wires - people heading back to offices.

[batu @batudal]

The rich aren't cheating the system. They're following it perfectly. That's the problem.

It's inevitable under current tax laws that a tiny percentage will keep taking a bigger share of the wealth.

Imagine your passive income is 100 times your expenses.
What would you do with that money?
Buy more assets, stocks, land, houses.
Why cash it in when you can keep compounding and borrow tax-free to fund your expenses?

It's not even their fault.
They're just playing the game the system sets up. Hoarding assets is the default way to keep winning in this setup.

I just watched @garyseconomics, former top trader and inequality economist, on the #ProfGPod with @profgalloway, and one thing stood out: we need a safe space for real intellectual debate on this.
No more populist policies with loopholes.
A holistic approach using inheritance laws, locality of assets, and specialized wealth taxes to stop extreme wealth accumulation.

What do you think it'll take to change this?
Drop your ideas below or follow for more insights.
Full Interview: https://t.co/SokmOwzfyS

[Jason Fried @jasonfried]

Bragging about how much software you’re shipping with AI is like holding down the shutter button and bragging about how many photos you took.

[batu @batudal]

@PostgreSQL just made a common backend headache vanish.

The database is quietly fixing a papercut every backend engineer has worked around: the "get-or-create" pattern.

The idea is simple: try to insert a record. If it already exists, return it. If not, create it.

For a decade, INSERT ... ON CONFLICT gave us two options, and both had problems.

DO NOTHING returned nothing if the record already existed.

DO UPDATE worked, but generated dead tuples for writes that changed nothing.

The workaround was a complex CTE that everyone knew how to write but nobody enjoyed reading.

Now, with ON CONFLICT DO SELECT, things change.

It returns the existing row through RETURNING. No write, no bloat, no gymnastics.

Benchmarks show it's roughly 4x faster than the no-op DO UPDATE workaround we've all reached for.

Sometimes the best features are the ones that quietly erase a workaround you forgot you were making.

#PostgreSQL #DataEngineering #DevOps