Pinned Tweet
Hey 👋
If you’re in
- Tech
- Web Development
- Software Engineering
- AI
Say Hello and let’s
connect and grow 🤝
Developers:
Which is one the best for Coding and Development?
- Claude code
- Codex
- Cursor
- Gemini Antigravity
The most dangerous AI coding workflow:
Prompt → Copy → Paste → Ship
The better workflow:
Understand → Prompt → Review → Test → Verify → Ship
Developers:
What's the correct HTTP response code for a POST request?
POST /api/v1/users
- 200 OK
- 201 Created
Developers:
Why in every form submit handler function, we use
e.preventDefault() ?
What's the reason?
Mostly, don't understand it very well.
System Design Interview question:
Your application must support horizontal scaling without sharing local session state.
Which architecture helps?
A) Stateless
B) Stateful
C) Monolithic
Interview Question:
A payment gateway latency jumps from 200ms to 8s, crashing downstream services.
How do you isolate this failure?
DSA Interview question:
In a doubly linked list, how many pointer fields does each node typically contain?
A) 1
B) 2
C) 3
D) Dependent on the size of data
Developers:
Can you solve below using arithmetic operations using your fav language?
And what would be the answer?
If AI can
• Read the entire codebase
• Write features
• Fix bugs
What becomes the most valuable skill?
A. Debugging
B. Product thinking
C. Communication
Developers
What's the main issue with this React component?
#JavaScript #Reactjs
Developers:
When this happen to you?
- when fixing a bug
- when solving a leetcode problem
Be honest 😁
Interview question
Which logging practice provides the greatest debugging value in multi-service environments?
A. Log correlation ID
B. Log memory usage
C. Log service name
The Most Underrated Debugging Tool as a developer you should know:
👉 Correlation ID
Imagine a user clicks "Place Order".
That request travels through:
Web App
↓
API Gateway
↓
Order Service
↓
Payment Service
↓
Notification Service
Without a Correlation ID:
❌ Logs are scattered.
❌ Troubleshooting is painful.
With a Correlation ID:
✅ Every service logs the same unique ID.
✅ One search shows the entire request journey.
✅ Faster debugging and root cause analysis.
Think of it as a tracking number for your application requests.
Tip:
Generate it once, propagate it everywhere, and log it in every service.
Good logs tell you what happened. Correlation IDs tell you the complete story.









