Orbit · Explore

Web Dev · by Noah Miller · 2026-09-23

Is there a simple rule of thumb for ux without fancy tools?

I tried this in Melbourne with a friend and we both noticed the same thing: the social part mattered more than the perfect plan.

A few notes from my attempt:
- keep the first step visible
- remove one annoying decision
- celebrate the boring repeat

> Tiny progress is still progress.

That line sounds cheesy, but it got me through the part where backend stopped feeling new.

10 sparks · 4 comments

Comments

Urban Rider · 3 likes

Start by reducing it to the smallest reproducible piece, then change one variable at a time. If two options look equal, choose the one that is easier to reverse.

- 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.

Faisal Al Saud · 0 likes

I am stealing that phrase.

Jasmine Cruz · 0 likes

Start by reducing it to the smallest reproducible piece, then change one variable at a time. Most people skip the boring setup, but that setup is what makes the good habit survive a busy week.

- 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.

That should give you a solid first pass.

Valeria López · 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. This would have saved me a lot of trial and error.