Not a vibe coder | Backend Systems | GenAI Building, breaking & understanding systems
Joined January 2025
- Tweets177
- Following55
- Followers12
- Likes9.8K
Pinned Tweet
videos : youtube.com/@CSwithMIK
sheet : takeuforward.org/dsa/striver…
u will never ever regret this goated combination
dev ✪ retweeted
I wish someone had given me this 8-week System Design plan before my first interview:
> Week 1: Basics
- System Design Primer on GitHub
- latency numbers, scaling, CAP
→ done: explain load balancer vs reverse proxy
> Week 2: Storage
- SQL vs NoSQL, indexes, replication, sharding
→ done: pick a DB for a chat app and defend it
> Week 3: Caching + queues
- cache aside, write through, TTLs
- message queues and back pressure
→ done: design a URL shortener end to end
> Week 4: Theory
- Martin Kleppmann's 8 Cambridge lectures, free on YouTube
→ done: explain why you can't trust clocks across machines
> Week 5-6: Build it
- MIT 6.5840 distributed systems labs, free online, in Go
- start with MapReduce, then Raft
→ done: your MapReduce passes the lab tests
> Week 7: Real systems
- AWS Builders' Library, start with timeouts and retries
- Google's SRE books, free to read online
→ done: write 1 page on how retries can take a system down
> Week 8: Mock rounds
- design WhatsApp, YouTube, a rate limiter
- 45 min each, talk out loud
→ done: requirements, estimates, API, data model, scale, in that order
I'd do 1 hour a day
Open the primer tonight and start Week 1
dev ✪ retweeted
Are vibe coders even aware of these 50 things?
Database Indexes
Race Conditions
API Rate Limiting
Database Transactions
Cache Stampedes
Connection Pooling
Dead Letter Queues
ACID Properties
Webhook Verification
Distributed Tracing
N+1 Queries
Circuit Breakers
Database Sharding
Optimistic Locking
Exponential Backoff
Zero-Downtime Migrations
Message Queues
Isolation Levels
Idempotency
Load Balancing
Query Optimization
Graceful Shutdown
Redis Eviction Policies
Foreign Key Constraints
Replication Lag
Background Workers
Deadlocks
Eventual Consistency
Read Replicas
Retry Mechanisms
Database Migrations
Backpressure
Pessimistic Locking
Horizontal vs Vertical Scaling
Webhook Retries
EXPLAIN ANALYZE
Distributed Caching
Unique Constraints
Outbox Pattern
Health Checks
Database Partitioning
Job Scheduling
Reverse Proxies
Distributed Transactions
Cache Invalidation
Event-Driven Architecture
Jitter
CQRS
Event Sourcing
Circuit Breaker Recovery Strategies
Building a working demo is one thing.
Building a system that survives real users, failures, traffic spikes, and messy data is a completely different game.
dev ✪ retweeted
System Design Interview: Design an AI Agent Platform
Problem: Build a platform where AI agents execute multi-step tasks using tools and LLMs.
Requirements:
- Support thousands of concurrent agents.
- Maintain conversation and task state.
- Handle retries and tool failures.
- Execute tasks asynchronously.
- Track token usage and costs.
Challenge:
How would you prevent duplicate tool executions when an agent retries after a timeout?
dev ✪ retweeted
WHO'S GONNA TELL VIBE CODERS ABOUT...
1. Idempotency Keys
2. Rate Limiting
3. Reverse Proxies
4. Connection Pooling
5. N+1 Queries
6. Caching Strategies
7. Cache Invalidation
8. Load Balancing
9. API Gateways
10. Timeouts
11. Retries
12. Exponential Backoff
13. Circuit Breakers
14. Race Conditions
15. Deadlocks
16. Memory Leaks
17. Webhooks
18. CORS
19. Secrets Management
dev ✪ retweeted
System design in 15 lines (save now):
High global latency → use a CDN
Slow database reads → add a cache
Sudden write spikes → add a queue
Distributed transactions → use Saga
Need ACID transactions → use SQL
Flexible data models → consider NoSQL
SQL database too large → shard the DB
Growing server load → scale out
High traffic → add a load balancer
Critical service failures → add redundancy
Need data durability → use replication
Too many requests → add throttling
Unpredictable traffic spikes → enable autoscaling
Realtime updates → use WebSockets
Retries causing duplicates → use idempotency keys
Start here...The rest is just details.
dev ✪ retweeted
As a Frontend Developer,
Please slap yourself if you cannot clearly explain at least 10 of the following :
Hydration
Partial hydration
Islands architecture
Streaming SSR
Concurrent rendering
Time slicing
Reconciliation algorithm
Fiber architecture
Virtual DOM diffing complexity
Structural sharing
Immutable data patterns
Referential equality
Memoization pitfalls
Stale closure problem
Event loop (macro vs microtasks)
Task starvation
Layout thrashing
Critical rendering path
Render blocking resources
Tree shaking internals
Code splitting strategies
Dynamic import chunking
Module federation
Shadow DOM
Custom Elements lifecycle
Web Components interoperability
Web Workers vs Service Workers
SharedArrayBuffer
Transferable objects
OffscreenCanvas
WebAssembly integration
Browser compositing layers
Paint vs composite vs layout
GPU acceleration in CSS
CSS containment
Subpixel rendering
IntersectionObserver internals
ResizeObserver loop limits
MutationObserver cost
IndexedDB
Service Worker lifecycle traps
Cache invalidation strategies
Stale-while-revalidate
ETag vs Cache-Control
HTTP/3 and QUIC
Priority hints
Preload vs Prefetch vs Preconnect
CORS preflight
SameSite cookie modes
CSRF vs XSS mitigation
Content Security Policy (CSP)
DOM clobbering
Prototype pollution
Race conditions in UI state
Tearing in concurrent UI
Render waterfalls
Suspense boundaries
Selective hydration
Server components
Edge rendering
Micro-frontend orchestration
Finite state modeling
Event sourcing in frontend
Optimistic UI rollback strategy
Offline conflict resolution
CRDT basics for collaboration
WebRTC
Backpressure in streams API
AbortController
Streaming fetch response handling
Browser memory leak detection
Detached DOM nodes
Garbage collection timing
PerformanceObserver API
Long tasks API
First Input Delay (FID)
Interaction to Next Paint (INP)
Cumulative Layout Shift (CLS)
Largest Contentful Paint (LCP)
Speculative prerendering
Priority inversion in async code
Deterministic rendering
dev ✪ retweeted
System Design essentials:
1. Scalability
2. Load Balancing
3. Microservices
4. Caching
5. Databases
6. Message Queues
7. Partitioning
8. CDN
9. Rate Limiting
10. CAP Theorem
11. Stream Processing
12. Object Storage
Master these to design scalable systems.
#AI #Systemdesign #ML
dev ✪ retweeted
50 essential AI concepts everyone should know:
1/ Tokens
2/ Context window
3/ Embeddings
4/ Attention
5/ Transformers
6/ Temperature
7/ Top-p / sampling
8/ System prompt
9/ Few-shot prompting
10/ Chain of thought
11/ Structured output
12/ Function / tool calling
13/ Agents
14/ Multi-agent systems
15/ MCP
16/ RAG
17/ Vector databases
18/ Hybrid search
19/ Chunking
20/ Reranking
21/ Hallucination
22/ Grounding
23/ Evals
24/ Golden datasets
25/ LLM-as-judge
26/ Fine-tuning
27/ LoRA
28/ RLHF
29/ DPO
30/ Distillation
31/ Speculative decoding
32/ KV cache
33/ Latency
34/ Cost per task
35/ Semantic caching
36/ Model routing
37/ Guardrails
38/ Prompt injection
39/ Jailbreaks
40/ PII redaction
41/ Sandboxing tools
42/ Human-in-the-loop
43/ Observability / tracing
44/ Streaming (SSE)
45/ Multimodal
46/ Computer use
47/ Memory (short + long term)
48/ State machines for agents
49/ Fallbacks + retries
50/ Shipping to real users
If you can explain all 50 in plain English, you're ahead of most "AI experts."
PS. It's funny how few of them are just jargons
dev ✪ retweeted
As a backend engineer.
Please learn:
- System Design (scalability, microservices)
-APIs (REST, GraphQL, gRPC)
-Database Systems (SQL, NoSQL)
-Distributed Systems (consistency, replication)
-Caching (Redis, Memcached)
-Security (OAuth2, JWT, encryption)
-DevOps (CI/CD, Docker, Kubernetes)
-Performance Optimization (profiling, load balancing)
-Cloud Services (AWS, GCP, Azure)
-Monitoring (Prometheus, Grafana)
Pick up a language..
Stop jumping from one language to the other
dev ✪ retweeted
Ashneer Grover has No Filter. 🔥🔥
He just tore apart the “doglapan” of both, Godi Media and the Government in a single clip. 🗿🦁💀
dev ✪ retweeted
Cheating is so prevalent in online assessments now that students from all colleges, IITs, NITs, Tier-3 are doing it equally.
The sad part is even if you don't want to, you have to cheat if others are doing it as the game is rigged.
Not sure how to combat this though
dev ✪ retweeted
Cheating in an OA for a company - man, do whatever it takes for you to clear placement exams. I don't care. I am not here to moral police anyone, I know better than most that the world is a grey place.
Nothing is completely right or wrong, and there's nuance to it. But if you have successfully gamed the system - SHUT YOUR BITCH-ASS THE FUCK UP!!!!!!
That's all you had to do, but nope. VIT Pune and even some PICT Pune kids HAD to, just HAD to brag about it all on sub-reddits, even making guides for others to follow along.
Now I'mma sit back, and watch it all get as messy as it can be for all of y'all. I got no stake in the game, I am done and dusted with "Placements" long, long ago.
Cheat or don't, I DO NOT GIVE A FLYING FUCK ABOUT IT. But come bragging about it on a public app, and I do indeed care about that.
Cheers!
dev ✪ retweeted
Winter Arc starts tomorrow.
You’re unable to view this Post because this account owner limits who can view their Posts. Learn more
