vijay🍿☕️🍼

93 Followers
186 Following
297 Posts
Dad . Software . Microsoft . Views my own
personal websitehttps://vijaykrishna.github.io

The Weekly: 996 or AI? Pick.

First things first. Been away for a while. I have probably gone through 3 rounds of burnout this year. Those burnouts triggered an intense re-look at my life and life choices. I will speak to the burnout soon. What I can say is that while I accomplished a lot this year, I am not ending 2025 on a higher note than when I started it. Everything is dog💩.

But I am back. Back to tending the important things in life. Back to this blog and newsletter. And I am here to stay.

I have been meaning to write this come-back note for a while now. I wanted to pen a few thoughts about my burnouts. But they have been crushing difficult to talk about – even to myself. After a month of scribbling privately, I stumbled onto something that felt tangentially connected to my burnouts. So here it goes…

996 or AI? Pick.

Either AI will boost productivity like never before and cause large sections of today’s economy to go without human workers. Or, people will need to work harder then ever to keep up with the ever increasing demands of the workplace.

Which is it? Because you cannot have it both ways.

N. Murthy, founder of Infosys and guy who built a business model around necessary manual labor in computer science, recently came out and reiterated his stance on getting working-age Indians to perform 70+ hour work weeks. Some of his words,

“There is a saying in China – 9, 9, 6. You know what it means? g a.m. to 9 p.m., six days a week. And that is a 72-hour week.”

He’s made similar remarks going back to early 2025, 2024, and 2023. He talks about getting a life before getting work-life balance. I will say again, for a man who has exploited the need for manual labor in tech, i expect nothing less. Soon, we can expect a podcast from him, titled “996”.

But I sense a dishonesty in Murthy’s remarks.

Push for 996 vs. Push for AI

996 reeks of structure. Structure and Committees (because you need committees to enforce said structure). Hard work, especially over longer durations, is not fueled by structure; it is fueled by inspiration and creativity. Innovation certainly does not happen by committee.

If you want people to work longer hours then give them something to live up to, or look up to. Give them a problem that feeds their intellect or interest. Give them a mission. They will beg for more work. But let’s face facts, most (white-color) work is not like that. No matter how much we pretend otherwise. Most work is repetitive and boring, but necessary; which brings me to AI and automation.

Murthy is not alone on this 996 push.

And it is particularly odd to see corporate leaders begging people to work longer, in an age of AI — where most routine work should and would be automated away by now. Aside: all this begging makes them look feckless.

After praying to the 996 gods, these money-ghouls will immediately turn around and claim the powers of AI as “transformative” — Murthy has. They will claim that routine, repetitive work is/will get automated away, leaving behind only creative endeavors for human workers.

It’s a grift

These CEOs and corporate leaders do not want to pay fair wages. They ideally want an infinite source of labor for zero cost. And they want the ability right to replace any worker, at any time, with no repercussions. And i want a pony.

It is all a grift for them. Their grift is that they dangle salaries that look high to Indian workers. The salaries look high because young Indians graduating out of schools and colleges have never seen their parents make such sums of money. Give a worker 30,000 INR a month. Heck, give them 50,000 month. Push it to as high as 1,00,000 INR every month. Seems like a lot, because numerically they are higher compared to the salaries of a previous generation. Then slowly you realize that you get virtually no other benefits. You will be squeezed for all you are worth. And most of that money is going to get wiped off in rent, because you are likely living in a different city than where your parents or family are living.

I will say … these CEOs are getting creative with their grift. They are now spinning longer/harder periods of work as a selfless act of patriotism for the nation (in this case, India). It’s an idiotic thought.
First, not many are going to subscribe the kind of selfless patriotism that yields low pay rates and high degrees of stress — mental, emotional and physical. If anyone wanted to subject themselves to that kind of patriotism, they would and should join the Indian Army, where you get a meaningful set of benefits and perks, and walk away with a sense of pride and honor after possibly building a career. Second, if you have to beg and/or coerce people into working longer hours, then either you are not paying them enough or you are subjecting them to work that is inherently never interesting, or both.

Now, if we are getting rid of boring work (because AI has automated it all), it should leave the more intellectually curious work for human workers. Such engaging work should engross workers so much that they will typically just work around the clock, and keep coming back for more assignments.

Then why talk of 996?

Are we NOT getting AI to do more work in an infinitely scalable ways?

Which is it — push for AI or push for 996? It cannot be both — I did not set these rules, tech CEOs did.

It feels like part of same grift. AI feels less transformative, and more an excuse to fire workers when and how owners/leaders want. Humanity has not automated away boring office work. It has merely invented newer ways of doing the same work that requires human involvement. That human involvement just needs newer routines than known previously. Sure, the routines are changing, but they are not going away.

996 is intellectual dishonesty. Yeah, I said it.

#996 #ai

🏏 Watching the Indian National Cricket team play test cricket. it’s been a while since I have followed cricket matches live. Their current head coach Gautam Gambhir needs to be sacked by the end of this home-series vs. South Africa. Otherwise, it is hard to see how the BCCI is not corrupt.

#cricket #testCricket

17?! Every time I think tech cannot/did not descend further into depravity, I stand corrected. And in that regard, Meta is a particular “gift” that keeps on giving. Simply odious.

#disgusting #facebook

🏏 Ending superstar culture in Indian Cricket

The current coach of the Indian national cricket team is on a simple mission: to end the team’s “superstar” culture. He is accomplishing it, by becoming the center of attention.

I am nothing more than a fan who has followed Indian cricket since the age of ten. I have no practical experience in playing the game at any level. But as a near-lifelong viewer I can tell that something is off.

Normally in post-match press-conferences, the Captain shows up as the team’s primary spokesperson. I have long remembered images of Ganguly, Dhoni, and Kholi field questions from the press. These have been iconic leaders of Indian cricket.

More recently, the Coach – in this case Gautam Gambhir – has taken over that mantle of spokesman. It’s fine. But it has put a lot of attention on him. And has made him the de facto face of modern Indian cricket. Every where you look, it is Gambhir. I doubt people actually remember or know who captained the last international cricket match that India played last week. Hint: it was not Shubman Gill.

Gambhir wanted to end superstar culture in the Indian Cricket team. At first I took it to mean that he wanted players focus on their skill. And certainly not become bigger than the team or the sport itself. That is a nice idea to be honest. Too often, players like Kholi, Rohit or SKY (aka Suryakumar Yadav) start to resemble gods. Indian crickets can amass a disproportionate about of fame, and celebrity with stellar performances on field. In my opinion, there is exactly one player who has truly earned the fame and celebrity that he enjoys. But i digress. Sometimes high levels of fame, celebrity and attention can get in the way of actual performances – understandably. So if it can improve on-field performances – with good reason to think so – then why not end super star culture?

By all appearances Gambhir has certainly managed to nix any super-star culture in Indian cricket. No Indian cricketer in the national side is a household name any more. Unlike Gavaskar, Kapil Dev, Tendulkar, Ganguly, Yuvraj, Kholi, or Harbhajan. If anything the Coach is the current face of Indian cricket. And none of this has translated to on-field performances. The two may not be causally linked, or even correlated in some coincidental way. But two things are clear, related or not:

  • You can no longer think of players in the Indian cricket team as stars.
  • The Indian Cricket Team is not winning cricket matches.
  • Where this takes Indian cricket on the international circuit is anyone’s guess. I am holding out hope that it changes Indian cricket for the better. But Gambhir is going about this in the most ham-fisted ways possible.

    I also suspect that he is fighting the very nature of cricket in India. Cricketers are famous in India. To be a successful, international cricketer on the Indian team, is to be a superstar — that’s Indian cricket.

    To end superstar culture in Indian cricket is like saying, “I will take away ‘Silicon’ from the name Silicon Valley.” I suppose you can. But you are removing something that is so essential – almost elemental – that it binds the whole together.

    #cricket #india

    When writing tests, i do not optimize for code coverage

    I have now been on both sides of the code coverage debate. I have advocated that test suites should achieve higher code coverage. I have also advocated against using code coverage for blocking PR merges.
    And fair warning: what i say next is based on my lived experience as a developer, and may not apply to all software engineering contexts.

    Some things i have learned to be true, over my time researching and practicing software engineering:

    • You can execute the same line of code a million time without ever catching a bug in that line.
    • Higher code coverage does not mean better tests.
    • Code coverage can be gamed.
    • Some code cannot be executed naturally in a test environment. A lot of UI and configuration code falls neatly in this category.

    Given that, I have landed on a very basic philosophy around writing tests, and how code coverage factors in:

    I do not optimize my test code for higher code coverage. And instead use coverage data to prioritize what i need to test and leave untested.

    The coverage metric itself is not meaningful to me. I rather have only 30% code coverage if i am testing the most critical sections of the codebase. I prefer that over covering 70% of the codebase which may be peripheral to the program’s implementation.

    Beyond the coverage metric itself, i am more interested in the set of lines got executed by the test. And i like to examine this data by each method or function. That tells me if the lines that I think should get executed are actually getting executed. I also use such insight to think about the program inputs i need to conjure to exercise the lines of code that are getting skipped from execution.

    Indeed, that sort of analysis can be time consuming. But to me it is no different than the time I spend in investigate bugs in production code with breakpoints and step-through debuggers. I use the full set of covered (and uncovered) lines as data in gaining a deeper understanding of how my test code is working.

    Personal take: Code coverage is not something that should be optimized for. It should be treated as an honest reflection of what got executed by the test(s), and what did not. That gives real insight into the inner mechanics of the test code.

    #codeCoverage #programming #softwareMetrics #softwareEngineering #testing

    Shifting UI paradigms: Feed. Story. Chat.

    Every five to ten years software engineering and computer interfaces seem to be getting a newer user interface control. Every new such UI control seems to be more popular than the previous era’s hero UI control. Right now, we are in what I call the “Chat” generation. The generation before was all about the “Story” UI — which gave way to “reels” or “shorts”, and even the base interactions in live video streams. The era before that saw the rise of the “Feed” UI, with my earliest memories of such interfaces dating back to Facebook’s Wall, or Orkut’s post feed.

    The Chat era started in late 2022 with the release of ChatGPT. It was preceded by the Story era, starting around 2014 with Snapchat’s rise in popularity. Snapchat’s user interface control to tell vanishing visual stories with highlights and text overlays became popular and eventually pervasive. While it started with social media, it soon found its way to places like LinkedIn1 and Signal. Going as far back as 2008, we got the first draft of the modern-day social Feed, when Facebook first introduced the Wall. Facebook’s take was a refined version of feeds in MySpace or Orkut. But it paved the way to follow not just friends but social influencers.

    None of these UI controls were new when they exploded in popularity. We have always had chat interfaces for instant messaging. RSS feeds with their focus on links likely seeded the idea for social media feeds. IRC chat streams gave way to information feeds we find ourselves in — both for group chats and microblogging feeds. The Story/Reel UI was a re-imagination of the photo carousel in portrait mode.

    I sound reductive – although not intentionally. Truth is that these UI controls have undergone numerous iterations to situate themselves in newer information and interaction contexts. And while those iterations were key, such evolutions were driven by the demands and contexts of the time.

    AI changed chat. The Chat interface had to evolve from a human-to-human paradigm to a human-to-bot paradigm. An explosion of multimedia – images and videos – compelled the creation of the Story control. The creators of the Story UI control needed fuse the complexity of annotations, fonts, colors and text boxes in PowerPoint presentations with the simplicity of photo slideshows. Social networking changed how we think about feeds in general. The feed of links had to iterate from serving a single-user experience in RSS readers to a social, multi-user experience that we find in modern social networks.

    It is easy to pigeon-hole these advances as a product of social media. But the recent uptick in “chat” implementations has bucked that trend with applications in domains ranging from enterprise to programming. The Chat UI is a peculiar case for a different reason as well. Larger paradigm shifts like AI certainly evolved Chat as user interface control. But the UI control itself re-defined what social networks looked like. Even before AI took center stage, IM apps’ natural evolution to group messages reshaped what social media is. Think Slack, WhatsApp Telegram. Group messaging platforms took the 1-to-1 instant messaging interface, and expanded it to multiple users with one chat feed visible to all. At one point it caused Twitter to be relegated as nothing more than a public group chat. It also elevated IM apps like WhatsApp to a “social-network” status.

    Each era offers a rich body for work for software engineers, designers, and product managers. That work entails reworking the whole software and product stack in light of these newer interfaces. In particular, think of — (a) implementing these frontend interfaces; (b) redesigning and re-implementing existing user-workflows around these newer interface paradigms; and (c) rewiring or tooling bank-end systems to support the evolving frontend.

    The Chat era has been particularly replete with work, or re-work in many cases. So much so that we are now rethinking what browsers are. Interesting to see what UI control we get next, and what work it spurs.

  • I think of LinkedIn more as a professional network, than a social network. But happy to concede that i am splitting hairs 😁 ↩︎
  • #chat #feed #product #reels #rss #snapchat #socialMedia #software #stories #userExperience #userInterfaces #whatsapp

    @vpalepu testing…

    I have started a new tech channel called Gunners Shot Tech. In this channel I will cover trends in military and emerging disruptive technologies. You may like to subscribe to it @ http://www.youtube.com/@GunnersShotTech-jl6gp

    https://youtu.be/Ai3cYh7OYZ4

    https://gunnersshot.com/2024/01/15/gunners-shot-tech/

    #DisruptiveTechnologies #Miltech

    Gunners Shot Tech

    MILITARY AND EMERGING TECHNOLOGIES SUBSCRIBE TO GUNNERS SHOT TECH AT http://www.youtube.com/@GunnersShotTech-jl6gp SUBSCRIBE TO GUNNERS SHOT AT http://www.youtube.com/@gunnersshot9829

    YouTube

    In this video, we have explored as to how AI can be put to use to fuse data from multiple sources to produce a holistic picture in multi domain operations. This is the future and one needs to get their hands dirty if we have to stay in the game. I hope those who want “Domain Awareness’ have a look at this to start a meaning program to achieve it.

    https://youtu.be/h893p4oNBzk

    https://gunnersshot.com/2024/01/11/ai-data-fusion-in-multi-domain-operations/

    #AI #Domainawareness #Multidomainops

    Gunners Shot Tech : AI & DATA FUSION IN MULTI DOMAIN OPS

    YouTube

    In *A City On Mars,* biologist #KellyWeinersmith and cartoonist @ZachWeinersmith set out to investigate the governance challenges of the impending space settlements they were told were just over the horizon. Instead, they discovered that humans aren't going to be settling space for a *very* long time, and so they wrote a book about that instead:

    https://www.acityonmars.com/

    1/

    A CITY ON MARS

    Earth is not well. The promise of starting life anew somewhere far, far away—no climate change, no war, no Twitter—beckons, and settling the stars finally seems within our grasp. Or is it? Critically acclaimed, bestselling authors Kelly and Zach Weinersmith set out to write the essential guide to a glorious future of space settlements, but after years of research, they aren’t so sure it’s a good idea.