To write code: start by writing text

Software writing, coding, development, hacking. There’s sure a ot of aliases for basically a thing that boils down to a recipe of
‘curiosity-satisfaction

Once upon a time, I learned a language called BASIC: It was rather easy.

PRINT “Hi!”

was command enough to print the text Hi! on screen.

IF PRICE > 9 THEN PRINT “High price! It is over 9”

would do the pretty obvious thing: if a variable called PRICE contains number greater than 9 (10, and onwards) — then the program warns that the price is high.

The code development recipe is here:

Know what to build next.

Write. Test. Just simple like that.

Write in English (or what ever is your own language) at first. This is sketching the functions, get their names — because it brings structure to your head.

Writing is a big deal of doing code.

Perhaps one of the most important questions of them all, is to really know what you will be doing next. And, a bit of designing it: how are you going to do your feature?

Design the feature in text

• write a plain Use case for this feature: think as a user; Ok, you are doing a virtual assistant? Yes. Then: “I want to write a question, and click Search” as a user. That is a use case.
• what inputs (data) does the app need? Counts also clicks, navigation as input
• example: ”user can click on button, and write text into a guestion box”

Make simple DoD criteria: what is it, you want in this version?

DoD means “Definition of done”. Write just the essentials. Break down your design into quite simple pieces. Think, as you would be a computer, just taking your command, executing on it.

When you think a bit like computer, design actually becomes really easy. You make your own work as developer streamlined.