Umakant Patil

Principal Architect, Learning Guitar when not coding

[Umakant Patil @TheRealUmakant]

@baabuOP It is good thing it is mandatory. The rule should be if you can deposit with whatever issues (e.g. name mismatch), should be able to withdraw with same ease.

[Umakant Patil @TheRealUmakant]

@ThatDesiGirl You ruined the song for me 😄

[Umakant Patil @TheRealUmakant]

@GemsOfMBMC @My_MBMC @narendramodi @iNarendraMehta @PratapSarnaik @CMOMaharashtra @krishnaguptaRTI @fpjindia @lokmattimeseng @RoadsOfMumbai

[Ludonauta @LudensLudonauta]

I was studying MCPs and this comment really blew my mind.

[Umakant Patil @TheRealUmakant]

AI has ruined the customer care support

[Sabudana khichadi @dishasatra]

Tukaram Munde sir ke pair choo ke thank you bolna hai🙏🙏🙏🙏

Can’t thank him enough for doing the bare minimum (not be corrupt)

[Umakant Patil @TheRealUmakant]

Is there a way to stop prerendering in Tanstack Start to get client side dynamic data in root component or shell? @tan_stack

[Umakant Patil @TheRealUmakant]

@aidenybai @shadcn

[Deedy @deedydas]

Most software engineers are facing an identity crisis bordering on depression.

As CTOs aggressively evangelize tokenmaxxing, a class divide ensues.

The lazy. The lazy push code. They don't write it. They don't manually test it. They don't even read it. They're on autopilot. See Jira ticket, prompt for task, submit code. Many of them are barely on their computer the whole day. A comment on the PR asking why they did this? The lazy ask AI. A Slack message? The lazy ask AI. Need to prepare for standup? The lazy ask AI. As long as it sounds enough like them and isn't detected. Some of the lazy are even overemployed, and work multiple jobs. The lazy smart ones get away with this, and even rewarded. After all, software engineering for the lazy is just a dance to convince your colleagues you're smart and hard working.

The craftsmen. The craftsmen are tired. Very tired. 15 PRs in queue. Slack blowing up. The entire burden of review falls on the craftsman. The burden of understanding. They try. They work their way through the code, thoughtfully commenting to improve what ships. The response? A lazy: "That's a clever idea! You're absolutely right." with an incorrect change. It's fine, the craftsman says. I can fix them. They write a doc urging his colleagues to be better. The next day? 20,000 line PR to review. Day after day, their workload grows. Bugs seep into production. No one seems to care. Another round of AI is thrown at it. Their animosity to their colleagues rises. Eventually, they give up. It's just not what it used to be. The craft they loved is dead. They eventually wake up, a lazy.

This isn't all companies. Many companies are genuinely more productive, adopt the right set of principles and practices around AI development and have highly talented teams that trust each other. It tends to happen in bigger companies that are 10+yrs old with a higher talent variance. But it happens. A lot.

[Mitchell Hashimoto @mitchellh]

Got em. I poison my AGENTS.md (and other things like code comments) all over the place with prompt injections like this to find people who don't review their code and sling it off to another human. Catches folks all the time and then its an instant ban.

As I've said, I don't care if you don't review your own code. But if you're submitting code to an OSS project and crossing a human boundary, it is simple courtesy to do some human review.

[Bella @BellaBaddie__]

Does anyone else spend the entire modern movie turning the volume up and down because there is zero sound consistency in movies anymore?

[Umakant Patil @TheRealUmakant]

@manish__aman @jaganmsna Boot space being primary driver

[Boring_Business @BoringBiz_]

CFOs realizing that their AI token budget is going to be higher than the salaries of the people they laid off

[Trendulkar @Trendulkar]

When I first watched Dhurandhar 2, I felt the music in Dhurandhar 1 was better. But now I’ve been listening to the songs on loop. D2 tracks are darker and have more replay value. Didn’t quite catch that in the film, but as standalone songs, they’re great.

[Vite ⚡ @vite_js]

⚡️ Vite 8.0 is here!
The most significant architectural change since Vite 2.

⏬ Powered by Rolldown bringing faster production builds and more consistency
🛤️ New features such as tsconfig paths and emitDecoratorMetadata support

[Umakant Patil @TheRealUmakant]

@Goofotl @DeepikaBhardwaj @UC_Assist @urbancompany_UC @abhirajbhal @letsblinkit @zomato What the. Customer deleted a order, so order becomes nullified. What a shady practice of @letsblinkit

Order high value items are real risks when ordering online

[Branko @brankopetric00]

Environment variables multiply like rabbits. You started with DATABASE_URL and now your application needs 47 environment variables just to start, and nobody remembers what half of them do.

[Naval @naval]

People who don’t organize into tribes get wiped out by people who do.

[Umakant Patil @TheRealUmakant]

Not using Acko Insurance ever in future. Doesn’t even allow to edit or download insurance on a website and want us to install app for smallest thing. Make things more accessible 🤷🏻‍♂️

[Dr Milan Milanović @milan_milanovic]

Kubernetes killed more startups than server crashes ever did

You don't have Spotify's scale. You have 8 engineers and a single server that's running fine

But you watched a KubeCon talk, and now you've got 23 YAML files, a Helm chart nobody fully understands, and engineers debugging pod evictions instead of buildinga product

Your "cloud-native infrastructure" is just a cloud bill with extra complexity

A $50/month VM can handle millions of requests. Your startup will run out of money debugging networking issues long before you need horizontal pod autoscaling

The best infrastructure decision is often the simplest one