Carpal Tunnel, Foolish fresh grads.
on
Too Old To Code?
·
· Score: 1
Perhaps they are scared that their wrists will give out if they employ them, and face a lawsuit.
Perhaps an office of unknowing fresh graduates under the iron grip of a bloodsucking corporate manager and other management-types in cahoots might also find out what they're missing if someone who knows the score in the industry shows up at work.
I think this is more of a question of the evolution of development environments. The myriad languages, protocols, hardware, software libraries and modern multi-tier architectures we see today are simply a refactoring of how we get the job done, given the limits of our technology at the time. Typically software written is the solution to a particular problem. How the task is acheived is not important as long as it serves the requirements described by the problem. We are just solving problems... Therefore the strength of a programmer lies in how well an accurate solution can be procured (in terms of time, feature fulfillment, and stability of the program) The tools with which it is done, and the manner in which it is done evolves as does our technology. The languages, libraries/APIs we use today and in the future, how we use them, and how we adapt to them will shape us as programmers. They say we program computers, but it is computers that program us.
Perhaps they are scared that their wrists will give out if they employ them, and face a lawsuit.
Perhaps an office of unknowing fresh graduates under the iron grip of a bloodsucking corporate manager and other management-types in cahoots might also find out what they're missing if someone who knows the score in the industry shows up at work.
Perhaps I read Dilbert too much.
I think this is more of a question of the evolution of development environments. The myriad languages, protocols, hardware, software libraries and modern multi-tier architectures we see today are simply a refactoring of how we get the job done, given the limits of our technology at the time. Typically software written is the solution to a particular problem. How the task is acheived is not important as long as it serves the requirements described by the problem. We are just solving problems... Therefore the strength of a programmer lies in how well an accurate solution can be procured (in terms of time, feature fulfillment, and stability of the program) The tools with which it is done, and the manner in which it is done evolves as does our technology. The languages, libraries/APIs we use today and in the future, how we use them, and how we adapt to them will shape us as programmers. They say we program computers, but it is computers that program us.