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!!!
No comments:
Post a Comment