Report Offensive Message
Another way of looking at the 10 points
1) Along with patience it is sometimes necessary to be a bit firm. Instead of simply solving user problems every time they come, why not help users to solve their own problems where appropriate?
2) Continued learning is a given these days in just about every field: I don't see that it applies particularly to IT.
3) + 10) Even on operational support you need to have some roster system. The same person can't expected to be on 24/7 call all the time.
4) I'm not sure that IT is that particularly a people-facing job. Perhaps for the business analysts, and yes, sure, you need good communication skills. But overall? I'm not that sure the head-down concentration and focus needed to write low-level software are found in the extrovert and people-focused person, who might be ideal for sales and marketing.
5) Sometimes you just don't have the time to re-create every production problem on a test system. That is the reality outside academia. Sometimes a particularly obscure permutation of data, applications running, software versions, machine load etc might not be possible to simulate. And if the error is not occurring on a regular basis, then it might be better to cut your losses, document what you've found out, code in some more logging and instrumentation to help you if the problem does arise again - and then get on with more high priority work.
6) Frustration can also be a good thing. It allows you to sit back and think what you are doing wrong. Why are you banging your head against a particular brick wall. What could you do better?
7) Multitasking is fine, but jumping aimlessly from one task to another is no substitute for good organisation and planning.
8) There are career paths in IT both for techie people and for those looking to get into management. In some organisations the CIO and CTO are among the highest-level people there.
9) Hating technology? Well I hate Microsoft with a vengeance and have still managed to stay in IT for all these years
2) Continued learning is a given these days in just about every field: I don't see that it applies particularly to IT.
3) + 10) Even on operational support you need to have some roster system. The same person can't expected to be on 24/7 call all the time.
4) I'm not sure that IT is that particularly a people-facing job. Perhaps for the business analysts, and yes, sure, you need good communication skills. But overall? I'm not that sure the head-down concentration and focus needed to write low-level software are found in the extrovert and people-focused person, who might be ideal for sales and marketing.
5) Sometimes you just don't have the time to re-create every production problem on a test system. That is the reality outside academia. Sometimes a particularly obscure permutation of data, applications running, software versions, machine load etc might not be possible to simulate. And if the error is not occurring on a regular basis, then it might be better to cut your losses, document what you've found out, code in some more logging and instrumentation to help you if the problem does arise again - and then get on with more high priority work.
6) Frustration can also be a good thing. It allows you to sit back and think what you are doing wrong. Why are you banging your head against a particular brick wall. What could you do better?
7) Multitasking is fine, but jumping aimlessly from one task to another is no substitute for good organisation and planning.
8) There are career paths in IT both for techie people and for those looking to get into management. In some organisations the CIO and CTO are among the highest-level people there.
9) Hating technology? Well I hate Microsoft with a vengeance and have still managed to stay in IT for all these years
Posted by WMDH
27th Dec
