Your GitHub Profile

How to set up a GitHub profile that actually shows what you can do. Even if you’re not a developer, GitHub can showcase your scripts, configs, and technical knowledge. We’ll show you how to make it work as your portfolio.
Categories:
Tags:

  4 minute read  

You’ve probably heard of GitHub. You may even have an account. But if you started in IT before DevOps was a word, it may not be totally clear why GitHub matters to you.

Let’s change that. Here’s a quick-and-dirty primer on what GitHub is, why it exists, and how to make your profile work for you, and not just sit there gathering dust. Also see: How Could Non-Developers Benefit From Using Git.

What Is Git?

Git is a version control system. Think of it like a save button, but smarter. It tracks every change you make to your code or config files, lets you roll back if something breaks, and helps you collaborate without stepping on each other’s toes.

It was created in 2005 by Linus Torvalds - the same guy who created Linux - because the version control tools at the time were not-good, and he wanted something fast, distributed, and flexible.

The idea is, you go and make whatever changes you need to make within a specific folder, that is your “repository”, or “repo” for short. Git keeps track of every single change in that folder. When you’re ready you create a “commit” of those changes. That is a snapshot of your work at that point in time. You can go back to that commit later if you need to.

See our Git Cheatsheet for a quick reference on common Git commands.

What Is GitHub?

GitHub is a website (owned by Microsoft) that makes Git easier to use and share. It adds collaboration tools like pull requests, issues, project boards, GitHub Actions, etc.. Most importantly for our purposes, it gives you a public profile and a place to showcase your work.

Even if you’re not a developer, you might still:

  • Write scripts
  • Manage Infrastructure as Code (IaC) with tools like Ansible, Terraform, or Pulumi.
  • Build security tooling and scripts
  • Write README files or deployment docs

All of that can live on GitHub.

Why Should I Care?

This is part of your public brand.

When someone Googles you (a recruiter, a collaborator, a potential client), your GitHub profile might be the first legit-looking thing that pops up. A clean, intentional profile shows that:

  • You’re active in your field
  • You document and share your work
  • You’re comfortable with modern workflows

It’s not about followers or stars, it’s about signaling that you’re still in the game. It’s a form of professional credibility or social proof.

Don’t worry if you don’t have public code to share

Even a small public repo with some Ansible playbooks or a README on how you do backups is more than most folks ever post.

Setting Up Your Profile

Here’s what we recommend for a solid setup.

1. Your GitHub Profile README

GitHub lets you create a special README file that shows up at the top of your profile.

To do this:

  1. Create a new repository with the exact same name as your GitHub username
  2. Check the box to “Add a README”
  3. Whatever you write in that README will be front and center

What should go in there?

  • A short intro (“Hey, I’m ITbyJohnD, sysadmin, and security tinkerer.”)
  • Link to your itbyjohnd.com brand site
  • Link to your LinkedIn
  • What you’re currently working on (personal projects, open source stuff, blog series)
  • How to reach out if they want to collaborate
Sample README Outline
## 👋 Hi, I’m ITbyJohnD

I’m a long-time sysadmin turned full-stack security engineer. These days I’m 
building [BuildMoreThanCode.com](https://buildmorethancode.com) and tinkering 
with open source SaaS apps.

- 💼 [LinkedIn](https://www.linkedin.com/in/itbyjohnd)
- ✍️ [Blog](https://itbyjohnd.com)
- 📫 best way to reach me: [email protected]

2. Pin Repos That Represent You

You can “pin” repositories on your profile, these are the ones that show up first. Pick 3–6 that reflect your skills and interests.

Some good candidates:

  • Your homelab automation repo
  • A Dockerized security tool you wrote or maintain
  • A writeup on how you do patch management or backups
  • A personal project you’re quietly proud of

3. Tidy Up Your Contributions

Even if you mostly work in private repos, try to have at least something public. You don’t need to build a whole framework. Just:

  • Share your dotfiles
  • Post a script you’ve cleaned up
  • Write a walkthrough of your homelab architecture
GitHub is about signal, not noise

One well-commented repo is better than ten half-baked ideas. This is your chance to showcase the quality of your thinking.

Summary

You don’t need to be a full-time coder to make GitHub work for you.

It’s a free tool that can:

  • Show your work
  • Anchor your online presence
  • Help people understand your skills, even if you never talk to them

Start with a basic profile README, pin a few repos, and link out to your brand site and LinkedIn. That’s it. That’s the baseline.

Anything above that is gravy.