🤯 wow, that’s a neat idea! That might come in handy some time 🤔

Feature flags are another solution. Merge the code, but have it disabled on prod until you enable the feature flag (when the whole feature is complete and deployed)

Not all Amish view technology as entirely something against their religion. Peter Santenello has a bunch of great videos where he interviews Amish people and understands their culture. This is a good one on that topic: https://youtu.be/EgY1SVXiBrU?si=E2zTNOhQxm6Qcgff

I thought that link was going to point to this other great programming language

I often take notes in the form of “TODO” comments, as I work through a problem. Then I have my editor set up to highlight them, and my git asks me if I’m sure I want to commit them. Works pretty well with keeping my thought process straight

I’ve jumped around between a few different platforms. Started on ancestry.com, but didn’t want to pay for the subscription. Then self-hosted for a long time using webtrees. I tried Wikitree.

Now I’m on FamilySearch, for a few main reasons:

1. They have MANY sources indexed and searchable
2. I really like how easy it is to link sources to individuals. That was something that was cumbersome in Wikitree and Webtrees.
3. Probably most importantly, all the data is shared between everyone. So everyone is working on the same big tree. That way, if I work my way up to my g-g-g-g-grandparent, and a distant cousin of mine has already done the work of researching that person, I just need to link to them. That said, this is a double-edged sword. I get to benefit from their research, but if they did it wrong, I might have a bunch of cleanup to do.

I also use 23andme to cross-check and find new relatives via DNA.