The way you program now is different from the way you programmed when you started. What happened? You now know more than you did then. Your growing experience constantly affects the circuitry of your brain making you more creative. Becoming aware of this process helps you optimize it even further.
Forget the code for a moment.
Daily coding offers the opportunity to meditate on the creative process involved in building websites and applications. Programming is often associated with the raw power and magnificence of algorithms — computing patterns that efficiently solve a given problem.
So is this really all about brutality of cold science? Is programming merely about knowing more than your peers?
The Way You Program Now
Whether you’re aware of it or not Computer Science principles fuel most of your coding patterns.
Even if you are relatively new to coding using a for-loop — one of the primal things you would come across — is really just following a similar pattern that in Computer Science is referred to as an Iterator. Or at least it can be said that a for-loop follows a similar principle as iterators.
But much is ignored if we limit our understanding of programming computers only to Computer Science. Sticking to the rules isn’t a bad thing. It keeps you organized, helps you write clean code that can be reused and makes it easier to maintain in the future. That’s great!
Coding for a long time your experience grows. And each time you get better at programming you learn to develop awareness of the creative process itself.
We can only optimize what we are aware of.
Increased Awareness of the Creative Process
Every decision you make down to the tiniest ones — and especially those — when writing your program will affect its overall integrity.
The computer language is only a tool that helps you solve problems. And while many common problems already have known solutions, defining structure — architecture — of your software is probably the key to writing good code.
And yet, still… the spirit of programming lies in the moment you put your fingers on your keyboard and stream your creative ability into construction of variables, functions and objects. The excitement and the worries of doing things right. It’s probably the very reason why you became a programmer.
This process will produce the most programming joy when you know that what you have created is done right. Structuring your code in such way that it’s easily read not only by computers but by a human is incredibly rewarding. Not only psychologically, but also in practice when you start to see that the development time on your project is being cut in half.
Thinking for 5 minutes determining what a variable name should be called is common sport among programmers. Are you 100% sure that a better name for this variable does not exist? Seeing exactly how your code will be reused in multiple cases. Thinking multi-dimensionally to see the big picture. All these things deplete the mental fuel of a programmer. How will you expend yours?
The Code I Just Wrote Influenced the Code I Wrote Next
Everything you write now will affect the future of your program. Every function and object composition pattern you craft.
Knowing what the right thing is — in terms of architecture — is hard.
Each line of code is a brick in the wall. The wall that will either be built for a wacky reason. Or for reasons that — when taken together — will contribute to overall integrity of your bug-proof software.
Next time you write code — think about this.