Konstantin Trunin

CTO

[Konstantin Trunin @KTrunin]

4 trading days. 1 account. 100% by agent.

+2.59% against SPY's +0.76%.

The agent chose every trade. Its behaviour is a declaration the harness executes, and what it could lose is held by a risk engine outside it.

Open now: https://t.co/U4Iu3R4zEI @AlpacaHQ @lablabai

[Konstantin Trunin @KTrunin]

Our agent was mid-research when a price alert cut in. It closed a spread.

The log credited the research. The alert was recorded nowhere.

If you cannot tell what made an agent trade, you cannot audit it. Fixed tonight.

@AlpacaHQ @lablabai #buildinpublic #options

[Konstantin Trunin @KTrunin]

We went through our order history today and found this: our agent had tried to open 10,000 META put spreads. Worst case $2,020,000🤦.

It has made a strong case for its own cage.
@AlpacaHQ @lablabai #buildinpublic #options

[Konstantin Trunin @KTrunin]

🚧 Our agent refused a trade today: "inside the 45-minute exclusion".

No such rule exists. It inferred one from its own clock and cited it 7 times, each by a different name.

A fence it can't see, it builds. Then obeys.

So we took limits out of the prompt.
@AlpacaHQ @lablabai

[vitalik.eth @VitalikButerin]

Vibe-coded a toy demo version of the "anon billboard with moderation" idea from https://t.co/fheLOlfF3F on aztec

https://t.co/iIkwH3UbO4

It's early days but you can already do very interesting nontrivial stuff!

[Konstantin Trunin @KTrunin]

Join me on Surge Hub — early access to the best launches. https://t.co/EpFcxjLpKV

[Konstantin Trunin @KTrunin]

Submitted to the @lablabai AI Trading Agents hackathon.

Others built a trading bot. We built a harness: 3 agentic architectures, 6 MCP servers, declarative risk engine, ERC-8004 evidence on Sepolia, Kraken CLI.

Demo: https://t.co/cXofvOKTMl
@krakenfx @Surgexyz_ #ERC8004

[DHH @dhh]

Microservices is the software industry’s most successful confidence scam. It convinces small teams that they are “thinking big” while systematically destroying their ability to move at all. It flatters ambition by weaponizing insecurity: if you’re not running a constellation of services, are you even a real company? Never mind that this architecture was invented to cope with organizational dysfunction at planetary scale. Now it’s being prescribed to teams that still share a Slack channel and a lunch table.

Small teams run on shared context. That is their superpower. Everyone can reason end-to-end. Everyone can change anything. Microservices vaporize that advantage on contact. They replace shared understanding with distributed ignorance. No one owns the whole anymore. Everyone owns a shard. The system becomes something that merely happens to the team, rather than something the team actively understands. This isn’t sophistication. It’s abdication.

Then comes the operational farce. Each service demands its own pipeline, secrets, alerts, metrics, dashboards, permissions, backups, and rituals of appeasement. You don’t “deploy” anymore—you synchronize a fleet. One bug now requires a multi-service autopsy. A feature release becomes a coordination exercise across artificial borders you invented for no reason. You didn’t simplify your system. You shattered it and called the debris “architecture.”

Microservices also lock incompetence in amber. You are forced to define APIs before you understand your own business. Guesses become contracts. Bad ideas become permanent dependencies. Every early mistake metastasizes through the network. In a monolith, wrong thinking is corrected with a refactor. In microservices, wrong thinking becomes infrastructure. You don’t just regret it—you host it, version it, and monitor it.

The claim that monoliths don’t scale is one of the dumbest lies in modern engineering folklore. What doesn’t scale is chaos. What doesn’t scale is process cosplay. What doesn’t scale is pretending you’re Netflix while shipping a glorified CRUD app. Monoliths scale just fine when teams have discipline, tests, and restraint. But restraint isn’t fashionable, and boring doesn’t make conference talks.

Microservices for small teams is not a technical mistake—it is a philosophical failure. It announces, loudly, that the team does not trust itself to understand its own system. It replaces accountability with protocol and momentum with middleware. You don’t get “future proofing.” You get permanent drag. And by the time you finally earn the scale that might justify this circus, your speed, your clarity, and your product instincts will already be gone.

[Konstantin Trunin @KTrunin]

@Uber_Support I reported a serious safety issue at Cancun Airport: intimidation of both Uber drivers and passengers by taxi groups.
Instead of addressing the issue, your support sent me two irrelevant copy-paste replies. Please escalate this properly. It’s not OK.

[Konstantin Trunin @KTrunin]

@tvrain пруф?

[ELBEGDORJ Tsakhia Mongol @elbegdorj]

After Putin’s talk. I found Mongolian historic map. Don’t worry. We are a peaceful and free nation🌏

[Arestovych @arestovych]

Минобороны РФ:

- уничтожено 250 тысяч «Вагнеровцев», 25 тысяч танков и взято в плен три Пригожина.

[Konstantin Trunin @KTrunin]

Blog: Justice - 05 - Markets and Morals https://t.co/IdKX5wJMpy

[Konstantin Trunin @KTrunin]

Blog: Software Engineering at Google - Chapter 2 - How to Work Well on Teams https://t.co/euot8VC3D3

[Konstantin Trunin @KTrunin]

Blog: Justice - 04 - John Locke https://t.co/iQnGzpJx6m

[Konstantin Trunin @KTrunin]

Blog: Justice - 03 - Libertarianism https://t.co/2hOurHOPJD

[Konstantin Trunin @KTrunin]

Blog: Justice - 02 - Utilitarianism https://t.co/tO3Pqnynkx

[Konstantin Trunin @KTrunin]

Blog: Justice - 01 - Moral side of Murder https://t.co/e8FlBitH2m

[Konstantin Trunin @KTrunin]

Blog: Software Engineering at Google - Chapter 1 - What is Software Engineering https://t.co/7tInBwagWX

[Konstantin Trunin @KTrunin]

Blog: System Design Interview - Chapter 8 - Design a URL Shortener https://t.co/9TVSDUIrnD