Mudit Choudhary

My Competitor of @hashnode is deployed and live here: bashnode.onrender.com 😁 Jokes aside I wanted to learn React, node, and how to make full-stack applications. I like #hashnode & took inspiration from them & built a clone of it to learn them while building it.

how to be a cracked backend engineer 👇

Doubt yourself every day. Imposter Syndrome is real and essential. We keep looking for resources to overcome it, but to be honest, there is no real need. I let it hit hard, as it, pushes me to learn more, dig deeper, and explore concepts I would have otherwise overlooked. But here's the critical part - this self-doubt should not erode your confidence as too much of it can devastate you completely, so you need to maintain a balance. So, every time you solve a problem, fix a bug, or implement a feature, take a moment to acknowledge it and reward yourself. Remember, even most senior engineers face challenges that they are not equipped to handle. But, the difference is, they use their self-doubt as a push toward new learning opportunities. Did I ever feel like an impostor in my career? yes; do I feel it today? absolutely. There were moments when I felt like an imposter and thought it was way over my head. But that feeling pushed me to learn more, work harder, and dig deeper. Remember, the goal isn't to eliminate self-doubt but to leverage it to identify growth areas. But, don't let it define you. I keep writing and sharing my practical experience and learnings every day, so if you resonate then follow along. I keep it no fluff. #AsliEngineering #CareerGrowth

🥳🎉 I'm thrilled to announce that I have finally started looking for a job and spending 6 months of freelancing and experimenting with different fields. I promised myself to keep experimenting and have an open mind and look for all opportunities that I haven't....

How To Write Cold Emails or DMs. 🧵

Optimisation in ReactJS: A very important thread for those who are beginners in frontend dev. Before that we need to understand about component re-rendering. A component in React re-renders when: 1) Any state variable inside its component gets changed. Ex: const [state, setState] = useState(); If we call setState() to change the state then component re-renders to show u the current value. 2) If the state value of its props changes. Ex: function MyComponent({propsState}) { return <> } If propsState change anywhere then MyComponent re-renders. 3) If it's parent component re-renders. Ex: A has child B and B has child C then if A re-renders then B & C also re-renders. Optimisations: 1) You can see in the 3rd case of re-rendering, when children are not accepting any props from parent then it is unnecessary to re-render all children when parent re-renders. To prevent this unnecessary re-renders, you should wrap children inside React.memo. While exporting do this: "export default React.memo(MyComponent)" This will prevent re-rendering of 3rd condition. But still re-renders in 1st & 2nd condition which is required to reflect changes in UI. 2) Make use of the useMemo() hook. Suppose, u have a function that takes some argument and based on that it does a heavy calculation to get the result. If u don't use useMemo() then every time u call this function, it will get do calculation to give the result. Suppose function takes (a, b) as argument, u called this function for (2, 3), it does calculation, you called this function for same (2,3) again, it will do calculation again. If you use useMemo() then it will not run the whole function and do calculation for the same argument again. It will return the previous cached value. If u studied DSA, then it is the same as DP. It doesn't run the function if it has cached its value. 3) Make use of the useCallback() hook. When a component is re-rendered then whatever functions u wrote in it will be newly created and a new reference of that function will be attached. But if u wrap your function in usecallback() then the same function reference will be attached to the next renders and no new function will be created. It will do 2 optimisations: a) Save time of creating new function definitions on every re-render. b) Suppose this function is passed as props to any child component and if u don't use useCallback() then childComponent will re-render even after u wrap it in React.memo() because of 2nd rule of re-rendering (read above). Because propsState which has the function changed because a new function reference is created on parent re-rendering. But using useCallback() would prevent it and make use of the same reference of function in every render.

Win a ticket for #CityJSIndia - winner to be announced on Friday All you have to do - Repost #RT and Follow us! More info india.cityjsconf.org

❓How can I learn/upskill/prepare with a fulltime job? An "excuse" I hear often. Do you have a goal? (Getting that better paying job, switching fields, learning DSA etc?) If no, then learning is a hobby. Do it passively (but hopefully often enough) If YES, read on

The truth is, you’re likely not as good as you think. It’s hard to accept, and your ego resists it. But that quiet voice urging you to improve? It’s probably right.

Documentation is ENOUGH for most of your journey. It's English. It's straightforward. Don't look for easy tutorials all the time. They can be shallow and often WRONG! Things worth doing are often hard and boring. Learn to deal with it, instead of avoiding it.

The secret to getting better at building software is to first get exceptionally good at one language. It doesn’t matter if it’s C++, JavaScript, Go, Python, or Dart. Become exceptionally good at it. Explore the concepts of synchronous and asynchronous programming. Understand the intricacies of OOP and other programming patterns in that language. Once you do that, you’ll realize shifting stacks is a piece of cake. Most of the concepts are transferable. In fact, you’ll see how most advanced programming languages have more similarities than differences. You will no longer be haunted or limited by a particular tech stack. At that point, you’ll focus more on engineering rather than worrying about how to write code.

Power of “Focus and Discipline”. Problem1: Was a mathematics student in College. At 24, by job I was in a medical laboratory. So learning biology was must for professional “Dignity” Problem 2: Was a Tamilian. At 24, for job I was in Mumbai. So learning Hindi was must for personal “dignity” Bought books for both. Invested by focusing for 1000 days, consistently, daily 6 to 7 am for Biology and 9 to 10 pm for Hindi. Anything, be it a language, subject, game or art, an adult can learn with 1000 hrs of “focus and Discipline”. Do not get intimidated and give up courses or jobs or business or spouse too early. Success is when you do, what is difficult to do. Not what is easy to do.

Some have it better, some have it worse. Each person's journey is unique, shaped by different circumstances and challenges. So comparison is futile; acceptance is liberating.

@KeshuTechie 🚀🚀

Day 69 of my #100DaysOfCode :🚀 🔹completed my samll project [Shopping cart] 🔹Fetches and displays products from a remote API. 🔹Implements React Router for seamless navigation between pages. 🔹Context API for passing data between components. #WebDevelopment #Coding

❌ Don't get scared by what others can do. Don't compare yourself vs the entire internet as a whole. You know a tonne of things someone else will see and get anxious. It's not you vs the system. You are in the system. A LOT of people could kill to get to where you are.

@The_Sarvesh512 @DevDotCommunity Padhte chalo badhte chalo 🚀

#100_days_machine_learning_challenge with @DevDotCommunity. #Day_12 ✅😊

A🧵on ReactJS Internals. What is "rendering" in React? When does re-rendering happen? What is reconciliation and Virtual DOM etc? It will help to clear every frontend interview. Will post this thread in 3 parts. This is part 1. It will cover Rendering. Thread🧵 (1/8)

@KeshuTechie @TheOdinProject 🚀🚀

Day 62 of my #100DaysOfCode: Finally done with college exams! -Back to my full-stack course on The Odin Project. Completed Linked Lists and implemented my own HashMap. 🚀💻 #coding #learning @TheOdinProject

@tamalCodes Same, It's too small, 25 min to smjhane mai chala jate hai 😅. 60 | 10 min works fine for me.

No that work for 25 mins and take a break technique doesnot works for me.

Go beyond “How much package you earn” India has a huge population of developers. Tech brings in more money than most career options in India. But unfortunately tech education is not up to the mark and there is so much work to do here! If you’ve already made it into Tech and are now also a creator in Tech, it is your responsibility to help the upcoming developers from India to think bigger. Dream bigger. And that’s not going to happen if you sell the young community dreams of “how much package I earn” and “a day in the life of a FAANG developer” Making good money is inevitable if you’re even decently good at what you do in Tech. We are responsible for creating “cheap labour for the west” instead of skilled developers and engineers. Sell logic. Sell Maths. Sell deep tech. Sell research. Sell networking skills. Sell negotiation skills. Breaks my heart when I see students and kids fall for such things. Indian students grow up in a scarcity mentality. I did too. It is our job to help them see the bigger picture. Once you have the skills, there is enough pie for everyone and collaboration will take you ahead. Not cheap competition. Let’s do better folks.

Good morning 5:30 am club 🌄