As a systems engineer, ive been a reverse centaur more often than not.

I have a Jira queue. It drives what work I do. I may have some leeway in how I do the work, and what tickets I pull, but Im absolutely at the behest of the ticketing behemoth.

Tickets have been my life since I started helpdesk. And future roles will also be ticketed. And they almost all are customer-facing or system-breakage (which impacts lots of customers).

Im not sure what IT roles im capable of doing wouldnt have tickets. So, yeah. Reverse centaur.. But not an AI driven reverse centaur, yet.

▲

bendmorris 9 hours ago | parent [-]

Reverse centaur means a machine is using you to get things done. Presumably at the other end of the ticketing system is other people. So not really the same thing at all.

	▲	mystraline 6 hours ago \| parent [-]
		I look at at reverse centaurs as a spectrum of autonomy at work. We can now observe a complete reverse centaur. But those of us who go ticket after ticket, metrics of tickets, response times, and all of those management metrics also go directly to reverse centaurs as well. Now, its not Marshall Brain's "Story of Manna" level each listed action at a time... But it was definitely getting to that point. Call centers were already absolutely at that point, with completely scripted communications, that that attendant could not deviate from or be fired. > Presumably at the other end of the ticketing system is other people. Sometimes. As a systems engineer, tickets can also be generated by other systems as an "immune response" to detected but unfixable errors.