Susan Potter

Talk to your kids about decentralized version control before someone else does.

And patch theory too.

found the darcs user

Pijul.

Using Pijul is like wearing a nerd beanie where each propeller blade also has a tiny propeller mounted on it in other words EXTRA AWESOME

Practice safe commits.

And sign your commits.

I don’t do this. Should I do this? I don’t think my commits are generally important/sensitive enough to warrant signing. Just keeping tabs on my apt signing key drives me loopy.

In some contexts (sadly not at work) all contributors sign commits and have done since the first commit. As a result there can be greater level of trust since all commits are signed (signing a commit on top of a signed commit, etc).

I have signing commits setup by default. Your mileage may vary, but I concur with the other replier re: signing release tags.

It’s something that’s been in my to-look-into list for a while. I tend to commit across many different devices (directly from dev on a Pi) which has been a point of friction for me getting started. Already have SSH auth keys scattered to the four winds

Agreed. Your 8yo should create a sourceforge account and use CVS until she's older.

TIL https://sourceforge.net  is still a thing!

Haha. My 15 year old has an account. Now my dilemma is do I learn him Vi or Emacs?

Ha! While I might be all about emacs now, I am recommending VSCode to coworkers as they get up to speed with Haskell now.

Same happened here. He is now using vscode for a school project. :-)

Vim has it own learning curve. But if something non-vscode like is rightaway introduced to children, they might grasps it very well. There is no bias of why am I doing all this. I can do it easily in non-vim like text-editor. Although vim key bindings on vscode can be introduced

*chants* NANO NANO NANO

That's what the comparative command reference for editors says for most features in the pico/nano column: "N/A, no". ;-)