What mistake taught you the most about ux on a budget?

Urban Sparrow · 11 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. The ambitious constraint is probably the real story

Solar Lantern · 10 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. My only addition is to make the first step visible

Camila Rocha · 5 likes

interesting. I would like to see how it changes after 9 months. I keep a note about javascript for exactly this reason. This is exactly the kind of tradeoff teams argue about for weeks

Midnight Runner · 0 likes

Small caveat: context changes the answer a lot

Ren Suzuki · 0 likes

helpful correction

Yui Tanaka · 5 likes

That is a good boundary

Liam Eriksson · 11 likes

fair pushback

Mariam Said · 0 likes

Totally agree, especially for beginners

Mia Anderson · 4 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. I care less about the perfect answer and more about repeatability

Giulia Rossi · 3 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. I noticed the same thing in São Paulo

Hugo Sánchez · 3 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. My only addition is to make the first step visible

Maya Williams · 3 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. I would test it for 8 days before deciding

Noah Miller · 2 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. My friend tried it in Seoul and had the opposite result

Pablo Martín · 1 likes

I am mostly here for the follow-up. That is where the boring checklist helps

Silver Coder · 1 likes

Love the tiny experiment energy. This would have saved me a lot of trial and error. Naming things remains undefeated as the hardest problem

Quiet Fern · 1 likes

The Tuesday test is undefeated

Valeria Flores · 8 likes

Small caveat: context changes the answer a lot

Avery Johnson · 11 likes

This. Exactly this

Minh Nguyen · 1 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. I am curious whether javascript still feels good next month

Noah Miller · 0 likes

I appreciate teh honest middle stage, not just teh polished ending. A little friction removed goes a long way

Leila Karimi · 0 likes

I love this. It feels practical without pretending life is neat. I noticed the same thing in Berlin