Lohith

A student of life, one simple step at a time. Trying to understand things using common sense

[Priyansh Agarwal @Priyansh_31Dec]

Life when you are obsessed with solving a single problem and nobody bothers you with anything else >>>>

[Lohith @SimplyLohith]

@RDogrades Price?

[Lohith @SimplyLohith]

@Rajiv1841 Ah, so you don’t follow the pitch report before the match and make assumptions while a team is batting? Brilliant. Mullanpur is known for slow pitches too.

[Ashwin 🇮🇳 @ashwinravi99]

Travi-shek restoring normalcy for Hyderabad. #ipl2026

Orange Army 🔥🔥

[Shubhvani @shubhvanii]

Neverrrrrrrrrrrr forget the person who taught you the work when you were new and clueless.

Many people can hire you, but only a few will teach you with patience, protect you when you make mistakes, and say, "Don't worry, you learn."

That person deserves lifelong respect.

[Lohith @SimplyLohith]

@striver_79 Agree, but how do resumes get shortlisted at first? Is it through ATS scanners? If so, then how can we even pass the resume shortlisting phase when applying for jobs, especially when we want to include genuine points? Just a question on my mind in general.

[Elon Musk @elonmusk]

😑

[Lohith @SimplyLohith]

@systemdesignone Playbook

[Neo Kim @systemdesignone]

API Design Playbook:

Giveaway Alert!!

• Core API fundamentals.
• Clean & scalable design principles.
• Common patterns used in real world systems.
• Practical concepts for interviews & building projects.

(24 hours only & I won't offer this ever again!)

To get it:

1. Like, Retweet & Follow @systemdesignone
2. Reply "Playbook"

Then I'll DM you the details.

[Lohith @SimplyLohith]

Fascinating article that I read after many years. Please suggest some more related to these kinds of topics if anyone happens to know them.

https://t.co/BBKk65lAVX

[IT Unprofessional @it_unprofession]

Our intern just asked me why we don't use Kubernetes.

I said because we don't need Kubernetes.

He said everyone uses Kubernetes.

I said everyone TALKS about using Kubernetes. Most companies are running Docker containers on three servers and calling it a day.

We have 40 employees. Our entire infrastructure runs on AWS with auto-scaling groups. It works fine.

Kubernetes is designed for companies running thousands of services across hundreds of servers. We have twelve services.

But he read that Kubernetes is "industry standard" so now he thinks we're behind.

This is what happens when people learn from tech Twitter instead of actual experience.

They think every company is Google-scale and needs Google-scale solutions.

We don't need Kubernetes. We need our MySQL database to stop running out of connections because someone wrote a query that doesn't close properly.

But that's not exciting. Nobody writes blog posts about "I fixed a connection leak."

They write about "How we migrated to Kubernetes and saved millions" even though the migration cost more than they saved.

I told the intern he should learn why tools exist before learning the tools themselves.

He looked disappointed. He wanted to put Kubernetes on his resume.

[Ray Dalio @RayDalio]

Discuss your issues until you are in sync with each other or until you understand each other's positions and can determine what should be done. As someone I worked with once explained, "It's simple--just don't filter." #principleoftheday

[Indian Tech & Infra @IndianTechGuide]

This is a massive win for the Indian AI revolution. 🤯

[ThePrimeagen @ThePrimeagen]

very cool study

very happy to see anthropic measuring the negatives as well. Honestly good for them

[Striver | Building takeUforward @striver_79]

If you want to buy things without looking at the price, start working without looking at the clock.

[Arpit Bhayani @arpit_bhayani]

Not every mistake needs a correction.

Some folks take a little too much joy in proving others wrong. Sure, it can feel satisfying - especially when you're right. And yes, sometimes stepping in is the responsible thing to do.

But if you're constantly scanning for flaws and calling them out, you're not being helpful - you're just being exhausting. People remember how you made them feel far more than whether you were technically right.

Give others the benefit of the doubt. Maybe they missed something. Maybe they're just having a rough day. If it's not mission-critical, let it go. Kindness doesn’t mean staying silent - it means being intentional about how you speak.

- If someone misses a small detail in a PR, nudge gently
- If someone shares an idea that’s slightly off, don’t tear it down
- If someone gets something wrong, help them understand without making a scene
- If you're in a group setting, choose private correction over public shaming - always

When this nitpicking behavior becomes normalized, it starts shaping team culture - and not in a good way. In some orgs, it's even unintentionally incentivized.

People start optimizing for not being wrong instead of moving fast and learning. Everyone gets a little more defensive, a little more hesitant. Progress slows down - not because people aren’t smart, but because they’re too busy being careful.

Engineering is not a zero-sum game. You don’t win by pulling others down. You build influence by being the person others want to work with.

Be kind. You're not here to win arguments - you're here to build.

[Lohith @SimplyLohith]

Couldn't agree more. I recently started DSA about a month ago with @thita_ai. It starts with theory and builds upon problems. I'm enjoying every bit of it.

[Vaishnavi @GeekyVaishnavi]

Been revisiting my DSA prep and realised something again —
doing random problems only takes you so far.

What actually helps is pattern recognition.

I’ve been using a 93 DSA patterns sheet that groups problems by ideas like
sliding window, two pointers, recursion, DP, graphs, etc.
Once the pattern clicks, new problems stop feeling “new”.

What I liked is that it’s not just a list of problems —
it also includes theory and video explanations for each pattern.

Feels much more structured and less overwhelming than blind LeetCode grinding.
If you’re preparing seriously, learning patterns first is a game-changer.

Sharing the sheet here in case it helps someone.

[Paras Chopra @paraschopra]

It’s a great comfort to realise that, no matter who you are, the marginal impact of your work on the future is close to zero.

Most outcomes are inevitable in the long run - if you don’t do it, someone else will.

This was true for relativity theories, and is certainly true for most of the everyday work we all do.

This realisation should be a reminder that one must work earnestly and live the only life you have got, but not sacrifice finite time for a delusion that simply isn’t true.

[K Srinivas Rao @sriniously]

one common thing I have always noticed in the kind of content that I consume and see other people love consuming, and the kind of products that I feel is wildly intuitive, is that, most of the times these creations are the results of founders/creators getting annoyed at their workflow or strongly feeling the gap, so much so that, they feel this strong urge to fix it themselves. go ahead and try it, think back, the kind of videos that you care enough to hit the like button or post a comment, the articles that you bookmark or the saas product or dev tool that is an integral part of your workflow.

there is that energy, that you can’t fake. when someone creates something to scratch their own itch, you feel it. the attention to detail, all the edge cases handled because they have LIVED those. the explanations land perfectly in your brain like a tetris because they remember what confused them. The feature prioritisation always works in the market because to date they are still the target users.

now contrast that with content or products built "for the market." You also feel that instantly. that saas landing page, that youtube video optimized for the algorithm, that blog post written to rank, you know exactly what I’m talking about, we see those everyday.

when something feels meh, I ask, was this made by someone who would actually use/consume this? 9 times out of 10, the answer is no. they just reverse engineered what they thought people wanted instead of building what they knew people needed because they needed it themselves.

fortunately, our tech ecosystem is so beautiful today because the number of "I made this for me and people like me" stuff still dominates the "I made this for you" stuff

[Lohith @SimplyLohith]

@AurvaWorld, it's been one month since I ordered a puzzle, and there's still no information. No response to emails or Instagram DMs. When can I expect the order? Could you please at least inform me of the delivery status?