Ankit

Defence Brat 🇮🇳Senior Software Engineer | | Building Tech for the nation!

[Kenn_eth @keenn_eth]

If you’re hunting for a remote job, you just need to figure out how Reddit works, and you’ll never be unemployed for a long time.

Here’s a list of subreddits you should bookmark right now:

[Neo Kim @systemdesignone]

Goldmine for Software Engineers! 📌

If you're learning System Design and/or AI Engineering, then bookmark this repo right now.

https://t.co/4SURKMITj0

[rari @0xwhrrari]

Google Brain founder Andrew Ng:

"Prompting will be dead in 6 months"

"Loops and graphs are replacing it"

In just 2 hours, he shows how to build agents that work, learn, and improve on their own

LLMs → Agents → Loops → Graphs → Self-Improving Systems

The first 15 minutes alone are more valuable than most $500 AI courses

Most people are still learning prompts while AI engineering is already moving beyond them

Watch the lecture first

Then read the full guide to loops and graphs below ↓

[Swapna Kumar Panda @swapnakpanda]

You will be a world-class backend engineer once you finish watching all these courses:

[Puneet Patwari @system_monarch]

I learned basic system design.
↓
Drew a client, server, and database.
↓
"Looks scalable enough."
↓
Added 1 million users to the question.
↓
Server died.
↓
Added another server.
↓
"Wait, how does traffic know where to go?"
↓
Learned load balancers.
↓
Database became the bottleneck.
↓
Added read replicas.
↓
Writes were still slow.
↓
Learned indexing.
↓
Added a cache because everyone kept saying "use Redis."
↓
"Wait, what happens when the cache is stale?"
↓
Learned cache invalidation.
↓
One service started taking 8 seconds.
↓
Added a message queue.
↓
"Wait, what if the message gets processed twice?"
↓
Learned idempotency.
↓
Users started uploading huge files.
↓
Stopped storing them in the database.
↓
Learned object storage and CDNs.
↓
One region went down.
↓
Learned replication and failover.
↓
Realized every new box creates another problem.
↓
Finally understood system design.

Jokes aside.

Beginner system design feels overwhelming because people throw around terms like sharding, Kafka, Redis, CDNs, queues, replicas, and microservices.

You do not need to memorize all of them.

Start with one simple system:

Client → Server → Database

Then keep asking: "What breaks if traffic becomes 10x?"

[Shubham Mishra 🐐 @shubh6200]

WhatsApp Status disappears after 24 hours.

2 billion users post daily.

You can’t run a cron job to delete them. It’ll kill the DB.

How would you design it?

[Alex Xu @alexxubyte]

What is MCP Really About clearly explained in 5 minutes

[Divyanshi @Divyyanshishrma]

this is f*cking gold

How to build your first AI agent (Full guide)

if I had this a year ago, I would've shipped my first agent in a day instead of 2 weeks in the right hands, this changes everything:

[Neo Kim @systemdesignone]

If you want to become GOAT-level with system design, then learn these 17 case studies (save now):

[Poonam @Aiwithpoonam]

If I were in my 30s or 40s right now and wanted to leverage AI to retire within 10 years, here's what I'd do:

1. Immediately form an LLC company. Not next month. Not once you're 'ready.' This week.

[Suraj Sharma @suraj_sharma14]

CANCEL your weekend plans.

You NEED to:

• Learn golden dataset design for regression testing AI systems
• Build 2-3 LLM-as-a-judge pipelines with bias calibration
• Set up grounding and citation quality metrics for RAG
• Learn adversarial evals for hallucination and jailbreak resistance
• Master cost-quality tradeoff analysis across model versions
• Build your own human eval framework that scales beyond one-off reviews
• Create automated eval gates in CI/CD for AI deployments
• Experiment with shadow deployments for output comparison
• Try DeepEval, RAGAS, TruLens for different eval dimensions
• Learn how to measure user trust in AI outputs quantitatively
• Build evals that detect drift in model behavior over time
• Run evals on competitor AI products to benchmark your own
• Learn to communicate eval results to non-technical stakeholders
• Use LangSmith/LangFuse for eval tracking and visualization
• Build one public eval report comparing models or architectures
• Read eval research instead of model release announcements
• Start sharing your eval methodology and findings publicly
• Learn how evaluation actually drives product decisions in AI teams

You have way too much to do.

@suraj_sharma14
#AIEvaluation #LLMOps #ReliableAI #July2026

[Khairallah AL-Awady @eng_khairallah1]

Anthropic engineer:

"You're not supposed to prompt Claude. You're supposed to build a system that prompts itself."

In 45 minutes she shows exactly how to build an agent that improves itself.

Most people are still doing all of this by hand.

Watch the session, then save the guide below.

[Ankit @thelostphoton]

Being an Indian, now I understand why we have been slaves for centuries.

#mandir #rammandir #corruption

[Rahul @sairahul1]

Anthropic just paid millions to hire Andrej Karpathy.

He gave you the same knowledge for $0 the same week.

Co-founder of OpenAI. Former head of AI at Tesla. The man who coined vibe coding.

No recruitment fee. No exclusive access. Just a link and 29 minutes.

LLMs are ghosts not animals.
Vibe coding is dead.
Software 3.0 is here.

Watch it.

Then read this.

Because Karpathy tells you what Software 3.0 is.

This shows you how to build one - a software factory with Claude Code that ships features while you sleep.

The full build guide is below.

[Movez @0xMovez]

Anthropic pays $750,000+ a year for engineers who can build LLM architectures from scratch.

This 2-hour Stanford lecture gives you the exact pipeline LLM engineers get paid $750K/year for.

Data + architecture + scaling laws + post-training.

Bookmark it & watch today. Then read article below.

[Vaibhav Sisinty @VaibhavSisinty]

Man there's some insane stuff sitting on GitHub for free right now

Spent the week going through 30+ repos

These 7 are the ones I keep coming back to 🧵

[Khairallah AL-Awady @eng_khairallah1]

🚨 Anthropic's own team just showed how to actually use Claude Code properly.

30 minutes. free. the person who created Claude Code.

watch the workshop. bookmark it.

worth more than every $500 course you almost bought.

you've been using Claude without knowing 40 of its commands.

Then read the guide below.

[SumitM @SumitM_X]

As a backend engineer.

Please learn:

- SOLID design principles
- Multithreading
- Immutability
- Streaming , messaging
- Caching
- Security - SSL, JWT, OAuth
- factory, decorator, singleton, obeservable design patterns
- TDD

All very important topics .