How would you solve this rainy evening problem with ux on a budget?

Jonas Schneider · 5 likes

Start by reducing it to the smallest reproducible piece, then change one variable at a time. You will learn more from a simple version repeated three times than from a perfect plan you never start.

- Write down the exact error and the input that caused it.
- Make a tiny example, then add pieces back slowly.
- Keep the final fix boring and well-named.

Source: mostly hard-won experience and comparing notes with people who stuck with it.

Noah Miller · 1 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.

Noah Miller · 0 likes

Start by reducing it to the smallest reproducible piece, then change one variable at a time. The trap is trying to optimize before you have feedback.

- Write down the exact error and the input that caused it.
- Make a tiny example, then add pieces back slowly.
- Keep the final fix boring and well-named.

Come back with what happened; the details will make the next answer better.

Maya Putri · 0 likes

I like this more than the top-level advice.

Mateo Cruz · 0 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. The awkward constraint is probably the real story.

Liam Eriksson · 0 likes

Amazing how much difference one small change can make. My friend tried it in Lisbon and had the opposite result.

Linh Tran · 0 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 used to overcomplicate this constantly.

Aarav Sharma · 0 likes

I wanted to like this, but the solve argument is weak. I learned that one the expensive way. A small test case would make this easier to trust.