What would you do first if you were new to Programming when life is busy?

Miguel Santos · 16 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. For me it came down to the tiny repair.

Ngozi Bello · 5 likes

Respectfully, I see it the other way.

Jasmine Cruz · 15 likes

This is adorable and oddly motivating. I care less about the perfect answer and more about repeatability. A small test case would make this easier to trust.

Ethan Brooks · 1 likes

I think both things can be true.

Chloe Davis · 4 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.

Hope this helps!

Paolo Garcia · 2 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. It reminds me of a very specific conversation near a coworking table.

Liam Eriksson · 2 likes

@ph_baker I had the same reaction to behavior.

Maya Williams · 1 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.

Kabir Khan · 5 likes

My wallet felt that.

Rohan Mehta · 4 likes

I like this more than the top-level advice.

Cedar Coder · 2 likes

Same here. It took me too long to learn.

Rohan Mehta · 2 likes

Noted, and thank you.

Faisal Al Saud · 1 likes

@sleepy_comet4 That made the concept click.

Cedar Atlas · 1 likes

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

Sebastián Rojas · 9 likes

@silver_marauder That is fair, but I still worry about maintenance.

Aoi Ito · 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 would write it down before changing anything else.

João Pereira · 1 likes

I wanted to like this, but the life argument is weak. This pairs weirdly well with tacos.

Isha Menon · 0 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.

That should give you a solid first pass.

Cedar Otter · 0 likes

This is the gentle version of my rant.

Mateo Cruz · 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. I used to overcomplicate this constantly.