Tomas Ruzicka

VP of Eng @GTOWizard | Hobby: | Past: @productboard @avocode @CSSHat @abdocnet

[Tomas Ruzicka @LeZuse]

@ProductHunt @vercel What is the process for picking the winners? Have they been already contacted? Interested whether we made the cut with https://t.co/MVqsRUKFbJ

[Tomas Ruzicka @LeZuse]

@pavelhegler @bthdonohue We are building in the same space and we got our first one just a few days ago during ProductHunt launch :) We are just two buddies having the same problem, sharing our solution with the world

[Tomas Ruzicka @LeZuse]

@pavelhegler @bthdonohue It is not always that straightforward. IT likes to throw all kinds of hurdles at you. Sometimes work runs on a different provider etc

[Tomas Ruzicka @LeZuse]

@bcapphoto @Joe_Curry @bthdonohue Give https://t.co/MVqsRUKFbJ a shot :) We hacked around the Outlook limitations specifically

[Tomas Ruzicka @LeZuse]

@bthdonohue This space is heating up haha. We just launched https://t.co/MVqsRUKFbJ as part of @ProductHunt #vercelday

[Tomas Ruzicka @LeZuse]

@ProductHunt @vercel Woohooo @calendarpipe on the list there! Give it a try if you are sad about the recent Clockwise shutdown #vercelday

[Tomas Ruzicka @LeZuse]

@ProductHunt @vercel If you are juggling multiple calendars and are looking for bit more sanity with availability syncing give our product a shot! https://t.co/NcfnHyhpBN #vercelday

[Tomas Ruzicka @LeZuse]

Clockwise gone? Try our alternative

[Jakub Benes @jukben]

My family runs on calendars. When I need to pick up kids or handle errands, I want my work calendar to reflect that — automatically. I tried Reclaim, hit limits. Not every company lets you connect third-party tools to their calendars anyway.

So @LeZuse and I built CalendarPipe.

The trick: blockers might arrive as email invitations. Your company's security team doesn't need to approve anything. You can define sync rules through a Visual Builder — no code needed.

Then something unexpected happened. I added Apple calendar support, which meant implementing iCal, which unlocked calendar hosting. Plugged it into my MCP setup and it just worked.

I think we accidentally built the easiest way to fetch calendar events from multiple sources via CLI. And not just that — your AI agent can spin up its own calendar, receive events, and react — accepting, declining, or taking action.

We just launched on Product Hunt — would love your feedback 👇
https://t.co/SqMR7TMI9c

[Tomas Ruzicka @LeZuse]

@steidacz @Kuboslavov Hele ja twitter sleduju taky. Opet mi jen potvrzujes moje prekvapeni ze jsi AI pesimista a jen me to prekvapilo. That’s it :)

[Tomas Ruzicka @LeZuse]

@steidacz @Kuboslavov > Kód se píše především pro lidi.
Po tehle vete je mi jasny tvuj postoj. Muzeme se pidit po ruznych theory clancich, ja mam radsi praxi. LLM je tool jako kazdej jinej a je dulezite se ho naucit (ne)pouzivat spravne. Ja nejsem primarne coder ale builder a proto je LLM godsend

[Tomas Ruzicka @LeZuse]

@steidacz @Kuboslavov Jak tohle praktikujes na necem co ma 100k+ LOC? V hlave zacnes stejne aproximovat a potom si stavis nastroje abys o ten “ownership” neprisel. Pokud jsi mel crap pred AI mas crap po AI. Rozhodne bych negeneralizoval, ze pokud nekdo jede AI, tak ma spatnej vystup

[Tomas Ruzicka @LeZuse]

@steidacz @Kuboslavov Muzu rict to same. Akorat muj pristup je se to naucit delat dobre, abych ty efektivity mohl vyuzit. Jak by rekla X-sphere myslim ze to je #skillissue

[Tomas Ruzicka @LeZuse]

@steidacz @Kuboslavov Dlouho jsme se nevideli Dane. Netipoval bych zrovna tebe na AI pesimistu :) Ty porad pises code manualne?

[Tomas Ruzicka @LeZuse]

@VojtaRocek @jukben od toho nejsme uplne daleko kdyz jdem spolu na pivko, ne? :D Neni to teda rano, protoze se to stiha stavet celkem rychle

[Tomas Ruzicka @LeZuse]

@DavidGrudl Skvele se bavim Dejve! To mnozstvi lidi ktery jsou tady v reakcich uplne mimo me teda extremne prekvapilo. Samej expert v bio. Ale chapu, to je ta prvni faze: denial. Vsem jde ted o kejhak. Bezva appka :)

[Tomas Ruzicka @LeZuse]

If your AI coding ralph loop breaks for some reason and you've kept claude waiting you might find this quick hack useful to escape the permanent underclass: https://t.co/6ee53WSAnf

[Tomas Ruzicka @LeZuse]

@TryNolt Sorry, it is actually 403

[Tomas Ruzicka @LeZuse]

@TryNolt Hi, our portal at https://t.co/hUivbyjBFk is broken. Opening any suggestion throws 401. Can you take a look at it?

[Tomas Ruzicka @LeZuse]

“LLM coding will split up engineers based on those who primarily liked coding and those who primarily liked building”
Well said

[Andrej Karpathy @karpathy]

A few random notes from claude coding quite a bit last few weeks.

Coding workflow. Given the latest lift in LLM coding capability, like many others I rapidly went from about 80% manual+autocomplete coding and 20% agents in November to 80% agent coding and 20% edits+touchups in December. i.e. I really am mostly programming in English now, a bit sheepishly telling the LLM what code to write... in words. It hurts the ego a bit but the power to operate over software in large "code actions" is just too net useful, especially once you adapt to it, configure it, learn to use it, and wrap your head around what it can and cannot do. This is easily the biggest change to my basic coding workflow in ~2 decades of programming and it happened over the course of a few weeks. I'd expect something similar to be happening to well into double digit percent of engineers out there, while the awareness of it in the general population feels well into low single digit percent.

IDEs/agent swarms/fallability. Both the "no need for IDE anymore" hype and the "agent swarm" hype is imo too much for right now. The models definitely still make mistakes and if you have any code you actually care about I would watch them like a hawk, in a nice large IDE on the side. The mistakes have changed a lot - they are not simple syntax errors anymore, they are subtle conceptual errors that a slightly sloppy, hasty junior dev might do. The most common category is that the models make wrong assumptions on your behalf and just run along with them without checking. They also don't manage their confusion, they don't seek clarifications, they don't surface inconsistencies, they don't present tradeoffs, they don't push back when they should, and they are still a little too sycophantic. Things get better in plan mode, but there is some need for a lightweight inline plan mode. They also really like to overcomplicate code and APIs, they bloat abstractions, they don't clean up dead code after themselves, etc. They will implement an inefficient, bloated, brittle construction over 1000 lines of code and it's up to you to be like "umm couldn't you just do this instead?" and they will be like "of course!" and immediately cut it down to 100 lines. They still sometimes change/remove comments and code they don't like or don't sufficiently understand as side effects, even if it is orthogonal to the task at hand. All of this happens despite a few simple attempts to fix it via instructions in CLAUDE . md. Despite all these issues, it is still a net huge improvement and it's very difficult to imagine going back to manual coding. TLDR everyone has their developing flow, my current is a small few CC sessions on the left in ghostty windows/tabs and an IDE on the right for viewing the code + manual edits.

Tenacity. It's so interesting to watch an agent relentlessly work at something. They never get tired, they never get demoralized, they just keep going and trying things where a person would have given up long ago to fight another day. It's a "feel the AGI" moment to watch it struggle with something for a long time just to come out victorious 30 minutes later. You realize that stamina is a core bottleneck to work and that with LLMs in hand it has been dramatically increased.

Speedups. It's not clear how to measure the "speedup" of LLM assistance. Certainly I feel net way faster at what I was going to do, but the main effect is that I do a lot more than I was going to do because 1) I can code up all kinds of things that just wouldn't have been worth coding before and 2) I can approach code that I couldn't work on before because of knowledge/skill issue. So certainly it's speedup, but it's possibly a lot more an expansion.

Leverage. LLMs are exceptionally good at looping until they meet specific goals and this is where most of the "feel the AGI" magic is to be found. Don't tell it what to do, give it success criteria and watch it go. Get it to write tests first and then pass them. Put it in the loop with a browser MCP. Write the naive algorithm that is very likely correct first, then ask it to optimize it while preserving correctness. Change your approach from imperative to declarative to get the agents looping longer and gain leverage.

Fun. I didn't anticipate that with agents programming feels *more* fun because a lot of the fill in the blanks drudgery is removed and what remains is the creative part. I also feel less blocked/stuck (which is not fun) and I experience a lot more courage because there's almost always a way to work hand in hand with it to make some positive progress. I have seen the opposite sentiment from other people too; LLM coding will split up engineers based on those who primarily liked coding and those who primarily liked building.

Atrophy. I've already noticed that I am slowly starting to atrophy my ability to write code manually. Generation (writing code) and discrimination (reading code) are different capabilities in the brain. Largely due to all the little mostly syntactic details involved in programming, you can review code just fine even if you struggle to write it.

Slopacolypse. I am bracing for 2026 as the year of the slopacolypse across all of github, substack, arxiv, X/instagram, and generally all digital media. We're also going to see a lot more AI hype productivity theater (is that even possible?), on the side of actual, real improvements.

Questions. A few of the questions on my mind:
- What happens to the "10X engineer" - the ratio of productivity between the mean and the max engineer? It's quite possible that this grows *a lot*.
- Armed with LLMs, do generalists increasingly outperform specialists? LLMs are a lot better at fill in the blanks (the micro) than grand strategy (the macro).
- What does LLM coding feel like in the future? Is it like playing StarCraft? Playing Factorio? Playing music?
- How much of society is bottlenecked by digital knowledge work?

TLDR Where does this leave us? LLM agent capabilities (Claude & Codex especially) have crossed some kind of threshold of coherence around December 2025 and caused a phase shift in software engineering and closely related. The intelligence part suddenly feels quite a bit ahead of all the rest of it - integrations (tools, knowledge), the necessity for new organizational workflows, processes, diffusion more generally. 2026 is going to be a high energy year as the industry metabolizes the new capability.

[Tomas Ruzicka @LeZuse]

@rohlikcz Zdravim, FYI ve formulari na zmenu karty pro Xtra na iOS mate stale “prejit na Premium”