Chapter 2: Naming Conventions That Scale скачать в хорошем качестве

Chapter 2: Naming Conventions That Scale

💭 Most React code doesn’t fail because of logic. It fails because no one can understand it six months later. In this chapter, we break down the naming conventions used by senior and top 1% React engineers — so your code explains itself without comments or guesswork. 🎯 What You’ll Learn 🔹 Common Naming Mistakes Overuse of abbreviations Vague or generic names Single-letter variables that hide intent 🔹 Why “Clever” Names Fail Short-term brilliance, long-term confusion How clever naming hurts maintainability and onboarding 🔹 Aggressively Obvious Naming The principle behind readable, self-explanatory code Making intent clear at a glance 🔹 React-Specific Naming Conventions Teams rely on consistent patterns like: handle for internal event handlers on for external callbacks use for custom hooks fetch for API calls get for derived values set for state setters 🔹 Comments vs Naming When comments genuinely help When comments are a red flag for bad naming 🚀 Why This Chapter Matters If your code needs explaining, the naming is already broken. This chapter shows you how to fix the names instead of adding comments. 🧪 Practice Along 📂 All React exercises & refactoring tasks from this webinar: 👉 https://github.com/CW-Codewalnut 🎙️ Instructor This session was led by Ben Sheridan-Edwards 👨‍💻 CTO & AI Engineering Lead at CodeWalnut 🔗 Connect with Ben on LinkedIn: 👉   / bensheridanedwards   🌰 Learn More with CodeWalnut We help developers: ✅ Write clean, readable & maintainable React code ✅ Understand architecture, abstractions & trade-offs ✅ Refactor confidently instead of rewriting everything ✅ Think like senior & top 1% engineers, not a tutorial follower 👉 Learn how we help engineers level up: https://www.codewalnut.com/ 🙌 Before You Go 👍 Like the video 💬 Comment your biggest naming mistake or key takeaway 🔔 Subscribe for more deep-dive React engineering sessions #React #CleanCode #NamingConventions #CodeWalnut