Quote:
Originally Posted by oldbird
Just to share my personal view. Correct me if I am wrong.
IT development
(1) Working hours can vary. Overtime and crunches needed for last minute user requirements/changes or use of unfamiliar technology. However, on normal days, people in development role can better plan and schedule their activities unless fire-fighting.
(2) Decisions/requests may not be time-critical or need to be made on the spot immediately. Development teams are given time (a day to a week) to research on a requirement and possible options before returning to user to propose the recommended implementation details.
(3) Usually no need to work shift. Irregular hours only happen during deployment or on-site testing of new systems.
IT operations
(1) Working hours can be erratic due to system maintenance, patching during off-office hours (weekends and early mornings 12am - 4am).
(2) Due to some 24x7 round the clock operations, personnel need to work in shifts.
(3) Common for ad-hoc requests for information, status updates or restoration of failed critical services. However for stable systems, very little required and life is peaceful. High stress for swift system troubleshooting and recovery.
|
You are making sweeping generalizations hoping to seek confirmation that IT development is good for you. It varies with company, industry, actual job / projects and your boss & management.
Bottom line is IT is not the place to just sit around go through repeat motion every day, you will be eaten by the FTs in no time with this sort of attitude. Better do something else.