muneeb

[muneeb @____muneeb]

@cagataycivici So what happened to open source for life 😑

[Chesny @chesny]

Una skill de Claude llegó a 58.000 estrellas en GitHub en una semana. 2,9k forks, gratis.

Hace que Claude programe como el senior más vago: 54% menos código, 20% más barato, 27% más rápido.

Añádela a Claude Code hoy.

[ClaudeDevs @ClaudeDevs]

What are best practices for running Claude Code at scale?

New blog post on what we've learned from teams running it across multi-million-line monorepos, decades-old legacy systems, and distributed microservices:

https://t.co/rJUYlIUiTT

[Irfan Akbar @majorirfanakbar]

Life these days 😢

[muneeb @____muneeb]

@SaadInCyber Having a dividend yielding portfolio for that amount guarantees the same thing plus a little more.

[John Galt @dadiani_george]

@AXChristoforou There’s a historical documentary about it actually. Here it is: The Art of War, by Don Tzu.

[DumWalaPaani @Champ4gneP4ki]

Pakistan Zindabad 🇵🇰 🇵🇰 🇵🇰

[A. @Ahmadridismo]

Pakistan Humesha Zindabad !!!

[Khawaja Abaid @KhawajaAbaid]

pakistani fellas, are you tired of winning yet?

[Kanye East @FuckedUpYogis]

I promised Hafiz Fancam if he pulled it off. The mad lad did it.

Nuclear Winter cancelled

40 yard screamer to take lead in Nobel Peace Prize Power Rankings

[Ahmed @effsixteen]

just leaving it here

[K. @RotiKholDeyo]

Shehbaz teri parwaz se jalta hai zamana

[Kshitij Mishra | AI & Tech @DAIEvolutionHub]

This AI System Design guide teaches RAG better than most courses.

Giving it away FREE
(only for first 4500)

Inside:
• RAG fundamentals & chunking
• Hybrid retrieval (BM25 + vector)
• Production RAG architecture
• Evaluation + RAGAS
• Hallucination reduction
• End-to-end LLM systems

How to get it:
• Follow me (for DM)
• Like + Repost
• Comment "RAG"

I’ll send it 👍

[Utkarsh Sharma @techxutkarsh]

A senior Google engineer just dropped a 421-page doc called Agentic Design Patterns.

Every chapter is code-backed and covers the frontier of AI systems:

→ Prompt chaining, routing, memory
→ MCP & multi-agent coordination
→ Guardrails, reasoning, planning

This isn’t a blog post. It’s a curriculum. And it’s free.

[Vaishnavi @_vmlops]

System Design rounds are where most engineers lose FAANG offers
this repo fixes that... courses, books, cheat sheets, interview Qs, all in one place

Repo - https://t.co/Q1zPw0ws3z

[Abhishek Singh @0xlelouch_]

If you want to be a distributed systems engineer who wants to become Staff at FAANG, I would say this a bit differently.

Do not try to learn 17 things as separate checklist items and then keep changing languages every 3 months.

That is how people keep “preparing” for 5 years.

You do not become Staff because you know REST, GraphQL, gRPC, Redis, Kafka, Docker, Kubernetes, AWS, Prometheus, Grafana and 40 other buzzwords.

You become Staff when you can look at a messy production system and answer things like:

Why is p99 latency suddenly bad? Why is replication lag increasing? Why are retries causing a thundering herd? Why did this cache make things faster yesterday but inconsistent today? Why did one region fail and now the whole system is timing out? Why does this service need to exist at all?

That is the real game.

For wannabe Staff engineers, the path is more like this:

1. Pick one backend language seriously. Go, Java, or even Python if your stack allows it. Not because language is everything, but because syntax should become invisible to you.

2. Go deep on fundamentals. Networking, OS basics, concurrency, storage engines, indexes, transactions, consensus tradeoffs, queues, failure handling. This is where actual engineers are separated from tutorial collectors.

3. Build systems, not toy CRUD apps. Rate limiter. Job queue. Distributed cache. Event driven pipeline. Notification system. Search autocomplete. Write something that breaks under load, then fix it.

4. Learn tradeoffs, not definitions. Strong consistency vs availability. Sync vs async. Horizontal vs vertical scaling. Partitioning vs replication. Monolith vs microservices. Every Staff conversation is mostly tradeoffs.

5. Get very good at observability. Logs tell you what happened. Metrics tell you how bad it is. Traces tell you where it broke. Most engineers write code. Few can debug production calmly.

6. Write design docs. A lot of people want Staff title. Very few can clearly explain: problem, constraints, proposed design, bottlenecks, rollback plan, and why this is the right tradeoff for the business.

That is why some engineers with less tech stack knowledge still grow faster.

Cause Staff is not “best coder in the room”.

It is usually: the person who sees around corners, reduces future incidents, simplifies systems, and helps 5 other engineers move faster.

So yes, learn system design. Learn APIs. Learn databases. Learn distributed systems. Learn caching. Learn security. Learn cloud. Learn monitoring.

But do it through one serious language and repeated real system building.

Otherwise you are just collecting nouns.

And FAANG does not promote noun collectors.

[Katyayani Shukla @aibytekat]

🚨 BREAKING: Claude can now prep you for FAANG interviews like a $1,000/hour executive career coach. For free.

Here are 18 prompts that get you past the final round within 14 days:

[Vaishnavi @_vmlops]

This is actually crazy 🤯

https://t.co/yReuA8ki65

A whole job hunting system built like a DevOps pipeline… tracking apps, tailoring resumes, everything automated

CI/CD for getting hired?? yeah we’re living in the future

[‏ً @omgsidewalks]

Yo!!! You wake up at 25. Make coffee. Go to work. Come home at 8. Too tired to do anything but scroll and sleep. Then Friday hits, maybe you go out, maybe you're too exhausted. Suddenly you realize: when did 15 become 10 years ago? You don't feel 25. You feel stuck in a loop you never signed up for.

Here's what they don't tell you: this is by design. The 9-to-5 wasn't built for your dreams. It was built to drain you just enough to keep you compliant. You work, consume, repeat. No time to question. No energy to build. And before you know it, 25 becomes 35, then 45. The system needs you tired. Because tired people don't rebel. They just survive. So if you're 25 and feeling this, you're not broken. You're waking up.

And that older version of you? They're not begging you to enjoy it. They're begging you to escape it