BETWEEN SYSTEMS & STORIES / CHAPTER 02

When technology became responsibility

Ganesh Uprety, owner-supplied editorial portrait

There is a difference between solving a problem in a classroom and being responsible for a system that people use every day.

My work as an Information Technology Officer at Sunkoshi Rural Municipality introduced me to that difference.

Technology was no longer simply a subject I studied.

It was infrastructure that needed to work.

Networks required maintenance. Devices needed support. Information needed protection. Employees needed practical solutions, not complicated explanations.

A technical problem could become an operational problem.

A security weakness could become a risk to information.

An unavailable system could interrupt work.

The experience changed the way I approached technology.

I began to see reliability, security, documentation and recovery as connected responsibilities.

It also taught me to think beyond the machine.

A system could be technically sophisticated and still fail the people using it if it was difficult to operate, poorly maintained or inadequately protected.

My role was not simply to understand technology.

It was to help make it dependable.

The moment people depend on your work, technology becomes a responsibility.