It was a smashing success with some 46k visitors. Yay!
But let's talk about how fuzzy the data was. Especially the job title part. Like, people just don't care enough to spell O.o
A visa application is no joke, right? It's an official document, that's going to be read by government employees. It's the kind of thing where submitting a week before the deadline is late.
And your document is judged. Harshly. People hire lawyers just to make sure all their paperwork is in order. That the t's are crossed and the i's are dotted.
You wouldn't expect spelling mistakes to make it through, right?
I found many spellings for
engineer. Everything from the correct
engineer to the silly
eingineeerr. But most got the first three letters right. The normalization regex is just
Well ... maybe counting on the first three letters is pushing it.
The more troubling fact is that people haven't mastered spaces very well. Or my scraping script hasn't. But a large part of the data assumes
engineer is a grammatical prefix (or suffix) to whatever your real job entails.
I saw everything from
But let's give people some credit, engineer is a pretty darn difficult word to spell. It's practically latin throws the usual English phonetics out the door.
developer though ... Here's the regex I had to use:
Yeah ... I don't even know. Like, seriously, I just don't know. How?
development, both of which are good, to the silly
And once more, a bunch of datapoints using it as a prefix ... maybe that's my bad though. Surely it's my bad. Surely it just means
.split() isn't the best word tokenizer.
Perhaps most interesting fact, though, is that the 81,122 visas in my dataset include 3,558 different job titles. Counting misspellings.
3,558 different job titles. Job titles I normalized to just 11 categories.
That's a hell of a lot of ways to say "person creating business value by getting computers to do stuff". No matter which way you cut it.
PS: if you take away rejected visas, there are only 3,472 job titles left. I wonder how many vanished due to spelling.
I write articles with real insight into the career and skills of a modern software engineer. "Raw and honest from the heart!" as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.
Subscribe below 👇
Join Swizec's Newsletter and get insightful emails 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
"Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️