Deepak Verma

50 JavaScript projects(with code) that will take you from zero to hero in 50 days. A Mega Thread 🧵

REST is not about fancy APIs. It’s about clear intent through conventions. Learn more at: youtu.be/uFGJVQvR59A?si…

REST helps you: ✅ Avoid endpoint explosion ✅ Make APIs predictable ✅ Reduce cognitive load ✅ Scale teams better

Lecture 3 🧵 Today I learned the real meaning of REST. It’s not about endpoints — it’s about intent and semantics.

@lingodotdev Loved it😂😂

At least the API works now 😂

@va_a14 😲

Amazon  pays around 65+ LPA, and 85+ LPA CTC for more than 3+ years of experience to a software engineer 𝗥𝗼𝘂𝗻𝗱 1 – 𝗣𝗿𝗼𝗯𝗹𝗲𝗺 𝗦𝗼𝗹𝘃𝗶𝗻𝗴 Leadership Principles (LP): 30 minutes of deep-dive behavioral questions. Question 1: Given a manager-employee tree, find how many new managers are formed if a current manager goes on leave (immediate reportees become managers). Solved for both Binary Tree and N-ary Tree Question 2: Longest Consecutive Sequence. 𝗥𝗼𝘂𝗻𝗱 2 – 𝗕𝗮𝗿 𝗥𝗮𝗶𝘀𝗲𝗿 Focus: 40 minutes of in-depth LP and current project architecture discussion. DSA Question: Find median in a data stream (presented as a real-world scenario). Expectation: Detailed explanation of logic and data structure trade-offs (Heaps). 𝗥𝗼𝘂𝗻𝗱 3 – 𝗟𝗼𝘄-𝗟𝗲𝘃𝗲𝗹 𝗗𝗲𝘀𝗶𝗴𝗻 (𝗟𝗟𝗗) Task: Design a Finance Application. Discussion: Requirements gathering, API design, class diagrams, and handling evolving business constraints. Focus: Translation of business requirements into extensible code structures and HLD components. 𝗥𝗼𝘂𝗻𝗱 4 – 𝗛𝗶𝗴𝗵-𝗟𝗲𝘃𝗲𝗹 𝗗𝗲𝘀𝗶𝗴𝗻 (𝗛𝗟𝗗) & 𝗛𝗶𝗿𝗶𝗻𝗴 𝗠𝗮𝗻𝗮𝗴𝗲𝗿 LP Discussion: 20 minutes of grilling on ownership and delivering results. System Design: Design Spotify. Deep Dive: Specific focus on playlist management and song queueing logic. Focus: Scalability, availability, and alignment with the team’s specific domain.

@geeksforgeeks Yesss, me typing this in metro towards office🥷

The first 4 days were trial. Real 2026 begins from today 😎

@arpit_bhayani @RoyDevelops 😂😂😂

@RoyDevelops Bhai. Mai reply bhi karne wala tha 😅 it was typed but then app crashed!

You can never explain what happened to me after I saw this

@akshaymarch7 Me after reading this

The fastest way to grow as an engineer is… boring. No shortcuts. No secret roadmap. No magic framework. Just work hard every day and do the same hard things again and again. Reading docs which feels boring. Fixing bugs that are pending since long. Refactoring ugly code. Learning something new even when your brain is tired. Most people quit here. Not because it’s hard. Because it’s boring. This industry moves fast. Really fast. If you stop learning for even a few months, you start falling behind. New tools. New patterns. New expectations. You always have to stay on your toes. Growth in tech doesn’t come from one big break. It comes from small, invisible efforts done daily. Consistency beats talent. Discipline beats motivation. There were many days I felt stuck. Many days nothing exciting happened. But those boring days are the reason I’m here today. So if your journey feels slow right now, if nothing dramatic is happening… Don’t panic. This is exactly how it’s supposed to be. As we say, “Boond boond se sagar banta hai.” Cheers, Akshay Saini 🚀 PS. Save this. Read it again when growth feels too slow.

@ATechAjay @grok please suggest a tidy layout

Help me to tidy up my cluttered workspace 😓

@arpit_bhayani Learning hard while it’s still fun. That’s the plan.

Everything eventually becomes boring, so make the most of it while it still holds your interest.

System design isn’t about tools or fancy diagrams. It’s about clear thinking before building. Day 2 done.

This mindset fits both approaches: 🔁 Spiral (requirement-driven) 🚀 Incremental MVP (growth-driven) Different paths, same rule: simple first, complexity later.

Day 2 — #AsliEngineer 🧵 Today I learned how to approach a system design problem — before drawing boxes or choosing tech. The biggest lesson? Fence the problem before you build anything.