Naming Conventions in tech: A Deverel Storytelling Opportunity

There are only two hard things in Computer Science: cache invalidation and naming things.

• "Welcome to 'Name Another Variable, I Dare You' - the game show where the points don't matter and neither do your variable names (just kidding, they totally do) 🎮"

• "In a world where 'myString' and 'myInt' roam free, one developer dared to ask: 'What if we actually named things properly?' dramatic movie trailer voice 🎬"

• "Breaking News: Local developer spends 3 hours naming function, settles for 'processData()'. More at 11! 📰"

Names have power. In tech, they can make or break entire systems. Through Kevin Blanco's golden rules of storytelling, let's uncover why naming might be the most crucial skill you're not thinking about.

• WHY (Hook with the crisis): "March 22, 2016: Thousands of developers worldwide stared at their screens in horror. Facebook's build? Broken. Netflix? Down. Spotify? Crashed. The culprit? A tiny package named 'left-pad' that vanished from npm. All because someone didn't like how it was named. Seriously."

• HOW (The cascade of chaos): "Here's the wild part: this 11-line code package was buried so deep in everyone's dependencies that nobody even knew they were using it. Like that one sock that disappears in the laundry, except this sock took down half the internet. The npm registry looked like a Christmas tree of red error messages, and developers worldwide learned a brutal lesson about naming and dependency management."

• WHAT (The lesson & transformation): "Today, we name things differently. We think twice before calling a package 'left-pad' or a variable 'data2'. Because in tech, names aren't just labels – they're survival tools. Let me show you how one naming disaster changed how we build the internet."

The Resolution:

1. Name with intention, not convenience

2. Think about future impact

3. Consider your code's story

My follow up

WHY : The purpose isn't just about coding style, we learn that names aren't just labels but they're survival tools.

HOW : Think of names like hashtags for your code. #UserAuthenticationService tells a better story than #data2. Here's how we turn naming from an art into a science...

WHAT : Let's break down the exact process from 'data' to 'userData' to 'userAuthenticationService', and why each iteration makes your future self hate you less..." Because in tech, clarity isn't just about good practice – it's about preventing the next left-pad apocalypse.