|
Concurrency: avoid it if you can. If not, then remember that with great power comes great responsibility. These are pretty good lessons to learn. What would you add to this list?
|
|
|
|
|
Great one, thanks for sharing. Would like to share my perspective also:
1. Never directly eye technological advances while working. Always have your senses focused on the logic at hand first and then if the current technology does not fit in only then analyze the alternatives. Nobody gets paid for learning new technologies continuously.
2. Sometimes as a programmer you will be in a fix over a feature that you think can be there in the program but considering today's scenario the specifications clearly list that this feature can never be part of the work. In this case it is obvious that you don't have to write in code for this feature but your objective should be to write code in a way that in future this feature really does not become IMPOSSIBLE to code. I can bet on this one I've experienced this situation multiple times.
Hope my experiences that lead me to believe in these facts were not extraordinary
|
|
|
|