Jagabandhu Malik

Snitch, one of India’s fastest-growing menswear brands, has stepped into the quick delivery market with Snitch Quick, a new service that delivers clothes to customers within 60 minutes in Bengaluru. Announcing the launch on social media, Snitch wrote, “Bangalore traffic can slow down anything – except Snitch. Introducing Snitch Quick: 60-minute delivery across most Bangalore pincodes. Your weekend plans, dates, and last-minute parties just got saved.” The new service gives customers access to over 1,000 clothing options, including shirts, t-shirts, jeans, and more, all available for fast delivery. By offering 60-minute delivery, Snitch aims to bring the comfort of quick commerce to fashion, letting customers shop for outfits even at the last moment. Currently, Snitch Quick is live in Bengaluru, and the company plans to take it to other cities soon. The service runs through local delivery centers that help make the one-hour delivery possible without delays. Founded in 2020 by Siddharth Dungarwal, Snitch has built a strong following among Gen Z and millennial men through its website, mobile app, and stores. The brand is known for releasing new styles frequently and keeping up with current fashion trends. Earlier this year, Snitch raised ₹340 crore in funding at a ₹2,500 crore valuation. The round included investors such as 360 ONE Asset, IvyCap Ventures, SWC Global, and the Ravi Modi Family Office, along with several angel investors. The funding supports Snitch’s plans to expand its store presence and improve logistics. With Snitch Quick, the brand is now moving beyond regular online shopping — making fast, on-demand fashion a reality for Bengaluru customers. If successful, this service could mark the start of faster, smarter shopping for men across India. #SnitchQuick #madhurai #Menswear #BangaloreFashion #QuickDelivery #FastFashion #MensFashion #60MinuteDelivery #BangaloreLife #Snitch #SnitchMen #MensOutfits #

143

𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗹𝗲𝗮𝗱𝗲𝗿𝘀𝗵𝗶𝗽 𝗼𝗳𝘁𝗲𝗻 𝗳𝗲𝗲𝗹𝘀 𝗹𝗶𝗸𝗲 𝘄𝗮𝗹𝗸𝗶𝗻𝗴 𝗮 𝘁𝗶𝗴𝗵𝘁𝗿𝗼𝗽𝗲. Think of it like debates in sports commentary—everyone has a different take on what makes a good captain. Similarly, leaders face numerous opinions about whether they are too hands-on or too distant. 𝘛𝘩𝘦 𝘳𝘦𝘢𝘭𝘪𝘵𝘺 𝘪𝘴, 𝘵𝘩𝘦𝘳𝘦’𝘴 𝘯𝘰 𝘴𝘪𝘯𝘨𝘭𝘦 𝘧𝘰𝘳𝘮𝘶𝘭𝘢. 𝘞𝘩𝘢𝘵 𝘢𝘱𝘱𝘦𝘢𝘳𝘴 𝘵𝘰 𝘣𝘦 𝘮𝘪𝘤𝘳𝘰𝘮𝘢𝘯𝘢𝘨𝘦𝘮𝘦𝘯𝘵 𝘪𝘯 𝘰𝘯𝘦 𝘤𝘰𝘯𝘵𝘦𝘹𝘵 𝘮𝘢𝘺 𝘧𝘦𝘦𝘭 𝘭𝘪𝘬𝘦 𝘮𝘶𝘤𝘩-𝘯𝘦𝘦𝘥𝘦𝘥 𝘴𝘶𝘱𝘱𝘰𝘳𝘵 𝘪𝘯 𝘢𝘯𝘰𝘵𝘩𝘦𝘳. 𝘞𝘩𝘢𝘵 𝘧𝘦𝘦𝘭𝘴 𝘭𝘪𝘬𝘦 𝘩𝘦𝘢𝘭𝘵𝘩𝘺 𝘥𝘦𝘭𝘦𝘨𝘢𝘵𝘪𝘰𝘯 𝘪𝘯 𝘰𝘯𝘦 𝘵𝘦𝘢𝘮 𝘮𝘢𝘺 𝘤𝘰𝘮𝘦 𝘢𝘤𝘳𝘰𝘴𝘴 𝘢𝘴 𝘥𝘦𝘵𝘢𝘤𝘩𝘮𝘦𝘯𝘵 𝘦𝘭𝘴𝘦𝘸𝘩𝘦𝘳𝘦. At the same time, leaders often hear conflicting voices: some question the value of managers altogether, comparing them to engineers who “build.” In contrast, others emphasise the need for leaders who orchestrate the bigger picture. Seasoned engineering leadership lies in cutting through this noise and finding balance—anchored in the culture of the organisation you are leading. So how do you build the cultural awareness that makes this balance possible? 𝟭. 𝗢𝗯𝘀𝗲𝗿𝘃𝗲 𝘁𝗵𝗲 𝗢𝗿𝗴𝗮𝗻𝗶𝘀𝗮𝘁𝗶𝗼𝗻 One of the most valuable lessons I learned from a mentor was to observe first, act later. Ask yourself:  • What is the vision of this organisation?  • Why are certain strategic choices being made?  • Who are the real stakeholders?  • Where do teams succeed, and where do they stumble? Careful observation gives you a map before you start moving. 𝟮. 𝗟𝗶𝘀𝘁𝗲𝗻 𝗮𝗻𝗱 𝗟𝗲𝗮𝗿��� Observation is powerful, but listening deepens the picture. Conversations with peers, leaders, and mentors uncover nuances you won’t find in strategy decks. Each person you speak with is a living “manual” of organisational culture. Listening—really listening—adds clarity and prevents you from leading in isolation. 𝟯. 𝗕𝘂𝗶𝗹𝗱 𝗥𝗲𝗹𝗮𝘁𝗶𝗼𝗻𝘀𝗵𝗶𝗽𝘀 At the heart of every organisation are relationships. Beyond systems, architecture, and execution, what people remember is: Who stood by me when I needed support? Trust built in those moments outlasts most technical wins. Strong relationships give leaders both influence and resilience. 𝟰. 𝗔𝗰𝗸𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 𝗮𝗻𝗱 𝗖𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲 𝗕𝗶𝗮𝘀 Every leader carries biases—towards people, ideas, or even ways of working. Cultural awareness starts by recognising those biases, then actively checking them. When leaders are honest about their blind spots, they make better, fairer decisions. 𝗚𝗿𝗲𝗮𝘁 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗹𝗲𝗮𝗱𝗲𝗿𝘀 𝗱𝗼𝗻’𝘁 𝗷𝘂𝘀𝘁 𝗺𝗮𝗻𝗮𝗴𝗲—𝘁𝗵𝗲𝘆 𝗹𝗶𝘀𝘁𝗲𝗻, 𝗮𝗱𝗮𝗽𝘁, 𝗮𝗻𝗱 𝗯𝘂𝗶𝗹𝗱 𝘁𝗿𝘂𝘀𝘁. What do you think? #EngineeringLeadership #CulturalIntelligence #TechLeadership #OrganizationalCulture #FutureOfWork #Leadership

22

Frontend system design part - 13 Question: How to show where you left ? on streaming platforms like youtube, netflix etc. Explanation: Easiest way to implement it is by making an api call periodically to save the video id and watched duration aginst the user id. But his can be optimised further on client by catching the time stamp. Periodically, save the timestamp locally first, followed by saving it on server. Next time when user opens the video make an api call first and wait for the result to get the updated timestamp. If it is delayed then use the local timestamp for faster experience. When you used the local timestamp do not update the server with latest watched timesmap. what do you think ? do you have a better solution for this ? Follow me and I will help you to find your dream job: Vasanth Bhat

54

6 Comments

“Made In…” — But Where, Really? Here’s something most people don’t know: A garment can be completely stitched, embroidered, finished, and pressed in India… …and still be labelled “Made in Italy,” “Made in France,” or “Made in UAE” — with just a minor final touch done offshore. A buttonhole. A brand label. A final steam press. That’s all it takes. 📦 Under WTO rules and trade agreements, the country of origin can be declared based on where the “last substantial transformation” happens. But what qualifies as “substantial” is often ambiguous—and easily exploited. 💡 Industry Insight: Many global luxury and high street brands outsource 80–90% of the product’s construction to India, Bangladesh, Vietnam, or Cambodia. Yet, the final QC, packaging, or even a barcode printing done in Europe allows the product to wear the ‘Made in’ badge of a country where the actual makers never lived or worked. 🌏 Why does this matter? 1. It erases craftsmanship. Indian artisans, tailors, and karigars remain invisible in the value chain. 2. It misleads consumers. “Made in Italy” suggests Italian heritage, quality, and local manufacturing—when in reality, that identity was stitched together in India. 3. It suppresses fair pricing. If the consumer knew it was made in India using premium techniques, would they not be more willing to pay what it’s truly worth? And would we not invest more in building Indian textile infrastructure and pride? As someone deeply involved in sourcing, I see this every day. And while we can’t change global trade laws overnight, we can demand better transparency in labeling and storytelling. ✅ Let’s advocate for: • Co-origin labeling (e.g., “Crafted in India, Finished in Italy”) • More brand accountability • Consumer awareness around origin and value Because behind every “Made In” tag, there is a human story that deserves to be told. Would love to hear from others in the industry: Have you seen this in your supply chain too? #MadeInIndia #EthicalFashion #TransparencyInFashion #TextileHeritage #FashionSourcing #BrandAccountability #SupplyChainTruths #SlowFashion

174

42 Comments

Very Interesting perspectives, I may disagree with a few and align with Many of the views shared, interesting views, perspectives, and practices nevertheless !! 1. The Counterintuitive Truth: Code Quality Does Not Equal Product Success Prasanna’s most striking lesson for engineers is that there is no direct relationship between high code quality and building a successful product. While technical excellence is a worthy goal, it is not the end goal. The ultimate measure of success is whether you are solving a real problem for people. < I am on the Edge with this one. While I am a strong proponent of Quality output/outcome, the ultimate measure of success is, however, the real problem solved :) Ramanan Natarajan - Would love to hear your thoughts on this :) 2. The Real Productivity Engine: Structure as the Foundation for Tools While Block is gaining attention for its powerful internal AI agent, Goose, Prasanna reveals that the single most impactful change for boosting productivity wasn't a tool, but a fundamental organizational restructure. The company shifted from a siloed structure to a unified, functional one. This new functional structure unlocked three primary benefits: > It created a singular focus on technology and technical excellence across the entire organization. > It allowed leaders to drive forward AI and platform depth for the whole company, rather than in isolated pockets. > It changed the hiring mindset. Instead of treating engineers as a "commodity" to be added to a business unit to increase feature output, "mythical man month", the focus shifted to building common platforms and leveraging deep experts across the entire organization. This unified structure not only drove technical depth but also created the ideal environment for small-scale experiments to be identified, supported, and scaled across the company, rather than dying within a business unit silo. < It's not always the Tool, it's the Mindset !! 3. The Principle of Momentum: Start Small to Win Big: The most successful and durable innovations rarely begin as massive, top-down corporate initiatives. Instead, they grow from small, focused experiments. < "Start small with everything." 4. The Human Element: Hire for a "Learning Mindset": The company now optimizes for a "learning mindset." They are less concerned with finding "amazing AI practitioners on the get-go." Instead, they prioritize finding people from recent college graduates to industry veterans who are eager, open to learning, and willing to embrace new tools. < Meta cognition is undervalued !! #organisationCluture #AI #Productivity https://lnkd.in/gw6saKXp

11

🔧 System Design isn’t just about code — it’s about engineering thinking. Thinking of cracking that FAANG interview or designing systems that actually scale? Then you need more than Leetcode. You need architecture intuition. 📘 I recently came across “System Design for FAANG” by Ravi Tandon — and it’s one of the most well-structured, realistic, and practically useful guides out there. Here’s what makes it a must-read: ➡️ Breaks down what FAANG really looks for in system design interviews ➡️ Covers trade-offs like CAP theorem, latency vs consistency, and vertical vs horizontal scaling ➡️ Explains key components — Load Balancers, CDNs, caching layers, sharding, queues, and more ➡️ Real-world use cases — think URL shorteners, rate limiters, notification engines, and more ➡️ Whether you're: Aiming for FAANG Moving into Senior/Architect roles Or just curious how scalable systems really work... This guide helps you think like a systems engineer — not just a coder. 💡 It's not theory. It's insight + real-world application. 👇 Drop a like if you want more such reads in your feed! #SystemDesign #FAANG #ScalableSystems #SoftwareArchitecture #EngineeringMindset #CareerGrowth #TechLeadership

156

12 Comments

About 25-30 years back, buying gold jewellery in India was about blind trust. You believed the jeweller when they said it was 22kt. You had no easy way to know otherwise, until the karatmeter arrived. Suddenly, purity was visible. Measurable. Objective. The industry changed and became much more transparent, much more organized. Today, I see the same story playing out in ethnic wear. Many sarees marketed as “pure silk/cotton” actually contain synthetics. They look identical. And most buyers aren’t fabric experts to recognize by touch. It’s only a matter of time before authenticity becomes transparent here too. And when that happens, technology won’t just protect customers, but it’ll also reward the artisans who stay true to their craft, giving authenticity the value it deserves.

92

10 Comments

Is CDN a reverse proxy, just like a load balancer or an API gateway? Yes. While LB and API gateway fit the classic definition of a Reverse Proxy, CDN is also a reverse proxy with caching as its primary purpose. Like any other reverse proxy, 1. CDN acts as a single point of entry for client requests, 2. CDN abstracts out different origins configured behind it 3. CDN can also route the requests across multiple origins depending on the route-matching configuration. Hence, the deduction is on point, and LB, API Gateway, and CDN are all examples of Reverse Proxies. I elaborated on CDN, as it is an unconventional example. ps: I love how the comments on my YouTube videos are also no-fluff and filled with thought-provoking questions. Thank you for asking such great questions. By the way, the question was asked in my recent video on Forward and Reverse Proxy. In the video, I went into highly practical details with real-world examples and stories from my life. give it a watch and subscribe - youtu.be/HrG0MHkSsCA btw, enrollments open for sys design June cohort, about 30 seats left - arpitbhayani.me/course

324

8 Comments

🎯 Frontend Development Skills for Product-Based Companies 🔥 Ready to stand out in top tech teams? Join Ng Delhi Community: https://lnkd.in/gZfR9exS ✅ A well-structured roadmap is your best friend if you’re aiming to become a high-performing frontend developer. 📌 𝗕𝗮𝘀𝗶𝗰 𝗝𝗮𝘃𝗮𝗦𝗰𝗿𝗶𝗽𝘁 𝗖𝗼𝗻𝗰𝗲𝗽𝘁𝘀 • Data types • Functions • Scope • Closures • Event loop • Prototype & prototype chain • Classes & inheritance • DOM manipulation • bind / call / apply • Promises • Web APIs • Task queue & call stack • Async/await • Generators • TypeScript 📌 𝗕𝗮𝘀𝗶𝗰 𝗛𝗧𝗠𝗟 𝗖𝗼𝗻𝗰𝗲𝗽𝘁𝘀 • Block vs Inline elements • Semantic HTML • Imports and includes • Forms & accessibility • Infinite questions, infinite possibilities! 📌 𝗕𝗮𝘀𝗶𝗰 𝗖𝗦𝗦 𝗖𝗼𝗻𝗰𝗲𝗽𝘁𝘀 • Selectors (Class, ID, Universal) • Pseudo Classes & Elements • Box Model • Display types: flex, grid, block • Centering techniques • Element states: active, hover, focus • Media queries • Preprocessors: SCSS/LESS • Mixins, variables, constants • BEM naming convention • Importing styles 📌 𝗕𝗮𝘀𝗶𝗰 𝗪𝗲𝗯 𝗖𝗼𝗻𝗰𝗲𝗽𝘁𝘀 • Page rendering lifecycle • HTTP, HTTPS, HTTP/2 • CORS • LocalStorage / SessionStorage • Cookies • JWT • XMLHttpRequest • Micro Frontends • REST / GraphQL / WebSocket • Browser internals • Debugging techniques • Chrome DevTools mastery 📌 𝗔𝗱𝘃𝗮𝗻𝗰𝗲𝗱 𝗝𝗮𝘃𝗮𝗦𝗰𝗿𝗶𝗽𝘁 • OOP principles • Design Patterns: ▸ Singleton, Provider, Prototype ▸ Observer, Module, HOC • V8 Engine insights: ▸ JIT, Interpreter, Execution • Currying 📌 𝗕𝗮𝘀𝗶𝗰 𝗥𝗲𝗮𝗰𝘁𝗝𝗦 (𝗕𝗼𝗻𝘂𝘀) • JSX • Components (Functional & Class) • State, Props, Hooks • Lifecycle methods • Virtual DOM • Context API • Redux / Flux • Routing • Testing with Jest & RTL • Webpack, Babel, ESLint, Prettier 📌 𝗕𝗮𝘀𝗶𝗰 𝗔𝗻𝗴𝘂𝗹𝗮𝗿 (𝗕𝗼𝗻𝘂𝘀) • Angular architecture & modules • Components, Directives, Pipes • Services & Dependency Injection • Lifecycle Hooks • Routing & Lazy Loading • Template vs Reactive Forms • RxJS & Observables • Change Detection Strategies • Angular Signals (latest) • State Management (NgRx / Signals) • Testing with Jasmine & Karma • Angular CLI, Environment configs • SSR with Angular Universal • Angular Material & CDK Like, save, and share if this helped you! Enjoy learning — one topic at a time! #frontend #javascript #html #css #webdevelopment #reactjs #angular #typescript #roadmap #developers #ngdelhi #codingjourney #techskills

110

5 Comments

𝗔𝗰𝗵𝗶𝗲𝘃𝗶𝗻𝗴 𝗙𝗶𝗻𝗮𝗻𝗰𝗶𝗮𝗹 𝗜𝗻𝗱𝗲𝗽𝗲𝗻𝗱𝗲𝗻𝗰𝗲: 𝗪𝗵𝘆 𝗜𝘁 𝗠𝗮𝘁𝘁𝗲𝗿𝘀 𝗳𝗼𝗿 𝗬𝗼𝘂𝗿 𝗖𝗮𝗿𝗲𝗲𝗿 𝗮𝗻𝗱 𝗟𝗶𝗳𝗲 As I reflect on my journey to building a net worth of ₹4 crore, I'm reminded of the importance of financial independence, especially in the Indian IT industry. Did you know that the likelihood of replacement increases once you hit 40 in the IT sector? This stark reality highlights the need to prioritize our financial future. 𝗪𝗵𝘆 𝗙𝗶𝗻𝗮𝗻𝗰𝗶𝗮𝗹 𝗜𝗻𝗱𝗲𝗽𝗲𝗻𝗱𝗲𝗻𝗰𝗲 𝗠𝗮𝘁𝘁𝗲𝗿𝘀: - 𝗙𝗿𝗲𝗲𝗱𝗼𝗺 𝘁𝗼 𝗖𝗵𝗼𝗼𝘀𝗲: Financial independence gives you the liberty to pursue your passions without being tied to a single paycheck. - 𝗥𝗲𝗱𝘂𝗰𝗲𝗱 𝗦𝘁𝗿𝗲𝘀𝘀: Having a financial cushion reduces stress and anxiety related to job security and unexpected expenses. - 𝗜𝗻𝗰𝗿𝗲𝗮𝘀𝗲𝗱 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆: Financial independence provides a safety net during economic downturns or industry shifts. 𝗠𝘆 𝗝𝗼𝘂𝗿𝗻𝗲𝘆: Reaching a net worth of ₹4 crore wasn't easy, but it was worth it. Through smart investments, disciplined saving, and strategic planning, I've been able to achieve financial stability and freedom. 𝗛𝗼𝘄 𝘁𝗼 𝗔𝗰𝗵𝗶𝗲𝘃𝗲 𝗙𝗶𝗻𝗮𝗻𝗰𝗶𝗮𝗹 𝗜𝗻𝗱𝗲𝗽𝗲𝗻𝗱𝗲𝗻𝗰𝗲: - 𝗦𝘁𝗮𝗿𝘁 𝗘𝗮𝗿𝗹𝘆: Begin investing as soon as possible to harness the power of compounding. - 𝗗𝗶𝘃𝗲𝗿𝘀𝗶𝗳𝘆: Spread your investments across different asset classes to minimize risk. - 𝗦𝗮𝘃𝗲 𝗪𝗶𝘀𝗲𝗹𝘆: Live below your means and save consistently. - 𝗜𝗻𝘃𝗲𝘀𝘁 𝗶𝗻 𝗬𝗼𝘂𝗿𝘀𝗲𝗹𝗳: Continuously develop new skills to stay relevant in the industry. 𝗧𝗮𝗸𝗲 𝗖𝗼𝗻𝘁𝗿𝗼𝗹 𝗼𝗳 𝗬𝗼𝘂𝗿 𝗙𝗶𝗻𝗮𝗻𝗰𝗶𝗮𝗹 𝗙𝘂𝘁𝘂𝗿𝗲 Don't wait until it's too late. Start building your financial independence today. Invest wisely, save consistently, and plan for your future. Remember, financial independence is not just about retiring early; it's about living life on your own terms. 𝗟𝗲𝘁'𝘀 𝗗𝗶𝘀𝗰𝘂𝘀𝘀: Share your thoughts on financial independence and investments in the comments below. How do you plan to secure your financial future? #financialindependence

19