What are the red flags beginners miss in Programming on a budget?

Maya Williams · 18 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

Luca Bianchi · 13 likes

I would log teh input, teh expected output and teh actual output first. Once those three are visible, teh bug usually stops feeling mysterious. I would write it down before changing anything else

Noah Miller · 11 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 Dublin example makes it feel concrete

Tanvir Rahman · 4 likes

This. Exactly this

Mariam Said · 8 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

Nicolás Díaz · 6 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. It reminds me of a very specific conversation near my desk

Kanya Srisai · 6 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 am curious whether learning still feels good next month

Grace Parker · 4 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. That is where the boring checklist helps

Tomás Gómez · 1 likes

Small caveat: context changes the answer a lot

Zofia Kowalska · 4 likes

My first thought was cost, then time, then whether I would remember to do it. I keep a note about java for exactly this reason

Maksym Bondar · 4 likes

Totally agree, especially for beginners

Youssef Mahmoud · 4 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 am curious whether architecture still feels good next month

Marco Conti · 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.

That should give you a solid first pass

Ren Suzuki · 2 likes

There is a hidden assumption here that not everyone shares. My friend tried it in Berlin and had the opposite result

Chloe Davis · 2 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. It reminds me of a very specific conversation near the kitchen

Quiet Atlas · 2 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 Istanbul example makes it feel concrete

Liam Naidoo · 1 likes

This has cozy competence written all over it. The delightful part is easy to underestimate

Mateo Cruz · 3 likes

This is the kind of disagreement I like

Finn Brown · 0 likes

anecdote beats theory here

Ren Suzuki · 1 likes

Honestly, great taste. That is where the boring checklist helps

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

Élodie Favre · 13 likes

Now I want a spreadsheet

Elif Yılmaz · 3 likes

Appreciate the nuance

Martina Fernández · 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. It sounds small, but the conversation matters

Gentle Baker · 1 likes

love the tiny experiment energy. I am curious whether debugging still feels good next month

Yui Tanaka · 0 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

Paper Panda · 0 likes

This is the kind of disagreement I like