AI, My Job, and the Existential Crisis Nobody Asked For

I have had the great fortune, or possibly the great misfortune, of being personally present for every single "this changes everything" wave in tech this century — Dot-com (I was too young to invest and too old to admit that's a good thing), Mobile and Social Media (still not entirely sure what half those job titles from that era actually meant, but I nodded along in plenty of meetings about it), Big Data (turns out it was just "data," but bigger, and somehow needed its own conference circuit), Cloud (yes, I was there when we still called it "someone else's computer" and acted shocked), Blockchain (I nodded, I did not invest, history will remember me as either a coward or a genius), Machine Learning (I nodded very seriously in a lot of meetings I understood 10% of), and now AI, where I have graduated to nodding seriously while also occasionally being replaced mid-nod. At this rate my professional bio is going to need its own microservices architecture.

Disclaimer: I am not an AI expert. I am a self-proclaimed AI Rookie and Prompt Architect (a title I gave myself, no one else was hiring for it) — the kind of Prompt Architect who gets the AI to write his prompts for him, which if you think about it for more than two seconds is either genius or the beginning of the end. AI Agents reading this need not get offended, you know I love you.

So there's this thing everyone's talking about — Artificial Intelligence. You've heard of it, no? (If you haven't, please tell me which decade you're blogging from, I'd like to join you there..)

Has AI changed how we work? The answer is a feeble "it's helping" and an emphatic "IT'S TAKING OVER" depending on which day you ask me. Monday mornings, it's a helpful assistant drafting my status reports. Friday evenings, when it finishes a task in nine seconds that used to earn me a full day's "In Progress" status on the project tracker, it feels less like a colleague and more like that one team member who makes everyone else's estimates look criminally inflated. You can actually see the nervousness spread across a tech team in real time these days — someone demos a new AI tool in a sprint review, and there's a very specific silence that follows, the kind where everyone's smiling and nodding and mentally updating their resume at the same time.

And here's the plot twist — this very post you're reading? Written with AI's help. Yes. MetalHead, the self-declared last bastion of human rambling on the internet, outsourced part of his rambling to a machine. The irony is not lost on me (it is, in fact, sitting directly on top of me, like namma Bengaluru traffic on a Wednesday).

And can we talk about the "Professional" Networking Site for a second? Every second post these days is some "thought leader" (self-appointed, naturally) announcing that AI is coming for your job, my job, and possibly the job of the guy who delivers your lunch. Always with a dramatic robot photo, because apparently our jobs can only be threatened in stock-image form. Is the sky actually falling? The answer is a dramatic "maybe" wrapped in eleven hashtags and a "thoughts?" at the end, honking for engagement the way vehicles honk at a red traffic light in namma Bengaluru — loudly, constantly, and with zero expectation that the signal's actually going to change any faster for it. Half these posts are written by the same AI they're warning us about, which nobody seems to find funny except me.

Let's talk work for a second, because that's where this really gets interesting. Every project now has some Technology Leader (and I use that title the way an amoeba might use the word "empire" — technically accurate, wildly overstated) quietly wondering if the next sprint's velocity chart is going to have a suspicious new contributor called "AutoMate" who never asks for leave, never complains about the coffee machine being empty, and never once says "that's not in my scope." As someone occupying that exact rung — somewhere below a single bacterium, technically alive but only just — I'll be honest: half of me is thrilled at the productivity, and the other half is drafting a contingency plan in case the stakeholders decide the AI can also attend my meetings for me (please, take them, I beg you).

And it's not just work-work. It's life-life too. Recipes generated in ten seconds. Travel itineraries planned before you've finished your filter coffee. Even this blog post's punctuation is probably more consistent than my usual chaos (my ellipses have union representation now, apparently).

But here's the earnest bit, and I mean it — the tool isn't the story. It never has been. Compilers didn't replace programmers, they replaced tedium. Search engines didn't replace curiosity, they replaced trips to the library nobody was making anyway. AI won't replace the guy who knows why the client actually wants the feature, or the one who catches the edge case nobody thought to ask about. It'll replace the parts of the job that were never really "the job" to begin with.

So am I worried? A little. Am I typing this with one eye on the horizon and one on my own job description? Also a little. But mostly, I'm just glad to be around to watch this happen — front row seat to the biggest software story since the internet itself.

Till then, keep shipping, keep questioning, and maybe double-check what the AI wrote before you hit publish (I did.. mostly).

Jai Hind!!!

The Great Indian Hybrid Work Experiment

 MetalHead is back.

Yes, it's been a while. Older, wiser (debatable), and noticeably greyer — turns out corporate life does that to a man faster than a toddler ever could. But some things never change, and namma Bengaluru's hybrid working "experiment" is exactly the kind of madness that pulls a retired blogger out of hibernation..

Disclaimer: MetalHead is not an HR consultant or an organizational psychologist, and definitely not the guy who invented "flexible working policy" decks with the smiling stock photo people on slide 3. Just one average software guy's take from the trenches.. take it with a truckload of salt..

Hybrid working. The best of both worlds. Work from home when you want, come to office when you "need to collaborate"..

Has it actually worked? A feeble yes.. and an emphatic no most Mondays and Wednesdays (because apparently Executive Leadership across this entire city collectively decided those are the "collaboration days" — coincidence? I think not).

Let's break this down like a proper sprint retro, shall we..

The Traffic Rant (You Knew This Was Coming)

Namma Bengaluru traffic deserves its own performance review, and if I were the Reporting Manager, the rating would be a straight PIP.

You have a stand-up you cannot miss. You leave home for what Google Maps promises is a perfectly reasonable commute (bless its optimism). You arrive sweating through your "smart casual," having renegotiated your entire relationship with patience somewhere between Silk Board and Whitefield — different area, different pincode, and yet somehow the exact same crawl, the exact same quiet existential crisis at every signal..

And the deadline doesn't care that you were stuck behind a bus doing a 3-point U-turn on a 2-lane road (HOW. HOW does that driver have that much faith in physics).

Driving vs Auto: A Trade-off Analysis Nobody Asked For

Two options, like any good architecture decision record — evaluate the trade-offs, pick your poison, live with the consequences.

Option A: Drive yourself. Pros — you control your own destiny (however minute that control actually is, boxed in by three buses and a guy on a bike carrying a wardrobe). Cons — you arrive already having aged three years, and you still have to find parking, an eight-part epic I won't get into today..

Option B: Take an auto. These days the negotiation doesn't even happen with the driver anymore — it happens with the app. You book, nobody accepts, you add a ₹20 tip, still nobody accepts, and now you're bidding against yourself in a reverse auction where the prize is "please, someone, take me to work." By the time someone accepts, you've paid a tip bigger than the fare.

And the moment he does accept, you've willingly handed over your life, your ETA, and your blood pressure to a man you've known for four seconds, now the sole Release Manager of your morning. He will take the "shortcut" (there is always a shortcut, and it is never shorter). He will take a call mid-ride and somehow drive one-handed AND better than before. You just sit there. A passenger, in every sense, having already paid a premium for the privilege..

(Don't get me started on surge pricing during rain. Namma Bengaluru rain plus auto apps is dynamic pricing wearing a raincoat.)

The Great Setup Swap

Here's the part nobody put in the policy deck — the actual physical switch. Twice a week, sometimes thrice if Executive Leadership decides "we need face time," you become a completely different professional entity.

At home: multiple monitors, proper chair, the whole ergonomic dream a recruitment poster would envy. Except half of it doesn't work, because the driver for your external monitor got blocked by IT for "compliance reasons" nobody can explain, filed under a ticket "in progress" since the last performance cycle. So you sit there, surrounded by three glowing, useless black screens, doing actual work on the 13-inch laptop like it's 2009 again..

And the dress code has quietly evolved into what I call Formal Shorts — collared shirt up top, camera-ready.. shorts and chappals below, completely off-screen and completely non-negotiable at this point. (If Teams ever adds a "stand up and turn around" feature, half of Bangalore's IT workforce is finished.)

Then it's an office day, and your "desk" is a hot-desk shared with the entire floor's rotating population — no monitors, no docking station that actually docks, sometimes not even a chair not already claimed by someone's jacket. You left a full command center at home to hunch over a 13-inch screen at office too. Functionally, nothing changed except the commute you suffered to get there..

Has anyone actually asked why we're doing this? The answer, like most things in corporate life, is a shrug wrapped in a policy document..

Coming Home to... More of the Same

And the punchline nobody saw coming — you finally make it home, back to your (partially working) command center, thinking surely the day winds down from here..

It doesn't. There's more meetings waiting. Always more. The stand-up becomes the sync-up becomes the "quick call" that runs way longer than it should, becomes the "let's take this offline" that somehow spawns two more. Somewhere along the way your headset fuses to your skull, and here's the real horror this glossy policy deck never mentions — you genuinely cannot tell which voice is coming from the headset, which one's in the next room, and which one is just your own tired brain running its own status update on loop. You nod at a silence that may or may not have been a question directed at you..

Has hybrid working given us the best of both worlds? Or the worst commute of one stapled to the worst meeting culture of the other, with a free desk lottery thrown in for sport?

I don't have the answer, honestly. But I know this — namma Bengaluru will keep doing what namma Bengaluru does, Executive Leadership will keep scheduling those "collaboration days," and guys like me will keep showing up, formal shirt on top, shorts underneath, one ear in the meeting and one ear waiting for that calendar to finally, mercifully, go empty..

Till then — here's hoping your next auto driver takes the actual shortcut, your monitor driver gets unblocked before the next performance cycle, and somewhere in all this chaos, you still remember which voice was actually yours.

Jai Hind, and good luck out there..