Blog
Guides et explications
Articles de fond sur les profils GitHub, les CV qui survivent aux systèmes de suivi des candidatures, et la façon de lire le travail public d’un développeur sans en tirer de mauvaises conclusions.
-
#github#portfolio#how-to
How to write a README for a portfolio project that a hiring manager will actually read
A project README written for a reviewer, not a user: what to put in the first screen, a section-by-section template with a worked example, the GitHub mechanics that quietly break READMEs, and how to check yours in five minutes.
-
#github#career#how-to
The 90-day GitHub profile audit for your job search
A week-by-week plan for auditing and fixing your GitHub profile in the months before you start applying, so the profile a reviewer eventually opens works in your favour instead of against you.
-
#resume#career#ats#github
The developer resume checklist: everything to check before applying
A single, practical checklist covering structure, content, GitHub, and ATS formatting for a software engineering resume, with a link to a deeper guide for every item.
-
#github#resume#career
How to turn an open-source contribution into a resume entry
Merged pull requests, issue triage, and documentation work all count differently on a resume. A practical guide to writing about open-source contributions with evidence a reviewer can check.
-
#resume#projects#github#career
GitHub projects vs. work experience: what should developers highlight?
When a personal project and a job both demonstrate the same skill, which one should lead on a resume? A practical framework rather than a fixed rule.
-
#resume#career#students
Software engineer resume for freshers: a complete guide
A full structure for a first software engineering resume: education, projects, GitHub, internships, skills, and how to handle every section when you have little or no paid experience.
-
#resume#projects#career
How many projects should a developer put on a resume?
The right number of projects for a resume depends on experience level and how much work history you already have. A practical breakdown for freshers, junior developers, and experienced engineers.
-
#github#career#how-to
How to make your GitHub profile look professional before applying for jobs
A cleanup checklist for a GitHub profile: pinned repositories, repository names, descriptions, stale forks, and the small details a technical reviewer notices first.
-
#github#resume#projects#career
How to describe GitHub projects on a resume, with before and after examples
Real before-and-after rewrites showing the difference between a project description that lists technology and one that reads as evidence of real engineering work.
-
#github#resume#career
How to put GitHub on your resume: a complete guide
Where your GitHub URL belongs on a resume, what recruiters actually look for when they click it, and how to make sure the profile backs up what the resume claims.
-
#resume#career#ats#github
The complete developer resume guide
A single, comprehensive walkthrough of every part of a software engineering resume: structure, summary, experience, projects, skills, education, GitHub, ATS formatting, and the mistakes that undercut otherwise strong resumes.
-
#resume#career#skills
Frontend vs backend developer resume: what actually changes
The structure of a developer resume stays the same across specializations. What changes is which evidence you lead with. A practical comparison for frontend, backend, and full-stack applicants.
-
#resume#career#how-to
How to quantify engineering achievements on a resume
Most resume bullets claim impact without evidence. A practical method for finding real numbers in your work, even when you never tracked them at the time.
-
#resume#career#students
How to write a developer resume with no professional experience
A structure for a first software engineering resume when you have no job history to draw on, built around coursework, personal projects, and GitHub activity instead.
-
#github#resume#projects#career
How to choose which GitHub projects belong on your resume
Not every repository deserves a spot on your resume. A practical filter for narrowing a full GitHub profile down to the handful of projects worth listing.
-
#resume#projects#career
How to build the projects section of a developer resume
Which projects belong on a software engineering resume, how to order them, and how to write a project entry that reads as evidence rather than a link dump.
-
#github#career#hiring
Do recruiters actually check your GitHub?
Who actually looks at a candidate's GitHub profile during hiring, what they look for when they do, and what a profile needs to hold up to that kind of scrutiny.
-
#github#copilot#contributions#explainer
Does using GitHub Copilot show up on your profile?
Whether AI-assisted commits are marked differently on GitHub, what actually appears on your contribution graph, and what that means if you use Copilot regularly.
-
#resume#ats#career
The complete guide to getting your resume past an ATS
How applicant tracking systems actually parse a resume, the specific formatting choices that break that parsing, and a full checklist to test your own resume against.
-
#github#how-to#beginner
Forking vs. cloning a GitHub repository
The practical difference between forking and cloning on GitHub, when to use each one, and how to actually do both from the command line.
-
#resume#career#how-to
Resume format: chronological, functional, or combination?
The three standard resume formats explained, which one fits which situation, and why the chronological format is the safest default for most applicants.
-
#resume#career#students
How to make a resume for your first job
How to build a credible resume with little or no formal work history, using education, projects and volunteer work to fill the space experience would otherwise take.
-
#github#explainer
Is GitHub free?
What GitHub actually gives you for free, where the paid tiers start to matter, and why most individual developers never need to pay for it.
-
#resume#career#how-to
What is a cover letter, and do you still need one?
What a cover letter is for, when it actually gets read, and how to write one that adds something a resume cannot say on its own.
-
#career#github#how-to
Adding your resume and GitHub profile to LinkedIn
Where to actually upload a resume PDF on LinkedIn, how to link your GitHub profile properly, and why the two should say the same thing.
-
#resume#career#github
Why people exaggerate on resumes, and the case for verifiable work
Why resume exaggeration happens, why it usually gets caught, and why evidence a reviewer can check directly is a stronger position than any claim, true or not.
-
#resume#career#how-to
What is a resume summary, and do you need one?
What a resume summary is for, how it differs from an objective statement, and a simple structure for writing one that actually earns its place at the top of the page.
-
#github#explainer#career
What is GitHub Actions?
What GitHub Actions does, how a workflow file actually works, and whether CI/CD experience built with it is worth mentioning on a resume.
-
#github#students#career
The GitHub Student Developer Pack, explained
What the GitHub Student Developer Pack actually includes, who qualifies, and how to turn a semester of using it into a resume that shows real, verifiable work.
-
#github#explainer
Who owns GitHub?
GitHub has been owned by Microsoft since 2018. How much independence it kept, what changed after the deal, and whether any of it affects your repositories.
-
#github#github-pages#resume#how-to
Hosting your resume or portfolio on GitHub Pages
How GitHub Pages works, what it is actually good for, and where it stops being the right tool once you need a resume that recruiters can search and parse.
-
#resume#ai#github#career
AI resume builders vs. building yours from GitHub
What AI resume builders actually generate, where that content comes from, and why a resume built from real repository data is a different, more verifiable kind of shortcut.
-
#resume#career
How long should a resume be?
The actual reasoning behind the one-page guideline, when two pages is genuinely correct, and why cutting length is usually an editing problem rather than a formatting one.
-
#resume#career#how-to
What to put on a resume, section by section
A section-by-section breakdown of what belongs on a resume, what commonly gets included but should not, and how the answer changes based on how much experience you have.
-
#resume#skills#career
What skills to put on a resume, and how many
How to choose which skills belong on a technical resume, why a shorter list usually reads as stronger, and how to group them so a recruiter can scan them in seconds.
-
#resume#templates#ats
Free resume templates worth using (and how to check one first)
What separates a genuinely useful free resume template from one that will get mangled by an applicant tracking system, plus a quick test you can run on any template before committing to it.
-
#resume#career#ats
How to make a resume stand out (without gimmicks)
What actually catches a reviewer's attention in the ten seconds they give a resume, and why most of the tactics people call "standing out" backfire in an ATS.
-
#resume#career#how-to
How to write a resume, step by step
A practical order of operations for writing a resume from nothing: what to gather first, how to structure each section, and the most common mistakes to check for before sending it.
-
#cv#resume#career#explainer
CV vs. resume: what's the difference?
How CVs and resumes actually differ in length, content and purpose, and why the right answer depends on your country and industry rather than a fixed rule.
-
#cv#career#explainer
What is a CV?
What a CV is, how the term is used differently in the US versus the UK and Europe, and when an academic CV genuinely needs to run longer than one page.
-
#resume#career#explainer
What is a resume?
What a resume actually is, what it is for, and the small set of things every version has in common regardless of format or industry.
-
#github#explainer#beginner
How to use GitHub: a beginner's walkthrough
The handful of things you actually need to know to start using GitHub: creating a repository, making your first commit, and the difference between a commit and a push.
-
#github#explainer#beginner
What is GitHub, actually?
A plain explanation of what GitHub is, what Git has to do with it, and why so many job applications now ask for a profile link instead of a portfolio PDF.
-
#github#contributions#explainer
How the GitHub contribution graph actually works
What counts as a contribution, what does not, why your graph looks emptier than your year felt, and how to read someone else’s graph without drawing the wrong conclusions.
-
#github#profile#career
How to write a GitHub profile README that is actually worth reading
A practical guide to the special profile repository: what to put in it, what to leave out, and why most profile READMEs fail the ten-second test.
-
#resume#ats#career
Jake's Resume template, explained
Why the most-recommended LaTeX resume template for engineers works so well, what each section is doing, and how to keep its advantages if you are not using LaTeX.