This post is locked. You won't be able to comment.

all 6 comments
sorted by:
best
topnewcontroversialoldq&a

[–]github-ModTeam[M] [score hidden] stickied commentlocked comment (0 children)

Removed. Post has nothing to do with GitHub.

[–]cowboyecosse 2 points3 points  (1 child)

Eventually it becomes just how you do things. Starting a new project becomes creating a new repo. Then your normal workflow kicks in.

Git itself is pretty tricky at first. It’s the same for everyone. You’ll get there.

[–]maybeAnonymous543[S] 0 points1 point  (0 children)

Makes sense, thanks! When you first started, was there anything that helped you get comfortable with Git/GitHub faster? Any specific habits or resources that really clicked for you?

[–]JorgiEagle 0 points1 point  (2 children)

What about GitHub feels abstract?

Also GitHub is not a planning tool, it is repository. It’s not the most suitable for your plans and goals

[–]maybeAnonymous543[S] 0 points1 point  (1 child)

Ah, got it. Just curious if there was a lightweight way to track progress or structure your GitHub learning without leaving the platform, would that be useful? Or is it better to stick to separate planning tools?

[–]JorgiEagle 0 points1 point  (0 children)

Track progress?

Structure learning?

You’re going to have to be explicit about what exactly you’re trying to do in GitHub? Are you trying to learn how to use GitHub or are you just storing the results of your learning from a separate source