How to Create a Skill Bar: The Definitive Guide
Description
A screenshot of a webpage or article providing a satirical tutorial on creating skill bars for developer portfolios. The image displays two progress bars: one for 'JavaScript' at 65% in red, and one for 'PHP' at 60% in grey. Below these is a green button that reads 'Try it Yourself »'. The main content consists of a title, 'How To Create a Skill Bar', followed by the first and only step: 'Step 1) Stop immediately. Abandon any desire to create a skill bar. What the fuck is 90% PHP anyway?'. The humor is derived from its direct opposition to the tutorial format, critiquing the widespread and often meaningless use of skill bars to quantify programming proficiency. This resonates with experienced developers who find such metrics to be arbitrary and a poor representation of actual skill, as highlighted by the rhetorical question about the meaning of '90% PHP'
Comments
7Comment deleted
The only thing a 90% skill bar truly communicates is a 100% chance you're underestimating the complexity of the language and overestimating the patience of the hiring manager
Résumé skill bars are Monte Carlo simulations without confidence intervals: 65 % JavaScript, 60 % PHP, and a 100 % chance the hiring panel asks what the denominator was
I've seen candidates claim they're "90% JavaScript" but can't explain event loop behavior, meanwhile the guy who wrote V8 probably rates himself at 60% on a good day
Ah yes, the classic skill bar - because nothing says 'hire me' like claiming you've mastered exactly 65% of JavaScript's prototypal inheritance quirks, 60% of PHP's inconsistent function naming conventions, and somehow stopped learning both languages at precisely those arbitrary thresholds. The real skill here is confidently quantifying the fundamentally unquantifiable, which ironically demonstrates 0% understanding of the Dunning-Kruger effect
Skill bars are the résumé version of claiming p95 latency by measuring p50: “90% PHP” - cool, what’s the confidence interval, and does Composer live in the missing 10%?
90% PHP skill: You've refactored more WordPress plugins than features, yet still can't escape the callback hell of procedural legacy
When I see “90% PHP” on a portfolio, I assume the other 10% is headers already sent - because skill isn’t scalar; it’s a probability distribution with very wide confidence intervals