It's tempting to pad a resume with every technology ever touched — a weekend tutorial in one framework, a half-finished side project in another, a language explored for a single assignment that never went further. On paper it looks impressive: fifteen logos, fifteen bullet points, a wall of proficiency suggesting someone who can handle anything thrown at them. But experienced hiring managers can usually tell the difference between a name on a list and a tool someone has actually debugged at 2 a.m. under real user load, and the tell is almost always in the follow-up questions. Ask about the tenth item on that list and the answers get vague fast; ask about the third item, the one actually used to ship something real, and the story changes entirely — a specific bug, a specific limitation nobody warned them about, a specific decision that turned out to be wrong and had to be unwound later. That specificity is what separates a genuinely useful hire from an impressively long list of buzzwords nobody's going to ask about twice.