Out of the three things needed to be a good developer, one of them is the understanding that you’re likely going to spend a significant amount of time in frustration.
That’s a fact.
But I’m curious…
What is the most frustrating aspect of writing code for you?
It doesn’t matter if you’re a total beginner or have been doing this for decades.
Go.
Jason Bradley says
Not having enough time to execute all the ideas that you have. Ohh….and syntax errors.
Tom McFarlin says
Yep. Been there.
To some degree, I think I still am but I will say that partnering with other people can help you actually see those ideas come into fruition exponentially faster :).
Kylan Robinson says
1. Compile times. Nothing hurts worse than finishing a three-hour build, only to find that you’ve forgotten to include one measly file.
2. Repetitive tasks. Unless you know (and use!) shortcuts and macros in your development environment, carpal tunnel is almost certainly in your future.
3. Losing sight of the big picture. I don’t know how many times I’ve spent hours chasing down an elusive bug, only to find that it was a simple oversight. Think before you act!
Tom McFarlin says
1. I used to work in a continuous integration shop and our build times were down to roughly two minutes and even that was painstaking for me. I guess I had it lucky :).
2. Shortcuts and macros, for sure. Of course, the challenge there was finding the time to write ’em ;).
3. The more I’ve programmed, the more I’ve found that bugs are usually (though not always) easiest to identify from the big picture rather than debugging 427 lines a four levels into the domain layer.