Orbit · Explore

Programming · by Tomás Gómez · 2026-09-02

What would you do first if you were new to Programming as a beginner?

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

22 sparks · 8 comments

Comments

Benjamín Rojas · 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.

That should give you a solid first pass.

Rapid Panda · 4 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. My friend tried it in Madrid and had the opposite result.

Tanvir Rahman · 2 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.

Ananya Rao · 2 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. I care less about the perfect answer and more about repeatability.

Luca Bianchi · 1 likes

Maybe, but the tradeoff seems bigger than the post suggests.

Maja Wiśniewska · 0 likes

I wish more posts had this much context.

Gentle Runner · 1 likes

I was going to disagree, but your second sentence got me.

Miguel Santos · 0 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.