Border radius on buttons was the last thing still doing its own thing. I moved it into a single CSS variable and made the treatment more subtle. Now every border follows the same rule instead of having its own opinion. Before & After 👇

I bought a car 🚗

Border radius on buttons was the last thing still doing its own thing. I moved it into a single CSS variable and made the treatment more subtle. Now every border follows the same rule instead of having its own opinion. Before & After 👇

Styling with Tailwind feels like being trapped in a cage. You get some speed at the start, but the moment you want real control you're stuck. Only pure CSS gives you raw power. Change one variable and the border-radius updates everywhere in your UI. That's it. You can't beat that.

Hetzner increases prices once again 😭

Styling with Tailwind feels like being trapped in a cage. You get some speed at the start, but the moment you want real control you're stuck. Only pure CSS gives you raw power. Change one variable and the border-radius updates everywhere in your UI. That's it. You can't beat that.

I had tiered pricing for my product. Spent basically the whole day thinking about it. Then I woke up and was like, fuck it. This is too complicated and the product isn't even live yet. I want the first people who try it to feel welcome, not overwhelmed So I changed it to just $19/mo. One plan only

Hetzner increases prices once again 😭

I had tiered pricing for my product. Spent basically the whole day thinking about it. Then I woke up and was like, fuck it. This is too complicated and the product isn't even live yet. I want the first people who try it to feel welcome, not overwhelmed So I changed it to just $19/mo. One plan only

Okay, I really didn’t expect this Rust → Ruby conversion 😅 xlii.space/eng/from-rus...

What if the optimal path is: 1. Build in Ruby (ship fast) 2. AI-convert to Go/Rust (run fast) The Bun [Zig -> Rust] rewrite suggests the "rewrite everything later" cost is collapsing. Still a bad idea?

The moment we install a new tool or framework, we start hunting for the “real” setup. We assume the defaults must be inferior simply because they’re common. They’re not. kyrylo.org/2026/05/20/s...

The moment we install a new tool or framework, we start hunting for the “real” setup. We assume the defaults must be inferior simply because they’re common. They’re not. kyrylo.org/2026/05/20/s...

I chose yellow backgrounds and orange buttons for the modals in Telebugs, even though those colors weren’t used anywhere else in the UI. Asked three different AIs what they thought. They all gave the same answer: don’t do that. Stay consistent. I’m changing it now.

In the end, I ripped out JavaScript (oh yeah 😌) and moved the relative time out of cache. Here's how it'll look in the new version:

I chose yellow backgrounds and orange buttons for the modals in Telebugs, even though those colors weren’t used anywhere else in the UI. Asked three different AIs what they thought. They all gave the same answer: don’t do that. Stay consistent. I’m changing it now.

Would you use a hosted version of Telebugs?

In the end, I ripped out JavaScript (oh yeah 😌) and moved the relative time out of cache. Here's how it'll look in the new version:

Would you use a hosted version of Telebugs?

Got a support email that stopped me for a second. Someone was confused why an error still showed “1 minute ago” days after it happened. Turned out the relative timestamp had been cached the very first time the report was opened. After that, it never updated again.

As I was editing this testimonial, my 4-year-old daughter walked in and saw it: > Papa, who's that? > That's my customer > That's your customer? He's really happy He is 😜

I have a simple benchmark for “are we AGI yet?” If your LLM says “You’re right!” too easily, we’re not there yet.

As I was editing this testimonial, my 4-year-old daughter walked in and saw it: > Papa, who's that? > That's my customer > That's your customer? He's really happy He is 😜

I have a simple benchmark for “are we AGI yet?” If your LLM says “You’re right!” too easily, we’re not there yet.

It’s a huge honor to be noticed by the legend himself, John Resig. Thank you 🙇‍♂️

🛠️ Starting work on the Telebugs API This has been one of the most requested features. I'm prioritizing it now so you can programmatically manage projects, query errors, and build automations around Telebugs.

Sometimes an “improvement” creates problems you don’t see until real data hits it. A customer reported that after updating to 1.15.1, some of their events started failing with 500 errors. The culprit turned out to be non-ASCII characters (things like box-drawing characters and emojis).

Every time Google shows you a CAPTCHA, it also apologizes for it.

It’s a huge honor to be noticed by the legend himself, John Resig. Thank you 🙇‍♂️

🛠️ Starting work on the Telebugs API This has been one of the most requested features. I'm prioritizing it now so you can programmatically manage projects, query errors, and build automations around Telebugs.

Sometimes an “improvement” creates problems you don’t see until real data hits it. A customer reported that after updating to 1.15.1, some of their events started failing with 500 errors. The culprit turned out to be non-ASCII characters (things like box-drawing characters and emojis).

Every time Google shows you a CAPTCHA, it also apologizes for it.

I made an interactive demo showing clamp() in action and comparing it to traditional CSS media queries (link below):

Warning: LLMs may contain buLLMshit.

I made an interactive demo showing clamp() in action and comparing it to traditional CSS media queries (link below):

Last week, a customer nearly left Telebugs because of a mistake I made at the design level. Their queue database grew to 95GB in a single day. Their app was processing ~40,000 jobs daily, and I had designed the main ingestion job to carry large payloads directly in the job arguments.

Warning: LLMs may contain buLLMshit.

One year ago today I dropped justfuckingusehtml.com and told the entire industry to stop overcomplicating everything. Still true. Still loading in 12 milliseconds while your framework app is busy hydrating its feelings. Still the best piece of web advice anyone’s written in years.

Last week, a customer nearly left Telebugs because of a mistake I made at the design level. Their queue database grew to 95GB in a single day. Their app was processing ~40,000 jobs daily, and I had designed the main ingestion job to carry large payloads directly in the job arguments.

This is probably the first time I’ve seen a 500 error on Google 😲

One year ago today I dropped justfuckingusehtml.com and told the entire industry to stop overcomplicating everything. Still true. Still loading in 12 milliseconds while your framework app is busy hydrating its feelings. Still the best piece of web advice anyone’s written in years.

This is probably the first time I’ve seen a 500 error on Google 😲

We’ve become obsessed with immediacy. But the universe has always worked on delay. Look up at the night sky. The light from those stars left years - sometimes centuries - ago. What you’re seeing right now is already the past. And maybe that’s one of the most elegant systems we know.

There is a quiet magic in the terminal. The screen is black. The cursor blinks - steady and patient. You lean in and begin to type, your fingers moving with intention across the keys. A few simple words appear: ls, cd, mkdir, grep. kyrylo.org/2026/04/15/t...

We’ve become obsessed with immediacy. But the universe has always worked on delay. Look up at the night sky. The light from those stars left years - sometimes centuries - ago. What you’re seeing right now is already the past. And maybe that’s one of the most elegant systems we know.

There is a quiet magic in the terminal. The screen is black. The cursor blinks - steady and patient. You lean in and begin to type, your fingers moving with intention across the keys. A few simple words appear: ls, cd, mkdir, grep. kyrylo.org/2026/04/15/t...

One line of CSS. Perfectly responsive typography on every screen. font-size: clamp(1rem, 1vw, 1.75rem); 🪄 1rem minimum keeps text readable on phones 🪄 1vw makes it scale fluidly with the viewport 🪄 1.75rem caps it elegantly on large displays No media queries or breakpoints. Try it!

One line of CSS. Perfectly responsive typography on every screen. font-size: clamp(1rem, 1vw, 1.75rem); 🪄 1rem minimum keeps text readable on phones 🪄 1vw makes it scale fluidly with the viewport 🪄 1.75rem caps it elegantly on large displays No media queries or breakpoints. Try it!

CSS is ridiculously powerful when you stop thinking of it as “just styling”. I added a subtle polka-dot background pattern to the dashboard using just a few lines of CSS. It doesn't use images, or extra elements. Yet it completely changes how the interface feels. Modern CSS is awesome!

Most pricing pages use subtle dark patterns (confusing tiers, hidden limits, “contact sales” for basic stuff). I deliberately avoided all of them. I wanted people to understand exactly what they’re getting and how much it costs, with zero tricks. Here’s what I built instead: