Finding the flow in coding
Development has often been described as a ride with a roller coaster. The happiness in being on the top where the the coach is about to ride downwards in infinite speed, is of course the feeling you get when the code is running as expected. The other part is when the train is in the bottom and on its way up and you just don't know how long the upper part is. The feeling is that it probably will last for ever! However when you see the solution and get the happiness of having solved your thing. Down you go again!
Development has often been described as a ride with a roller coaster. Happiness, fear, hard feelings, happiness etc.The happiness in being on the top where the the coach is about to ride downwards in infinite speed, is of course the feeling you get when the code is running as expected. The other part is when the train is in the bottom and on its way up and you just don't know how long the upper part is. The feeling is that it probably will last for ever! However when you see the solution and get the happiness of having solved your thing. Down you go again!
On the down-going ride:
Work with team mates is clearly on the happiness easy going down side. Every time you achieve a goal you can share that with your team and that is a euphoric feeling.
The flow in having a great idea and getting the code to work - especially if it did not work in the first place. That can make you shout out in the same way as when you are passing the highest point and you are on your way down.
Fact: Git
Pushing, adding, pull requesting are things that are ongoing during the roller coaster ride and can be visible milestones that make your roller coaster ride more fun. It is more like if it is part of the safety rules for the roller coaster itself.
Finding an answer from somebody else and thereby be able to solve a problem or bug is a very nice part of the ride.
On the up-going ride:
Down in the dark part of the ride it can be a great deal of frustration. It is for example when your don't know how to fix something and you can't somebody else with the same issue. And when you're new to the industry or area it can even be hard to know how to ask the question.
There can also be moments in the ride where you don' t believe in your self for no reason. Or that new solutions are destroying things that worked at the first place.
When everything looks ugly and you have done it yourself you are definitely on the bottom of the roller coaster ride.
Coding vs a roller coaster ride in reality
My reflection on this is that I rather take the roller coaster feeling from coding on a daily basis and a reality roller coaster ride every second year or so. The advantage for me is obvious: You don't need to get the height fear kicked in as a developer.