I'm far from what I would call a senior engineer (or a engineer at all), but the times I've written the most readable and maintainable code were when I write fi

I'm far from what I would call a senior engineer (or a engineer at all), but the times I've written the most readable and maintainable code were when I write first what the program should do in comment form and then completed it with the corresponding code. This way you force yourself to think outside your programming language and also forces you to write the corresponding comments. I think this has a name as a methodology but cant remember it.