Git Good: Solo Development Use Cases

Third part to the Git mini series all about working as a solo developer with Git.

Hope you enjoyed the video!

Join my Discord server and come say hi:

Check out some code on my GitHub:

Send me a Gab:

Other Social:

[EngineerMan]

You probably noticed force pushing was an item but I didn't talk about it. I decided to cut it out since it was almost entirely described as a team development problem so I'll cover it there instead.

[fadhilsaheer]

Others: preparing slides
EM: .yaml

Man of culture
:wq

[bgildersleeve]

I had barely any experience with source control until I joined a big tech company and was forced to learn to use git. Now, I can never go back, especially for solo projects. It helps me logically organize my work, focus on one task at a time, and have a clear history of everything I've ever done. It also encourages clean coding principles like separation of concerns, composition over inheritance, etc... Honestly, the single biggest level up to my coding abilities came out of learning to use git in a large organization, and all of those gains translated over to the solo use case as well.

[ChandarSunderraj]

Please talk about stash, that’s one feature I rely on heavily while working on multiple tasks and experimental features to jump between them without loosing my work

[KarlKatten]

best content out there for people trying to learn

[El-Burrito]

I guess this is kind of a funny anecdote, but when I first picked up a codebase at a company I worked for, there were credentials that were committed to the repository. So even though we eventually learned that this was bad and removed them, they were obviously still there due to it being a git repo. So when something really needs deleting you actually have to delete it from the repo entirely.

[ADITYA_JEENA]

thanks a lot for this one. thank you sir.

[Stoney_Eagle]

I'm really close to go from alpha to beta on my project and I want to do the release right.
Can you give some solid tips on how to handle that?
Like permissions, work flows, documentation, versioning and most important how to make sure a pull does not result in a broken install for a user because of a non updated dependency.

[RussellSmith-nvje]

Is it bad practice to use branches instead of tags for different releases of your software? I typically branch from master to a branch release/version_xxx, make and test changes for the next version, and once complete merge back into master. That way I can simply check out a branch if I need to go and look at code from a previous release and master will always be the latest stable release. Should I be using tags instead?

[hemanthkotagiri]

I really want to know your opinion on Linux ricing, tiling window managers and minimalism.

[yomajo]

The reason Engineer did fetch instead of pull is to review the changes from remote in local repo before merging them, right? Thanks for anyone who responds.

[BbB-vruh]

What’s the command for the merge after you’ve done git fetch?

[wiccanring]

My sister in laws facebook page was hacked and after getting it back he rehavked it. Had her setup 2FA on both Google account and her fb...google is fine, but she's got pictures of my baby nephew and he's saying he has "private pictures" and demanding money to give the account back! Is there anything you can do to punish this guy? He hid his face when I called her old account. Please help...for my nephews sake!

[eldaiblol]

Do. not. push. to. production!

Also would be cool if you used main/production instead of master-branch

[Auios]

This video promotes racism by using a master branch. /s

[merger]

'Master' naming convention is kinda obsolete

[deersakamoto]

Git is great for Linux kernel but a waste of time for the majority of solo projects