Orbit · Explore

Web Dev · by Piotr Zieliński · 2026-08-29

Why does performance feel easy for everyone except me in real life?

Would love to hear how other people handle this. I am especially curious about the version that works on a tired weekday, not just on an ideal Sunday

64 sparks · 15 comments

Comments

Kabir Khan · 8 likes

Try making a tiny reproduction with no framework code. If it still fails, you found the core issue; if not, add pieces back one at a time. Honestly, the simplest version wins for me

Ethan Brooks · 3 likes

I was going to disagree, but your second sentence got me

Brave Comet · 7 likes

I would log the input, the expected output and the actual output first. Once those three are visible, the bug usually stops feeling mysterious. I keep a note about css for exactly this reason

Jasmine Cruz · 2 likes

adding this to my notes

Oliver Smith · 0 likes

that is fair, but I still worry about maintenance

Jasmine Cruz · 0 likes

This. Exactly this

Bianca Santos · 0 likes

Totally agree, especially for beginners

Curious River · 5 likes

I would log teh input, teh expected output and teh actual output first. Once those three are visible, teh bug usually stops feeling mysterious. This would have saved me a lot of trial and error

Tomás Gómez · 6 likes

Beautifully concise

Nima Ahmadi · 5 likes

I would log the input, the expected output and the actual output first. Once those three are visible, the bug usually stops feeling mysterious. This pairs weirdly well with shakshuka

Tiny Runner · 4 likes

I disagree a bit. performance matters, but the bigger issue is usually expectations. I would test it for 6 days before deciding. This is exactly the kind of tradeoff teams argue about for weeks

Jack Taylor · 12 likes

Small caveat: context changes the answer a lot

Tola Ibrahim · 3 likes

The context helps. Without it I would of assumed the opposite. This is exactly the kind of tradeoff teams argue about for weeks

Priya Nair · 1 likes

I would log the input, the expected output and the actual output first. Once those three are visible, the bug usually stops feeling mysterious. The 2-minute rule is underrated

Curious Panda · 0 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. I am curious whether performance still feels good next month