novaragnar

[वाक़िफ़ हैं निगाहें 👀 @Tere_do_nainaaa]

“Never skip Zakir Khan's words.”💯

[The Driven Man @Thedrivenman]

How to read people in 30 seconds

[योगी @YogiBharatX]

जहाँ हाथों में जादू हो तो जायका तो तगड़ा होगा ही..

[YourCloudDude | AWS & Python @yourclouddude]

Don’t overthink AWS architectures ☁️

Start with these:
• Static website (S3 + CloudFront)
• 3-tier app (EC2 + RDS + ALB)
• Serverless app (Lambda + API Gateway)
• Event-driven system (SQS + SNS)
• File upload pipeline (S3 + Lambda)
• Monitoring setup (CloudWatch + SNS)
• Auto scaling system (ASG + ELB)
• Secure VPC setup (public + private subnets)
• CI/CD pipeline (CodePipeline)
• Multi-region failover (Route 53)

Learn by building → not memorizing.

[Uday👨‍💻 @uday_devops]

Terraform workflow and commands 📚📕

[Saidul @saidul_dev]

Yale University students pay a premium to learn from Professor Ben Polak.

One of his most valuable lectures is sitting on YouTube for free.

It explains the hidden logic behind negotiations, pricing, salaries, and decision-making.

Topics like:
• game theory
• strategic thinking
• incentives and tradeoffs
• Nash equilibrium
• backward reasoning

Most people walk into negotiations relying on instinct.
The people who understand these ideas walk in with a framework.

That difference quietly shapes careers, income, and outcomes over time.

Spend an hour with this lecture and you’ll start seeing decisions through a completely different lens.

Free to watch.
Save it before it disappears into your feed.

[Dr. Anshul Sadhale @AnshulGains]

Multivitamins are useless.

Watch this video before popping random pills.

[हिन्दी पंक्तियाँ @Hindi_panktiyan]

ये पूरा का पूरा पॉडकास्ट ही बहुत प्यार है।

[Jaynit @jaynitx]

Marc Andreessen on Elon Musk: "Every week he identifies the biggest problem and fixes it. That's 52 problems solved per year."

"He has an operating method that is very unusual by modern standards. I'm not aware of another current CEO who operates the way that he does.

And I think probably the single biggest question in all of business right now is... why don't more CEOs operate the way that he does?"

Andreessen explains:

"If you go back in history, you find characters more like him. The industrialists of the late 1800s, early 1900s... Henry Ford, Andrew Carnegie, Thomas Watson who built IBM."

On what makes Musk different:

"The top-line thing is this incredible devotion from the leader of the company to fully, deeply understand what the company does. To be completely knowledgeable about every aspect of it. To be in the trenches, talking directly to the people who do the work. Deeply understanding the issues. Being the lead problem solver in the organization."

The method:

"Basically what Elon does is he shows up every week at each of his companies. He identifies the biggest problem the company is having that week... and he fixes it. Then he does that every week for 52 weeks in a row. And then each of his companies has solved the 52 biggest problems that year."

On everyone else:

"Most other large companies are still having the planning meeting for the pre-planning meeting for the board meeting for the presentation... with the compliance review and the legal review. It's this level of incredible intellectual capability coupled with incredible force of personality, moral authority, execution capability, focus on fundamentals... that is just really amazing to watch."

On why top talent wants to work with him:

"The side effect is he attracts many of the best people in the world to work with him. Because if you work with Elon... the expectations are through the roof in terms of your level of performance. He is going to know who you are. He is going to know what you've done. He is going to know what you've done this week. He is going to know if you're underperforming. And he may fire you in the meeting if you're not carrying your weight."

But for those who match his commitment:

"If you are as committed to the company as he is and working hard... many people who have worked for him say they had the best experience of their lives."

On delegation... and the bottleneck:

"Most CEOs have a problem knowing when to delegate. The Elon method is a little bit different. He actually delegates almost everything. He's not involved in most of the things his companies are doing. He's involved in the thing that is the biggest problem right now... until that thing is fixed. Then he doesn't have to be involved anymore. Then he can go focus on the next thing that's the biggest problem."

Andreessen uses a manufacturing analogy:

"In any manufacturing chain, there's always a bottleneck. Something keeping the line from running the way it's supposed to. Sometimes the bottleneck is at the beginning... we can't get enough raw material. Sometimes it's at the end... we don't have enough warehouses.

Or it might be somewhere in the middle. Whatever the bottleneck is... is holding everything up. Job number one is to remove that bottleneck and get everything flowing again."

Musk universalized this:

"He looks at every company like it's some sort of conceptual assembly line... sometimes a literal assembly line making cars and rockets. Any given week, there's guaranteed to be one main bottleneck. One thing holding people back."

The resolution:

"I'm going to micromanage the solution of that. I don't need to manage everything else... because everything else, by definition, is running better than that. So I can go focus on that."

On going directly to the source:

"When he identifies the bottleneck, he goes and talks to the line engineers who understand the technical nature of the bottleneck. If it's people on a manufacturing line, he's talking to people directly on the line. If it's a software development group, he's talking to the people actually writing the code."

What he doesn't do:

"He's not asking the VP of engineering to ask the director of engineering to ask the manager to ask the individual contributor to write a report... to be reviewed in three weeks. He doesn't do that. He goes and personally finds the engineer who actually has the knowledge about the thing. Then he sits in the room with that engineer and fixes the problem with them."

Andreessen explains why this inspires loyalty:

"The technical people who work with him are like... wow, if I'm up against a problem I don't know how to solve, freaking Elon Musk is gonna show up in his Gulfstream and sit with me overnight in front of the keyboard or in front of the manufacturing line and help me figure this out."

He asks:

"If you're a normal CEO running a normal company... how can you possibly compete with that?"

On why other CEOs don't do this:

"It's the way management is taught. Most classically in something like Harvard Business School or Stanford Business School. It's management as it was developed in the 1950s, 60s, 70s... the so-called scientific school of management."

He describes it:

"Management as a generic skill you can apply to any industry. You could manage a soup company or a car company... they're kind of all the same. There's a common set of management practices. It's process. How to manage the balance sheet. How to set the review schedule for meetings. How to do compliance. How to hire and motivate executives. How to resolve interpersonal conflicts. All these general business skills."

The problem:

"Those general business skills are very useful in lots of contexts. But that training gives you none of what you need to go do what Elon does."

Andreessen concludes:

"Elon pushes as far as he can... not doing all the stuff you're classically trained to do... so that he can spend all of his time doing the things only he can do. And it turns out that has this incredible catalytic, multiplicative effect. His companies are just incredibly amazing."

[Sri @__karnati]

Most engineers say they "know Kubernetes."
But can you trace a request from the browser to the pod?

Here's the full journey. End to end. 👇👇👇

1. User opens your app.

- DNS resolves the domain.
- AWS Route 53 (or your DNS) points to a Load Balancer.

2. The AWS Load Balancer (ALB/NLB) receives traffic.

- It's Layer 7 — it reads HTTP headers, paths, and rules.
- It decides: "Which Kubernetes Ingress should get this?"

3. Ingress Controller (NGINX / Traefik / AWS ALB Controller) receives the request.

-It matches the path rule from your Ingress resource.
-"/api/v1/users" → routes to service "user-svc"

4. Kubernetes Service picks it up.

- kube-proxy or eBPF (Cilium) translates the Service ClusterIP to a real Pod IP using iptables/ipvs rules.
-This is service discovery in action.

5. The Pod handles the request.

-It may call other microservices internally.
- DNS-based service discovery again → "payment-svc.default.svc.cluster.local"

6. Databases and external APIs respond.

- PersistentVolumes, RDS, Redis, all hit in milliseconds.
- Timeouts, retries, and circuit breakers matter here.

7. The response travels back through the same chain.

- And Prometheus scrapes metrics from your pods the entire time.
- Grafana shows you exactly what happened.

A single user click triggers DNS → LB → Ingress → Service → Pod → DB → back.
End-to-end
Engineers who understand this flow debug 10x faster.

Follow for more Kubernetes + DevOps breakdowns 🧵

[Mario Nawfal @MarioNawfal]

🇺🇸 @elonmusk on why most people never make it:

"If you're in the Matrix, success was never possible. The only way to achieve success is to reprogram the Matrix."

Change the system or stay stuck in it.

[Camus @newstart_2024]

Chris Williamson dropped a hard truth on Joe Rogan:

If you actually change your life for the better, you might have to let go of your friends.

And if you keep growing… you’ll probably have to do it multiple times.

You finally find your people after the lonely phase, then realize you’ve outgrown them too. That repeated loneliness is exactly why most people stay stuck — the comfort of old friends is a powerful anchor.

Real growth isn’t just about discipline or goals. It’s often about relationships. The circle around you either lifts you or holds you back.

This one stings because I’ve lived it. Those seasons of walking away are painful, but staying the same is worse.

Have you ever had to leave behind a friend group because you were growing in a different direction?

[Manisha Mishra @manishamishra24]

Instead of watching an hour of Netflix, watch this 30-minute speech by the Head of Anthropic’s Coding Agents research team. It will teach you more about vibe coding than 100 paid courses.

[Dr. Mansafa Bepari @MANSAFAB]

You stopped eating rice and you still don’t lose that stubborn belly fat?

Eating less is not working for you.

Follow these 5 steps to get out of the plateau:

1. Stop extreme diets
2. Lock in protein
3. Stop this particular workouts
4. Fix hidden fat loss killers
5. Track these metrics

[Dr. Rhonda Patrick @foundmyfitness]

I'd encourage everyone to grab a copy of Dr. Arthur Brooks' new book 'The Meaning of Your Life' or gift it to someone who might enjoy it (I plan to buy a few copies myself!)

He shares so much wisdom on how to live a happy, fulfilling life.

[Goldie @dezgoldie]

This is the only advice you’ll ever need. Gas pedal.

[Dale Vaz @dale_vaz]

We just closed our Series B. $33M at $200M valuation. 3.3x step-up from Series A.
I'll be honest, I almost didn't post about this.

Valuation is the easiest number in a startup to celebrate. It's also the least real. It's just a number that our investors and us agreed on in a room. That's it.

The numbers we actually celebrate are different ones:
→ 4 lakh demat accounts. Each customer acquired by our marketing teams, with honest messaging and sharp targeting.
→ 96% of orders executed under 10ms. Each millisecond fought for by our engineers who care deeply about slippage and losses.
→ 40+ product releases in 1 year. Each one shipped by a super lean product and tech team that is innovating at AI native speed.
→ 130 million trades processed since launch. Each one processed flawlessly by our dedicated Operations team, every single day
→ 90% CSAT positive rating. Each customer interaction carefully resolved with genuine care by our Customer Delight team

These numbers don't come from capital. They come from the team. This Series B funding isn't a finish line. It's just rocketfuel for the team that built and operates this thing.

And so, I raise a toast to the Team at @Sahi_HQ . Thank you for everything you bring to work every single day, and the impact you create. Onwards and upwards.

[Sanket @BTechComedian]

घरचे सांगतात वाईट, मतलबी लोकंपासून दूर रहा, अनुभवातून सांगतो Sadistic Mindset वाल्यांपासून जास्तच लांब रहा. यांना जळी, स्थळी सगळच वाईट, उणीव दिसते मग Office काम, बारसे, लग्न, हळद ते Society Redevelopment. वयानुसार हा Mindset एखाद्या Clinical Disorder सारखा होतो आणि चितेवरच संपतो.

[Allen Braden @allen_explains]

Anthropic hires engineers who deeply understand how AI systems actually function, and those skills are worth serious money.

Now, Stanford University has released lectures covering the same foundations for free on YouTube.

Don’t leave this sitting in your bookmarks.
Set aside time this weekend and watch it.

[Saurav Chaudhary @sauravstwt]

Docker has become the master of containers.

But for beginners remembering all the commands can feel difficult .

That’s why I created this Docker Commands cheatsheet that neatly organizes the most important commands across different categories:

1. Images
From docker pull (download images) to docker build (create from Dockerfile) and docker tag (versioning), this is where containerization begins. Managing images is the foundation of every Docker workflow.

2. Containers
Commands like docker run, docker exec, and docker logs help you create, run, and debug containers. This is where Docker shifts from theory to practice, bringing applications to life.

3. Build & Dockerfile
docker build, --target, and --build-arg let you customize how images are built. Mastering this area means cleaner, more efficient Docker images.

4. System & Cleanup
Over time, Docker environments get cluttered. Commands like docker system prune and docker df keep your system lean and resource-friendly.

5. Networking
From docker network create to docker network inspect, networking is what lets containers talk to each other. Without it, Docker is just isolated boxes.

6. Volumes & Storage
Persistent data matters. Commands like docker volume create and docker volume prune ensure you don’t lose critical data (and don’t end up with disk bloat).

7. Inspect & Debug
Troubleshooting becomes easier with commands like docker inspect, docker events, and docker diff. They reveal what’s happening under the hood.

8. Docker Swarm
For clustering, commands like docker swarm init, docker service ls, and docker stack deploy scale containers across multiple nodes.

9. Docker Compose
Finally, the powerhouse for multi-container apps: docker-compose up, docker-compose down, and docker-compose exec simplify orchestration at the project level.

Docker isn’t just a tool, it’s a workflow helper.

Learning these commands gives you superpowers in DevOps, cloud, and modern app development.

Bookmark it.