Rohitesh Dutta

Journalist: Kaunsa accha kaam kiya tha Modi ji ne ? Protima Sarkar : Oi ja maar-pit kiya tha woh accha laga mujhe (referring to operation Sindoor ) 😆

Bro shifting gears like pro 😂🔥

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

Professor corrigindo os alunos do lado de fora da piscina. Até eu aprendi daqui 🫶🏼

My dad used to put his thumb impression on my mark sheet... I asked him: Being a Chartered Accountant, why are you putting your thumb impression, instead of signing on my progress card? My dad replied: idiot, after looking at your marks, the teacher should not think that I am educated.... 😂😂

Dear white people .. this is how you survive in horror movies - don’t ask questions … just run 🏃‍♂️

At the airport, a sweet Mallu girl sitting next to me, just said to me, "Ye Lawde" I gave her a piercing, angry stare, surprised how this girl could say something like that? I was about to blast her, but then I saw her pointing at her baggage & I replayed those words slowly in my mind, and then realized she actually had said, "Yeh allowed hai? I bet you'll replay it in your mind with a Mallu accent 🤣🤣

Post Op-Sindoor, Trump repeating the number of jets lost was a calculated move, he was tutored. They knew this irrelevant number in the face of mission objectives, has been hyped up by the opposition & enemies abroad. The plan was to weaken Indian hand, to accept the lopsided trade deal, open up agriculture, to make Trump stop. Suddenly Trump is not mentioning any number of Jet crashes in Iran. Suddenly it’s about operation goals. Credit to the govt for not giving in.

"Chinki, Chinese, momo girl." 😡 "North-East girls faced racism again." ❌ At Patna Railway Station, Bihar, a woman abused NE girls by using slurs chinki, momo.., TARGETING THEIR APPEARANCE. The Railway Administration should arrest her without any delay. She is so disgusting!

IT WAS FORETOLD, BUT IT IS NOW REALITY, GITHUB HAS ACHIEVED 2 9's OF RELIABILITY!!!

guys, i honestly do not like clowning on Gary. I don't find being the butt of a joke funny, so I imagine he does not either. But, this is what worries me about where we are going. We are actively encouraging an entire generation that the tech is there when its not, and a couple of silly mistakes made on a website isn't the end of the world, but people's data and breaches are serious. We are entering a very VERY hackable world, and I do not like it one bit.

I have seen more systems struggling because of wrong code than slower ones. The fact remains, most engineers optimise too early. About 8 years ago, my principal engineer once told me: Performance is almost always the last thing you should be thinking about. As an SDE-2, this did not make sense :) After a few follow-ups, I understood why he meant that. The order that actually matters is this. First, is the code correct? Does it do what it is supposed to do? Second, can someone maintain it six months from now without wanting to quit? Third, is it fast to read and write? Only after all three does performance even enter the conversation. The reason this order exists is simple. A fast, unmaintainable codebase is a liability. A performant-but-wrong system is worse than a slow, correct one. You cannot optimise your way out of a bug. Now, this is not universally true. Databases, high-frequency trading systems, and real-time embedded software are domains where performance is a first-class concern from day one. But those are the exceptions, not the default assumption you should bring to every PR. What is certainly true is that for most codebases, premature optimisation adds complexity, reduces readability, and solves a problem that does not exist yet. So, write correct code first. Then clean it. Then, only if the profiler gives you a reason, make it fast.

A blind baby sees his mother for the first time after surgery. Look at his reaction

Dhurandhar if made by YRF 😅