so you're thinking of learning to code?

the first useful thing i ever made with code was small enough to be embarrassing. it saved me from doing the same boring task by hand again.

that was enough. i understood, for the first time, that a computer isn't only a thing you consume things through. you can ask it to do work differently.

you don't need a startup idea to start learning. you don't need to turn every afternoon into a career plan. maybe you want to rename a pile of files, make your desktop less annoying, build a tiny game, or understand why a page breaks when one line of CSS changes. those are real reasons.

start with a problem you can touch#

syntax matters, but it is not the beginning. the beginning is noticing a small piece of work and asking what steps a computer would need to take.

if you want to rename files, what information does the script need? where are the files? what should their new names look like? what happens if two names collide? that is programming: turning a vague annoyance into instructions precise enough to run.

pick one beginner-friendly tool and stay with it long enough to make something work. Python is a good place to begin. so is a little HTML, CSS, and JavaScript if you want to see the result in a browser. The Odin Project and CS50 are useful when you want structure, but don't mistake watching for learning.

let projects make the curriculum#

i'd rather see someone build a clumsy file organiser than finish another playlist of tutorials with nothing to show for it. projects give you the questions that lessons cannot: why did this fail? where does this data go? how do i make it less ugly? why is the program doing exactly what i told it to do instead of what i meant?

that frustration is not a sign you picked the wrong thing. it is the part where the machine starts becoming legible.

start small. make the weird little tool. break it, read the error, change one thing, run it again.

you do not need permission to begin. you just need something you wish your computer could do.