multiple cool motion graphics

Last week, I posted a simple statement on LinkedIn that I wrote in under two minutes saying that marketers who wanna be hirable in a year from now should probably have a GitHub account.

I didn't think this was gonna blow up this much.

It got about 1,400 likes and hundreds of people commenting that they agreed or disagreed.

The day after posting this, my GitHub account got suspended, so all I can think is that angry people reported me, whether it was devs, whether it was marketers who didn't wanna accept this.

I think they were reporting me, the irony of this story we'll see in a second, is that I recovered the account within an hour or so thanks to networking.

The reason I posted this is because I work in tech, and our team has currently fully embraced AI to the point where all of us are shipping to our product.

So no non-engineers are left out when it comes to building our product.

And I know from first-hand experience that hiring managers and hiring teams at tech companies and tech startups are prioritizing people who are embracing AI.

They're not prioritizing the people that are demonizing AI.

Of course, they're looking for people that are using it to build apps, skills, ship code that's useful, not people who are using it to write slop on LinkedIn.

In this video, I wanna get into how you can set up your GitHub account as a marketer and why this doesn't have to be bad news.

It's literally something that takes 10 minutes, and of course, is not a proxy to years of experience and years of practice in your field.

It's just an external-facing indication of how much you're actually building, which I think very few marketers are embracing at the moment and I think is still an opportunity for you to invest in.

So we're gonna go over some of the rebuttals, and then we're gonna go over the actual setup of your GitHub account, At least your profile or homepage.

my credentials is that I have about 120 followers on GitHub, which I have been told is pretty good.

No, I'm just kidding.

I've been shipping stuff with AI since January of 2026, which isn't even that long.

It's just been a few months.

And some of the skills, like this one that lets you turn long-form content into short-form social clips is almost at 500 stars.

So please bear with me, because none of this is hard, and you can do it too.

Before we dive into the setup, I want to address whatever emotion you may be feeling at the thought of having to become an engineer, 'Cause that's the number one counterargument I got to my post, which is, "Stop turning marketers into engineers." Now, in 2026, becoming an engineer doesn't mean the same thing as it did just a few years ago.

For instance, you barely code yourself.

our entire dev team probably hasn't written a line of code themselves in months, thanks to Claude Code and Codex.

So, I would say whatever you're thinking of an, as an engineer or whatever you grew up thinking of as a software engineer is no longer really the definition.

Rather than engineer, I think you should think of yourself as a builder, someone who makes stuff that people want.

And whether you do that by making videos, by writing, by making websites, by making hardware, or by writing code using AI, that makes you a builder.

But basically, it's more about the mindset, which is very user-centric, knowing what people want, and knowing how to distribute and build at a pace that, you know, keeps up with, with tech startup pace.

that's kinda what hiring managers are looking for.

I wanna show you this video by, Marc Andreessen, who actually went on to talk about this idea of builders being what Silicon Valley at least is looking for.

I'm seeing in a bunch of the really leading edge companies in the Valley, which is they're, they're kind of circling around a job title sort loosely called builder, or, or something like it.

And, and basically the idea is that you had these separate jobs in the past of, programmer, product manager, and designer.

and I, I've been describing what's happening in the Valley companies as sort of this three-way Mexican standoff, where the programmers think that they can, they don't need the, the product managers and the designers anymore 'cause they can have AI do that.

And then e- each of the other two doesn't think they, they need the other two either.

and, and what I've been predicting is, they're all, they're all correct.

you know, the product manager can generate code and design now and, you know, so each of them can do the job of all three.

and so the idea is, yeah, the job's changed.

And so now, now the job is builder.

and you might come into that builder, you might get on the builder track by coming out of coding or product management, design or, or maybe even something else, customer service, or whatever.

but you then, you, you then become responsible for building, you know, building complete products.

and again, you have this kind of, you know, you're super empowered by the AI that can help fill in, all the things that are not directly in your background.

I really think there's two ways you, you can interpret this video, which is with a scarcity mindset to say, "Oh my God, my traditional job role, whether it's product manager or even software engineer, isn't safe anymore.

I now need to include things into my job description that weren't mine or that I'm not so comfortable with." And I really understand this fear or pushback.

But I'd like to point out, if you're a marketer or a salesperson watching this, that you're not the only one that's gonna have to adapt their job description.

personally, I find the prospect of being able to actually ship code to a real product that's been making money really exciting.

Like, to me, whenever I get to contribute to Tella, our product, I get really excited.

Whenever I get to build a skill that people then use or, like, build on top of, I get really excited.

using AI has just unlocked a way for marketers just another way to express your creativity, your whimsy, your taste through product, then I think you'll really like this challenge The second rebuttal is that networking was way more impactful on hireability.

Now, I will admit, this post was a bit rage bait-y.

I said that in a year from now, if you don't have a GitHub account, you're not hireable.

Of course, that's meant to get you to click on it.

Now, networking itself, coming from someone who has built a personal brand and who has invested in this over the past years.

Whenever I wasn't working on my job, I would spend time creating LinkedIn content, X content, or Twitter content, et cetera.

of course, I believe in networking in this, sense, I can also confirm that all of my jobs have come through network or have come through, having an online presence and then having people find that.

I think networking sounds a bit demotivating, this depending on, yeah, what your position is geographically or what your, yeah, what your draw at life is.

If you have a GitHub account and it has thousands of followers and each, repo that you post has hundreds of stars, then that's, to me, signals, as a hiring manager, signals that you have built some sort of an audience.

So rather than networking, which to me sounds something, like something you, you kind of sit down to do and then think of who you could reach out to and puts everything in the other person's hand when it comes to finding a job, I think you should probably do what you can control and, try to gain following or an audience through that.

Number three rebuttal.

Engineers will think your GitHub profile is lame.

I saw this tweet the other day, and it really made me laugh because it was posted, I think, a day after I posted that I think marketers should be on GitHub.

And it basically said, "One of the worst things you can do to your GitHub profile is turn this, your README," which we'll see in a second is, like, your About Me, "into a mess like this." And I think this is so funny because it does how marketers think about any opportunity to, yeah, market themselves or brand themselves versus engineers, where for software developers, it's really cool to look like you don't care.

In fact, spending too much time on polish suggests that you're probably not that good at what you do.

And this was actually confirmed by our CTO who said, "Ugh, if I saw a developer with, like, this really polished profile, then I'd be like, 'You're probably not very good at your job.'" Which may be toxic and problematic in itself, but we are marketers, salespeople, customer support people.

We're not developers.

So once you're done spending 10 or 15 minutes on this About description, and as long as you write it by hand and not using AI and don't make it sloppy, then you're good, and you can just go back to focusing on building.

Again, you'll be one of few marketers that actually spends time on this, so you'll still stand out, in my opinion.

Number four rebuttal, which I think is also very fair, is all of my work is in private repos.

So if you work in a startup and you actually contribute to your product, you might be a product manager or even a marketer, then much of the code that you will be, committing will be going to private projects, as you can call them.

Now, my counter to this is twofold.

On GitHub, you can still change the settings of your contributions, and you can actually make private contributions visible as well.

So rather, it won't show what you actually committed, don't you worry, but it'll show how active you've been on GitHub the past year.

So I think that's still a nice signal.

again, take all of this with a grain of salt.

Like, this isn't guaranteed gonna get you a job, but I do think it's nice to see that you've been active on there.

And then the second thing is that I think it just cool to use, AI to build projects of your own.

So, like, I've been working on a budgeting app forever, that's gonna help me save more and do less impulse spending.

I also worked on a AI psychologist, so something that's gonna help me recognize patterns.

And then I also like to dabble with anything fashion-related, wardrobe-related, to help me with my outfit stress.

So I think beyond work, think of the things you like to do, whether it's reading, your family life, sports, relationships.

Anything that interests you beyond work, just build stuff around that, if you distribute it well, you will find interest for it, and people will use your code.

The last counter was, "This feels intimidating." I saw really endearing posts by some people who were saying, you know, "I wanted to hate on this post, and I did hate on this post, but if I'm being honest, what I felt was anxiety at the thought of having to ship code, be on GitHub, do all of this technical stuff.

Like, I'm a marketer.

I wanna be creative in a, in a traditional sense.

I don't wanna be learning this new thing." And I really empathize, and that's also why I make a lot of these videos, because I'm in the same position, and I just wanna show you how easy it gets to do this.

So let's set up a GitHub profile kind of from scratch, and then you can see what the options are.

I'll walk you through some of the definitions, and then we can wrap up the video.

Number one, I wanna kinda do the anatomy of your GitHub page.

So this is mine.

I've removed my About section, 'cause we're gonna be making that just in a second, but I wanted to show you all of the things that you can update once you've gone to github.com and created an account.

The first step would be to see if you have a kinda team that you could join.

So I have, a Tella team where all of our code lives, and I can actually contribute to that directly using Claude.

on the left side here, you obviously see a small bio that you can edit like so.

Just add a description of yourself, as well as your social profile.

So what I just wrote here is where I work and what I do, and then, what Tella does, of course, and then also briefly the things I'm into.

On the bottom here, you can link your organization or where you work, of course, as well as links to your social profiles.

So if you actually go to my X account, you can see that I also brand myself as AI for non-engineers, which I did not change before this video.

I've always been talking, to non-engineers.

Then on the bottom here, we have our contributions, which kind of like a activity monitor for how much code you've been committing, and apparently also how active you are on GitHub.

So let's say you're reviewing someone else's code or their project.

So in our case, if I make a design for something, then I have our designer review our code, and then he can, well, he doesn't review the code.

He just reviews the design I made.

And then if he approves, then I can merge or basically publish the code to production.

So this graph I think is really cool.

you will see private activity over here, and as I said, you can turn on or off, your private contributions, so basically saying, do you want people to see that you've also committed code to a private repository.

Now, you've heard me say the word repository quite a bit, and I just wanna define it very quickly.

I think the best way to define it is a little folder with code in it, vibes in it.

I'm gonna show you one repository.

It's basically a folder with code in it that people can download or clone to their, own device and then start using or building on top of.

So let's open an example here.

This is a skill, a Claude skill.

If you don't know what Claude skills are, just look up Claude They are, yeah, also instructions for an AI model to act in a certain way.

So I basically made a skill, that allows you to turn long-form videos into short-form videos, and what's in here is a bunch of folders that you would basically, yeah, clone to your own computer or download if you want.

This can contain whatever you want.

It can contain more documentation, so more, like, traditional files, markdown files with information on how to use this code and then actual things you need to have the code run, and install on your computer.

I just need you to know that whenever I make something with Claude and I publish to GitHub, Claude publishes this through the GitHub CLI, and is just a way for you to talk to, GitHub directly using a AI model or through your terminal.

Your terminal looks something like this.

So if you set that up, then, Claude can basically take actions such as publish your code and your repos directly to your GitHub account.

So I didn't even write these descriptions in a lot of cases.

But you can see here, I'm just explaining what this does.

And you can ask Claude for help and say, "What does my code actually do?" And just make a description of that and publish it.

I think it's nice to see here you have some requirements as well, so just making sure that people have installed certain, yeah, prerequisites to run your code so that they understand what it takes to work and actually be usable.

and then also here at the bottom, included a structure, so it basically has a description of the skill, and then it has Python scripts.

So Python is just another, coding language, and these scripts all have different jobs.

just wanted to show you the anatomy of a repo, and then on the side here, you have a bit about the, repo and how many people have liked it, 'cause stars are just likes, and then how many people have forked it, which is they've cloned or copied the code and then are now building on top of it.

And I've actually seen people build new products, on my code, which is so cool.

So I made this I should say this is open source code, which means that it's free.

People can fork it and use it and do whatever they want with it for free, because I'm not trying to make money off this.

If you had a, product you were working on that, was private or in stealth, you wouldn't wanna share your repos, right?

Like, your code would all live in private, repos.

So back to our home profile here, you can see that you can actually customize your pins and basically select your repos or your projects.

So you can select the ones that have the most stars.

If you don't have stars yet, that's okay.

Just, put the ones that you, like here.

And then I'm gonna show you one more thing, which is we're gonna go and create a repo here, and we're gonna use that to, basically write a bit of an About Us section.

You can also do this through Claude, but, I just wanna show you can do it manually.

So you will have created your first repo.

On here, we wanna turn on README, because the README is where we're gonna enter our About section, and then we're gonna create a repository.

You'll see here that we've just created a special repository, The way we do that is by naming our repository exactly by our username, and this automatically tells GitHub how this is a special repository.

Now, you can see here it already pre-filled this in, and you can actually go and edit whatever is in here.

So here you can see that this how GitHub basically lets you fill in a bit of an About section.

learning.

So this has already been pre-populated.

I'm just gonna grab, initial text, and I'm gonna paste it in here.

Now, formatting kinda goes like that, and we're gonna commit our And here you just commit changes.

It's not that big of a deal.

You can also write a little bit of a description of what changed.

And then here, I think my photo is missing, but we can go back to our profile here, and you see now I have this nice block up here with a bunch of descriptions of what I'm working on.

So make this your own.

Put a photo of your face up in there for all I care, but I think a nice trait to have is just to keep it short, to handwrite it, and, to link to things that people will find relevant.

So I post on YouTube, here I basically share a video that got 31,000 views, and and that goes through how I edit videos with Claude.

So I think that's really nice, to send people to and show that you're a human.

And then I have links to my repos, and then I write about what I'm currently working on.

I had a photo in here.

but apparently that file didn't, stay in there, So the way I added a photo is I just went to Figma, and I created this banner of my dog.

You really don't have to add a photo, and it's probably gonna rage bait the developers the most, but I don't really care.

So Maggie is my dog, and it's just gonna save to my desktop.

Let's grab this here, and then you can just drop this in here as well.

Here you go, and we're gonna commit these changes.

Commit.

And there we have Maggie.

So let's go back to my profile.

I mean, this makes this so much better.

No, I'm just kidding.

So that was it for my super easy GitHub for marketers walkthrough.

I hope that I convinced you to not be afraid to start using Claude to start building skills, apps, whatever you want and whatever you think the world needs, and then actually publishing that to this website.

It's literally having a profile on a website rather than having a separate portfolio, which takes a lot of time to update.

Let me know in the comments if you have more questions or if you're still in doubt about something.

I'm here to help, and I'm also just new on this journey.

I have a whole team of devs behind me, so if I have a question that I know don't know the answer to, I can also ask them, and they can help us out.

So I'll see you in the next video, and don't forget to subscribe.