Yes - makes me think of the assassination of Shinzo Abe.
The gunman made his own gun, in a country with ultra-strict gun laws. The Unabomber made his own bombs. The Seattle mall Islamist knife attacker refused to stay down after being shot multiple times.
My takeaway: political terrorists are particularly motivated. Secondly, gun laws slow them down but don't stop them.
> When I write bad code I know because I run it, test it, and if needed, fix it.
This puts you ahead of 80% of coders in 2022. That's who's going to have trouble: the people churning out software that sucks and the companies that enable them. These companies have gotten by until now because most other companies' software sucks too.
But they're not. They created a new, feature-reduced repo type to make free/private. The marketing hides this, and you need to dig to the "Comparison" section to see it:
Maybe not so smart when devs realize that the free private "repos" have features removed that have been standard. The marketing avoids this fact. You need to scroll down to the "Comparison" section to see it. https://github.com/pricing#feature-comparison
How about hierarchical data? E.g., a country's laws / statutes? Thousands of text files organized in a hierachy. I've resorted to relational denormalizing and hacks to get decent performance. So I'm wondering if a graph database would be a better fit.
E.g., I frequently need to query, "What is the list of ancestors from the object to the top of the tree?"
In a relational system, this needs to be stored in some kind of data structure, which is redundant. But theoretically in a graph database, it'd be a fast O(log n) query if I'm not mistaken.