One skill every Leader needs to Master


Hello Reader,

As an Engineering leader, you are going to get requests all the time. So you need to prioritize how you are going to manage that.

According to a study by McKinsey, leaders who set clear priorities for their teams see a 25% increase in overall productivity.

You might have to say ‘no’ to your direct team or product leaders or might have to say no to priorities.

In Leadership, saying no means 'not right now', but let's work together to figure out 'when.'

While setting priorities, Never say we can’t do this now, hoping they would go away but instead, share the priorities and your roadmap 🛣️ with them. Ask them how their work takes priority over your existing roadmap and work with them to build a mutual understanding.

I have attached a handy infographic for you to learn and reference when you will say no next.

How do you say 'No'

This infographic and part of the lesson is taken from the Developer to Leader course which is filled with fun lil graphics like these.

Developer to Leader is a course that equips you all the skills needed to become a Successful Engineering Leader even if you've never managed or led anyone before.

🔥 Actionable Tip: Schedule regular self-reflections or engage in peer coaching to evaluate your decision-making and identify areas for growth.

🧰 The Engineering Leader's Toolbox

P.S.

Over the next couple of weeks, you're going to hear more from me about the upcoming Black Friday sale for Developer to Leader course, if you'd rather not hear about it you can click here to opt out however I'd still recommend to check it out since I'll be sharing exclusive bonus content that will be super helpful.

Ankita Kulkarni

Join 9200+ subscribers reading by weekly personalized Newsletter that helps developers level up their skills through weekly Frontend and Leadership Snacks. You get a deep dive into a Tech topic, Actionable tips to excel in your career and a toolbox!

Read more from Ankita Kulkarni
A terminal interface displays commands for a tool called next-browser, designed for AI agents to analyze and monitor Next.js applications.

Hey Reader, This week, Next.js 16.2 gave AI agents something they never had "a browser". Your agent can now see your app, find the problem, and fix it without asking you. This along with GPT-5.4 mini & nano (2 small models), TanStack Start going 5x faster, why you should ban useEffect, and more. Let's dive in. 🍿 Our Weekly Snack: Your AI agent can finally see what your users see (Next.js 16.2 is here) Next.js 16.2 dropped yesterday (deep dive here) and it just gave AI agents a browser. It's...

next.js proxy

Hey Reader, Middleware got renamed to Proxy in Next.js 16. Same functionality. Better name. What is Proxy? Every request to your app has to go somewhere - a page, an API route, a file. Proxy gets to look at it first and decide what happens: send the user somewhere else, serve different content silently, or just let it through as-is. Think of it as a traffic controller 🚦 sitting in front of your routes. So, why you should stop putting auth in Proxy? It feels like the perfect place but it...

You’re Suspending the Wrong Component

Hey Reader, There are thousands of you going through Modern Full Stack Next.js Course so wanted to be grateful here for your support. Just as a thank you, there is something big dropping for you. It will only last 24 hours ⏰ so keep an eye out for my email next week. Let's dive in! PRESENTED BY CLERK Instead of your coding agent guessing how auth works, you can now install specialized Clerk knowledge directly into it. Introducing Clerk Skills One simple command $ npx skills add clerk/skills...