What is your coding strategy?

Question

Do you plan your programs carefully using written pseudo-code or do you use trial and error?
Recent statistics show that young programmers often use trial and error while older programmers try to solve problems by planning ahead.
Which are you?

Answer 1

Depending on the size of your projects, the plan evolves from a simple command to a mindplan of commands, which develops into tasks' list, which in its turn mutates into functions list, which turns into behaviour list and so on.
Judging from own mistakes I can say that correct evaluation of the project scopes and hence the plan size save much time.

Answer 2

Although I'm old, I'm insane. I directly start coding, get stuck again and again, disturb Google uncle a lot and then finally get mad 😡

Answer 3

Idea!>How will I do that?>Code...

Answer 4

I might actually plan ahead if I get charged for every compilation error I recieve. =^=
Most of the plannings happen in my head, so even if it seems like I go head front with a problem, I know what I'm doing.

Answer 5

i always do with a plan
that is trial and error.

Answer 6

I usually write pseudocode in the ide as comments and then fill in the proper code. This way it feels like I'm getting straight into it but I'm really planning ahead. I always keep my pseudocode comments as well so I can refer back at a later date and remember my thought processes.

Answer 7

My approach is usually based on a top-down analysis and early prototyping.

Answer 8

I try writing pseudocodes, but end up in a trial and error situation...😅

Answer 9

I do both, but it does depend on the size. Small projects are good for planning while large project will need more trial and error. Though that's just me, I'm backwards 😂

Answer 10

first i work on a paper and draw a diagram of variables,functions ...and their relations.
then after writing them in codes i simply try and fix. i get the most help from the internet, these q&as and books.

Answer 11

most of my codes here are not planned and i just make it up as i go along, tackling each issue as i hit a wall....
talking about code efficiency issues... xD

Answer 12

as i am new in coding world so i have to think so deeply, properly but i am enjoying the process...

Answer 13

as a student, only trial and error... you can't plan a heads if you're only at the beginning! you set a goal and try concar it what ever you can!

Answer 14

Basic drawn ideas are my way to go about it, and then trial and error.
I sometimes have trouble, though, of polishing/finishing my ideas before I move on to the next one!

Answer 15

I use a mixture of both. though I'm only 13

Answer 16

people always say that you should plan out your program on a sheet of paper. I always start from the code...

Answer 17

Although I'm old, I'm insane. I directly start coding, get stuck again and again, disturb Google uncle a lot and then finally get mad

Answer 18

I can't imagine making a plan. I prefer to stream my imagination into code. That's just my way though. I also find that coding on the spot really helps with solving real world problems. It increases adaptability overall.

Answer 19

I first thinl about what my programm should do. Then I create an UML-Diagramm and after that a flowchart. At last I start programming.

Answer 20

Unfortunately i am from the one who doesn't plan ahead and just build programs and when bug comes out...I spend continous hours in running program in debugging mode untill the problem gets solved.