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

Nicolás Díaz · 27 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

Grace Parker · 26 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 care less about the perfect answer and more about repeatability

Amelia Hughes · 3 likes

That is a much better way to say it

Kabir Khan · 24 likes

You explained the tradeoff really clearly. The busy month version is even more interesting

Aoi Ito · 2 likes

I am stealing that phrase

Kabir Khan · 11 likes

Thanks for making it less intimidating

Priya Nair · 1 likes

The Tuesday test is undefeated

Hamza Malik · 5 likes

I would love a follow-up example

Mateo Cruz · 1 likes

Can you expand on that a bit?

Isha Menon · 0 likes

Totally agree, especially for beginners

Sara Ahmed · 9 likes

helpful and not preachy, which is rare. The the train station detail changes the whole answer

Rohan Mehta · 3 likes

short answer: yes. Long answer: also yes

Arif Hasan · 6 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

Maya Williams · 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. The rainy evening version is even more interesting

João Pereira · 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. The a neighborhood park detail changes the whole answer

Grace Parker · 3 likes

this feels like advice from a patient friend. I would write it down before changing anything else

Urban Noodle · 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. A little friction removed goes a long way

Haruto Sato · 2 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.

Hope this helps!

Nicolás Díaz · 2 likes

that would annoy me more then it helped. I keep a note about backend for exactly this reason

Aarav Sharma · 1 likes

Thanks for making it less intimidating

Piotr Zieliński · 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 Cairo example makes it feel concrete