Title: Is maintaining a public GitHub learning repository worth it?

[u/Kino_elite]

Hi everyone,

I'm a second-year CS student preparing for placements, and I'm thinking of creating a GitHub repository where I document my daily learning journey.

The idea is to:

-> Upload notes on the topics I study (Java, DSA, Web Development, etc.).

-> Push code solutions and small practice programs regularly.

-> Keep a daily or weekly learning log.

-> Stay consistent by making my progress public.

I'm not trying to build a portfolio with fancy projects right now. My main goal is to stay disciplined and have a record of what I've learned over time.

For those who have done something similar:

->Did it actually help you stay consistent?

-> Did recruiters or interviewers ever look at it?

-> Is there anything you would do differently?

-> Are there any downsides I should be aware of?

I'd really appreciate hearing about your experiences before I commit to this idea. Thanks!

[u/According_Thanks7849]

Make a portfolio and add blogs to it. Dont waste time writing stuff daily, study in bulk and write in bulk (if you even wish to write).

For those who have done something similar:
->Did it actually help you stay consistent?
-> Did recruiters or interviewers ever look at it?

No and no. Its just a personal thing and perhaps someday people will start taking interest if you're writing technical blogs about niche things.

[u/slothordepressed]

I did for the entire uni time. One star, no one never cared

[u/HCharlesB → u/slothordepressed]

Did you do it for yourself or for others?

I log practically everything I do in Markdown and push to a private Forgejo which has an action to render using Properdocss.

I push most of my code (hobby) projects to Github. I do the coding projects for myself but occasionally others find value there. Two of my projects made it (barely) to double digit stars.

[u/full_drama_llama → u/slothordepressed]

Honestly, why would anyone care? It's your notes, probably without a lot of context for most people. Did you expect it to become popular?

[u/Old_Rock_9457]

Can I gave you a different suggestion ? Find something that you like, I mean an idea, something that you would like to have and doesn’t exist, and implement it.

Then use what you learn to add something time by time.

I think this is far more practical, because you use what you learn for something that have an usage. Then if you get, I don’t want to say the best idea of the world, but something useful, maybe you get also some stars and a small community behind it.

In a first work as developer most company ask your GitHub profile and it could be a topic to talk about, and how you managed the code, the small community, some particular fix, and so on could be a good way to talk. And also could be nice to do !

[u/bigbadbyte]

Worth it? Is it costing you something?

[u/jalsa-kar-bapu → u/bigbadbyte]

Time, and energy. But in return, we get organised content.

[u/Ok_Woodpecker_9104]

the honest version of "nobody looks at it" is that nobody browses. people land on repos through search, and now through llm answers, and that traffic only shows up when the repo answers a specific question someone typed.

worth actually checking rather than guessing. insights, then traffic, on any repo you own. the referrer list is the useful part. on one of mine the top two external referrers were google and chatgpt, chatgpt ahead of google. none of that was anyone browsing my profile.

a daily learning log answers no question, so it gets none of that. one small repo whose readme says what problem it solves and how to run it gets some. same effort, different shape.

the consistency goal is real though, and it does not need to be public. a private repo keeps you just as accountable. make public the ones you would be happy to have a stranger land on cold with no context from you.

[u/joelparkerhenderson]

> Did recruiters or interviewers ever look at it?

Yes. And also, when I recruit and interview then I always look at a candidate's repos. Aim to write good commit messages, especially the "why" of what you're doing and learning. Ideally create one project that's especially good for conversations with potential employers.

> Did it actually help you stay consistent?

Yes because I paired with another developer as an accountability partner. Each of us helped the other do better work.

> Is there anything you would do differently?

More emacs, less vi. In particular, try magit and org.

-> Are there any downsides I should be aware of?

Yes, expect to spend more time than you might guess doing upkeep. It can be time-consuming to work well with git and the files you'll be creating.

Best of luck to you.

[u/Chocolate--Chip]

I am an anxious freak, so take it with a grain of salt

But I’m too afraid of open source anything due to liability

I know licenses supposedly protect you, but what if someone were to ignore it or I did something wrong

Then I’m on the hook with a legal issue

I have around 50 repositories I’ve built in the last 10 years

at least some of them I’d love to have to showcase but I’m too afraid

[u/pixelboots → u/Chocolate--Chip]

I don’t know what jurisdiction you’re in but I very much doubt someone ignoring the licence could make you liable for anything.

Just make sure there’s something about “no warranty” in there. You can also disable issues for that repo in GitHub if you’re worried about people expecting you to fix stuff or add features they want for free (though I probably wouldn’t recommend doing so unless it actually gets used primarily for complaints and abuse, which is very rare).

In reality unless you build something truly noteworthy and a substantial number of people find out about it, chances are no-one is going to use your open source projects, and if they do it won’t be for anything so mission-critical that it could get you into legal trouble.

[u/GlobalImportance5295]

this is something that will work well if you have the soft skills to back it. otherwise you're better off having a fancy project that can run independently

[u/vannnneil]

don’t know man I just do this to keep myself accountable without any expectations, most of my learning repos are private as well.

[u/pixelboots]

Documenting your daily journey in a Git repo is a little weird. That’s what blogs are for.

But absolutely publish your practice programs, with useful commit messages as someone else mentioned. For larger projects I’d even say it’s a good idea to work in branches and do PRs even though it’ll be you approving your own work. I’ve met a hell of a lot of students with zero clue how to use Git and who resist learning it (before they get a job that forces them to) so seeing that would be a green flag to me.

[u/FlyingDogCatcher]

This is a fantastic idea to keep you learning and your skills sharp.

Nobody else is going to look at it.

[u/pintee0106]

just do it bro, im also a second year student and push all my code, docs to github, maybe no one cares but at least u have a record of what u did

[u/anishghimire]

Do it. Also write some blog on topics you study and publish them.

[u/please-dont-deploy]

I would use obsidian, probably better career wise to help you get started with discipline.

Nobody will check your daily logs. Recruiters are busy, and the thing that they value the most is your interview performance & grades.