Greg Hendershott <rac...@greghendershott.com> writes:
> Idea: The cool kids these days tend to create an account on GitHub or
> GitLab. That way, other folks can see the code and more easily offer
> advice. Plus, the commit history is itself a story about your journey
> doing this. The commit messages can even be sort of mini blog posts,
> draft material for real blog posts.
To expand on this. I mostly wrote Turbo Pascal and C code in the 80s.
Today I mostly write Racket. Going from C/Pascal to Racket, is a big
change. :)
But also important: In the 80s I mostly didn't use version control. (In
the 90s, I mostly used version control systems that mostly were awful.)
So: Git is also a change. A big change. At least for me. I commit early
and often. It's a way to leave a trail of breadcrumbs. What was I
thinking? How the heck did I get here? How can I back up and get out?
You could think of it as a kind of persistent undo system. (Plus it can
be an undo _tree_: You can quickly/cheaply make branches to explore
different approaches, in parallel.)
That change may or may not be something that you want to embrace. I just
wanted to clarify that using Git{Hub Lab} as a kind of "coding social
network" is only part of the story when it comes to Git.
--
You received this message because you are subscribed to the Google Groups
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to racket-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/racket-users/87sgtk3gg1.fsf%40greghendershott.com.
For more options, visit https://groups.google.com/d/optout.
