Scribd
Upload
8 views

GitHub Strategy

The document emphasizes the importance of maintaining an active GitHub profile for self-taught programmers, recommending at least five contributions per week to demonstrate coding capability. It suggests contributing to open source projects, fixing documentation typos, and engaging with issues tagged as 'good first issue' to strengthen one's GitHub presence. Additionally, it advocates for 'building in public' by documenting the development process through blogging and social media, which can foster community feedback and potentially lead to monetization opportunities.

Uploaded by

Akma Acapeo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
8 views

GitHub Strategy

The document emphasizes the importance of maintaining an active GitHub profile for self-taught programmers, recommending at least five contributions per week to demonstrate coding capability. It suggests contributing to open source projects, fixing documentation typos, and engaging with issues tagged as 'good first issue' to strengthen one's GitHub presence. Additionally, it advocates for 'building in public' by documenting the development process through blogging and social media, which can foster community feedback and potentially lead to monetization opportunities.

Uploaded by

Akma Acapeo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 5

5.

Git going on GitHub


5:27
can talk about the most important social

5:29
site in github as a self-taught

5:30
programmer it's very important that you

5:32
at least have something going on in your

5:34
github in a perfect world you have

5:35
commits every single day not only to

5:37
your own project but to many other open

5:39
source projects out there that's not

5:41
very realistic but it's important to be

5:43
consistent and that's exactly why lambda

5:44
school or bloom institute of technology

5:47
requires that you make five github

5:48
contributions per week to an employer it

5:50
shows that you're capable of writing

5:52
code every day which tends to be a

5:53
pretty important part of the job if

5:55
you're just getting started one of the

5:56
easiest ways to contribute is to look

5:58
for typos in the documentation fireship

6:00
io for example is open source and you

6:02
can find all kinds of typos in it if you

6:04
fix it and send a pull request you can

6:06
easily add that contribution to your

6:08
timeline as you start using more open

6:09
source libraries don't be afraid to open

6:11
issues when you find problems and if you

6:13
want to contribute look for issues that

6:15
are tagged with good first issue it is

6:17
true that you're kind of working for

6:18
free here but doing so will make your

6:20
github profile much stronger and it's

6:22
just great experience as a developer in

6:24
fact if you don't have fun doing this

6:25
kind of stuff then maybe a career as a

6:27
software engineer isn't the best career

6:28
path now that your github is impressive
BUILD ON PUBLIC

Build in Public
7:15
an app is one thing but the next

7:17
strategy is to build this app in public

7:19
what i mean by that is you should

7:20
transparently document the entire

7:22
process while you spend the next few

7:24
months building something awesome the

7:25
most common way to do that is by

7:27
blogging there are many sites out there

7:29
like dev2 and medium to create your own

7:31
blog easily but i would highly recommend

7:33
blogging on your own custom built site

7:35
in my opinion a custom site expresses

7:38
more passion about the craft of web

7:39
development in addition to blogging

7:41
you'll also want to be documenting the

7:43
process on linkedin and twitter and you

7:44
may even consider starting your own

7:46
youtube channel building in public is
7:48
extremely powerful because it creates a

7:49
feedback loop you don't otherwise get

7:51
when you're just working alone in your

7:52
mom's basement there's a whole community

7:54
of startups who are building in public

7:56
you should give them feedback on their

7:57
products and in return they'll do the

7:58
same to make your project better in fact

8:01
you might even consider monetizing your

8:02
project because if you build something

8:04
really good you might end up

8:05
accidentally creating a job for yourself

8:07
one example of a success story is

8:08
superhuman an email application that

8:10
charges thirty dollars per month that

8:12
was built in public they got tons of

8:14
great feedback from potential customers

8:15
while building the product and you can

8:17
do the same thing with your personal

8:18
brand while looking for a job now we can

You might also like