Which advice about ux did you eventually ignore when life is busy?

Mango Mango · 10 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. That is where the boring checklist helps

Nour Ali · 6 likes

anecdote beats theory here

Aarav Sharma · 5 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. This is where I would ask one more question before choosing

Daan Bakker · 0 likes

I would pin this if I could

Emir Kaya · 4 likes

the safe answer is to keep the API boring: clear names explicit errors and one behavior per function. I used to overcomplicate this constantly

Yasmine El Amrani · 0 likes

Thanks that actually helped

Angel Reyes · 4 likes

the safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. Honestly, the simplest version wins for me

Yui Tanaka · 3 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. The social part surprised me too

Noé Petit · 3 likes

what happened after the first week? I am curious whether life stayed easy. I noticed the same thing in Lagos

João Pereira · 1 likes

Good reminder that boring can be good. The a tiny balcony detail changes the whole answer

Siti Lestari · 0 likes

That is a much better way to say it

Tanvir Rahman · 2 likes

This. Exactly this

Diego Quispe · 1 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. I keep a note about backend for exactly this reason

Inês Ferreira · 6 likes

my wallet felt that

Nicolás Díaz · 1 likes

Can you share what you tried before this? My friend tried it in Kuala Lumpur and had teh opposite result

Pixel Runner · 0 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. A little friction removed goes a long way