Skip to content

Instantly share code, notes, and snippets.

@bjf5201

bjf5201/normalize-portfolio.md

Last active March 3, 2025 19:51
Show Gist options
  • Save bjf5201/b60a8512d95513e6410d2b95ad78075a to your computer and use it in GitHub Desktop.
Save bjf5201/b60a8512d95513e6410d2b95ad78075a to your computer and use it in GitHub Desktop.
Download ZIP
Normalize Professional Digital Portfolio
Raw
normalize-portfolio.md

Process for Normalizing Professional Digital Portfolio

(aka ensuring your Professional Brand is consistent)

Overview

A software engineer's portfolio contains not only their central portfolio (usually a website), but a plethora of artifacts across the internet which demonstrate their abilities and provide credibility to the claims made on their central portfolio.

A SWE portfolio is essentially a central location to display all aspects of one's personal brand.

Personally, my portfolio website contains tons of dynamic information. The dynamic nature of this information, combined with my lil ADHD brain, can lead to mistakes and inconsistencies when publishing/deploying.

To remedy this, here is an index which collects all the various portfolio artifacts which exists as well as an outline of "acceptance tests" for each artifact.

Artifact Index

  • Portfolio website
    • Projects listed on website
    • Resume
    • Personal Info ("About" sections, contact info, location, etc.)
  • Blog Posts
    • Posts on personal website
    • Posts on external sites
      • HackerNoon
      • Medium
      • daily.dev
      • LinkedIn
      • StackOverflow
      • etc.
  • External Profiles
    • LinkedIn
    • GitHub/GitLab/Gitea
    • CodePen
    • Behance
    • etc.
  • Other Social Media
    • Mastodon
    • BlueSky

Portfolio Website

Projects

Projects listed on the portfolio website MUST:

  • contain a brief description
  • include information on what Languages/Stacks they utilize.
  • link to the repo associated with them (or a project video if this is not possible)
  • link to a DEMO (hosted on GH pages, netlify, or vercel) if a web app
  • link to a DEMO IMPLEMENTATION (in source code either in seperate repo or on CodePen) if a package/library/framework.

Projects are ENCOURAGED TO:

  • include a line that discusses what skills the project demonstrates proficiency in.
  • include an overview of the project and display any planning or design documents which are not located in the source code
  • include an animated GIF or short video which shows the project in action

Resume

The resume listed on the website SHOULD:

  • always be up to date
  • be in-sync with the information listed on LinkedIn (doesn't have to match exactly)
  • include an option to download the resume in PDF or CSV format.

Personal Info

Personal info on the website SHOULD:

  • always be up to date
  • be consistent with information listed on other public profiles such as LinkedIn

Blog Posts

Publish blog posts on central website first, and then distribute the posts to external publishers.

External Profiles

LinkedIn

Your LinkedIn profile SHOULD:

  • have an up-to-date tagline
  • be consistent with info on central website and GitHub

Your LinkedIn profile is ENCOURAGED TO:

  • highlight current projects you are working on
  • gather more references from those you've worked with

GitHub

Your GH profile SHOULD:

  • contain an engaging, up-to-date README.md
  • have your best projects pinned to your profile (no tutorials, forks of templates, etc.)
  • be consistent with info on other external profiles
  • include project READMEs in every project. Especially the pinned ones!

CodePen

Your CodePen profile SHOULD:

  • "showcase" the projects you are most proud of
  • be linked to your GH profile somewhere

Other Social Media

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment