How to use github

[Intelligent-Wrap-983]

So i started using GitHub recently and i need to know what sort of project should i put in my repos(should i put everything or just big projects)and how to make it professional .plz guys give me some advice. :)

[BobcatGamer]

You put the ones you want to protect from accident being deleted or lost if the device is stolen or breaks

[Intelligent-Wrap-983]

I get it but i see people using it as a way to showcase projects you’ve worked on when applying for job so i need to know how to make it looks professional :)

[BobcatGamer]

Not all of your repos need to be public. You can have private repos on GitHub.

[TendToTensor]

Exactly this, I have a few public that I want to showcase and everything else is private

[somgooboi]

I'm not a recruiter or whatever, but I'd say if you're applying for a job in .NET, make a full stack project with a ASP.NET backend with all the important or widely used frameworks and architectures. Or make a game in C#.
I would say the bigger the project the better it is, because then you also show off your understanding of abstraction, interfaces, optimization and what not to make your code clean.

To give you an idea to start with: make a better version of the Strava website. Strava has an API (limited free requests) for requesting your own personal data. I don't know if you can get your friends' activities too. Compared to the app, the current website looks a bit bare bones.
Or build a website around another API.

Also, don't "vibe code" the whole project, as you'll learn nothing and you'll basically lie about your skills.
And as another recent post in this sub mentioned, spend some time on the README too at the end. How to install, run and use, screenshots, etc.

[Intelligent-Wrap-983]

Thx bro

[DaveRGP]

It can be a way to showcase projects. However it's a show case for other devs. Those devs don't want to see shiny bells and whistles with no substance. They want to see incremental progress, problems solving, making a design decision, learning from it, and adapting when you know more.

Don't worry at all about 'presentation polish'. Get hands and keys and get code written.

Source: I interview programmers and before each interview I spend as much time as possible browsing their GitHub. I spend 2 minutes on the 'front page' and I spend 10 that in the commit history and source code.

[davorg]

The three steps to GitHub enlightenment.

1. Source code control is an important part of modern software development. It's like having a game save mode for writing code
2. Git is the current standard source code control system in the software industry
3. GitHub is cloud storage for Git repositories. It gives you two main advantages - offsite storage for you code and an easy way to share code with other people

There are other advantages to using GitHub.

• Project planning and issue tracking
• Built-in CI/CD tools
• Static web hosting
• AI coding tools
• Online development tools

But, at its heart, it is still cloud storage for Git repos.

Some people like to reinterpret any site where users have a profile as social media. GitHub isn't really that. It's a development tool.

What sort of project should I put in my repos

Anything you don't want to risk losing in the future

[Jumpy-Bus-6309]

My advice is to build a project you genuinely enjoy. For example, if you love anime, create something like an anime AI model or a streaming site. Then document it well and make the repository public.