Resumes are a great way to show off your skills, but with the amount of competition out there and the preferences of hiring managers, you might have options that are more efficient.
The Resume Is Dead. Long Live The Resume: a blog about github pages and code spaces.
Ever since I was young, I’ve been passionate about learning new things. I would say I’m an expert at learning, as it is something that comes naturally to me. I have always been curious about the world around me and have never stopped trying to learn.
I started out by teaching myself HTML and CSS when I was 8 years old and have been building websites ever since. My first breakthrough came when my parents decided to buy me a computer with internet access (I had been using their computers for some time).
Before that, I remember spending hours on coding websites in Notepad. And by coding, I mean typing random letters and numbers until something happened on screen (usually nothing good). It took me several hours to figure out how to just make a simple webpage display correctly, but eventually it all clicked.
“The Resume Is Dead. Long Live The Resume” is a blog about github pages and codespaces that I wrote for the project. My writing instructor gave me this title as an assignment. I’m not sure if it’s a good title, but I enjoyed writing the piece.
The Resume Is Dead. Long Live The Resume.
How to publish a website with GitHub Pages and Codespaces: A Tutorial by John Doe
For a long time, the resume was “the” thing you needed to get a job. You had to compose the best resume possible, with your most impressive skills and experiences listed in a way that would make you stand out from the crowd. Now, it seems things are changing again, and employers are looking for something new in job candidates: digital skill sets.
This article is going to explain how to build a website using Github Pages and Codespaces. At the end of this tutorial, you’ll have your own professional looking portfolio site—and you’ll have acquired a new skill set that employers will be impressed with!
The resume is dead. Long live the resume.
If you’re a job seeker, you’ve probably been advised to have a resume handy at all times. While this may still be true, it’s also true that recruiters are increasingly looking at other sources of information about candidates and their work. This means that candidates need to be ready to tell their stories in new ways, in a variety of formats.
It’s not enough to just have a resume on hand these days. The prospect of the traditional “paper resume” has become an outdated relic for many job seekers, but the act of summarizing your background, skills, and experience remains important.
As our reliance on technology and data increases in both personal and professional life, so too does our reliance on technology and data during the hiring process. In fact, with over three million open job listings on LinkedIn alone at any given time, recruiters are turning to technology to help source and screen candidates more efficiently than ever before.
Today’s job seeker should embrace this shift towards digital resumes as a way to differentiate themselves from other candidates by showcasing their skills through interactive tools like GitHub Pages and Code Spaces. Digital resumes provide an added bonus for employers — allowing them
The modern resume is a living, breathing showcase of a person’s skills and experience. It should be updated whenever you acquire new experience that’s relevant to what you’re doing right now.
To keep your resume updated, you need to keep track of your accomplishments throughout the year. I use a private git repo to track my accomplishments, but you could also do it in Evernote, Google Docs, Dropbox Paper, or an old-fashioned notebook. At the end of each month, I review the past month’s accomplishments and add them to my resume.
I’ve been doing this for several years now. I get a lot of job offers because of it. But it can be expensive if you want to host your resume on github pages (the cost is about $4/month). To solve this problem I used codespaces; a brand new feature from github that lets you run a web server from within github itself (no need to pay for hosting). This costs $5/month and comes with 1GB RAM and unlimited storage space!
Now when someone wants to check out my resume, all they have to do is click “open with codespaces”:
[Open with Codespaces](https://github.com/jbee/resume-april
CodeSpaces is a new way to code and GitHub Pages is a powerful platform for static websites. Whether you’re new to web development or new to CodeSpaces, we’ve got you covered.
CodeSpaces is a cloud-based development environment that lets you write, run, and debug your code with just a browser. It was designed from the ground up with GitHub Pages in mind.
You can find more information on CodeSpaces [here](https://github.com/features/codespaces)
Lately, I’ve been thinking a lot about resumes. Specifically, how I feel like I need a brand new one. The thing is, I haven’t changed jobs in about a year. But what I do day-to-day has changed a lot. Heck, even my title has changed!
My job title used to be “Software Engineer”. It was pretty darn accurate. My work involved writing code for software that interfaced with hardware that was in the sky. That was my primary role and it was what I spent most of my time doing each week.
Nowadays, my job title is “Senior Software Engineer”. It’s less accurate but at least it’s higher on the totem pole in terms of status and compensation. These days, most of my time is spent managing a team of people who write code for software that interfaces with hardware that is in the sky.
I still write code (though not as much as I used to), but it’s not the core focus of my job anymore. Nowadays, the core focus of my job is managing other people… getting them to work together effectively toward common goals… helping them grow their careers… mentoring them through tough technical and non-technical challenges… helping them plan for their future… etc etc
Every year, thousands of programmers send me their resume. And every year, I have to tell most of them, “I’m sorry, I can’t hire you.”
The reason is that they’re not good enough at programming. Usually they know a programming language, but not well enough to write a program that other people would use. They’ve never written a program that other people could use and they don’t seem likely to start. And the problem is so widespread I think it’s time we recognized it as a community-wide defect.
What’s weird is that these people are not stupid. Some of them have Ph.D.’s in mathematics; some have won international math competitions. Many of them are smart enough to get into MIT or Caltech or Harvard or Stanford; some of them are smart enough to be teaching there. (And no, it’s not just because “everyone’s doing it”– the fraction of resumes I get from non-programmers is low and stable.)
So what happened?
I think the problem is this: these days it’s too easy for kids to do well on tests without really learning how to do anything useful. So they think they’re good at problem solving, and they’re not.
So here’s my