Skip to main content
4 answers
5
Updated 907 views

Computer Analysts, How much of your time is spent responding to incidents, versus Preventing them?

I am a sophomore researching different IT careers.


5

4 answers


0
Updated
Share a link to this answer
Share a link to this answer

Teklemuz Ayenew’s Answer

Computer analysts play a vital role in keeping systems running smoothly. They split their time between fixing issues and preventing them, depending on the tools and needs of their organization. They solve system errors, help users, and improve system performance. They also work on maintaining databases, planning IT infrastructure, and designing workflows. Some analysts focus on software updates, network setup, or data analysis to boost efficiency. Thanks to automation and AI, many routine tasks are handled automatically, allowing analysts to tackle bigger challenges and make strategic improvements. To succeed, analysts need technical know-how and soft skills like communication, teamwork, problem-solving, and adaptability. These skills help them keep systems reliable and efficient.
0
0
Updated
Share a link to this answer
Share a link to this answer

Rahul’s Answer

From a developer's point of view, the split really depends on how healthy the codebase is. Most weeks I spend more time preventing issues- fixing bugs at the root, improving logs, tightening error handling and making small improvements that stop incidents before they happen. But when something urgent hits production, that instantly becomes the priority. over time, the more effort you put into prevention, the fewer late-night incident fixes you end up dealing with.
0
0
Updated
Share a link to this answer
Share a link to this answer

Cynthia’s Answer

Hi Logan,
Great question! Your role might change based on the company's size. In bigger companies, teams usually have specific tasks, like one team handling incidents and another focusing on prevention. Smaller companies might let you do a bit of everything. Adding AI learning to your studies is a great idea since this technology is really transforming things.
0
0
Updated
Share a link to this answer
Share a link to this answer

Ann’s Answer

Historically, we had separate teams for the technical debt verses new functionality. This is shifting where there is a single team that provides full focus on the application/product. As a general rule, there is roughly 20% spent on technical debt verses 80% on new functionality.

Note that this is separate from the HelpDesk/Triage team that is analyzing/routing and bringing the right resources together to address the break fixes.
0