I would go on further and say that it's not only for the recruiters but also for the hires to understand whay are the general skillsets they can have to expand over a period of time.
Block-chain Dev, Android Dev, AI/ML devs are domain specific but in each of those there are atleast 3-4 domains mapping out in general from the PCM.
There will be a domain specific competency matrix on top of PCM.
Are you targeting for subscription plans (or) is it a one time payment?
Which payment integrations have you tried so far?
Bank transfers for small amounts have too much friction at this point.
If it's a simple file like a pdf, audio or video file or even an executable file then I would recommend to go for Gumroad. Wouldn't recommend if it's an App that has to be put on an App store or Play Store.
I think the mindset of those people who make such arguments are those who want to delegate individual responsibilities that involve such risks to other parties. They might not understand the risk involved when such parties get big enough to dominate and decide what to do and how to do it.
Usually, we commonly agree by coming to consensus on what to do and not to. But here the consensus, sometimes, can get hijacked by the third parties which lot of people don't understand how it happens (read historical events). 2008 banks bailouts is a good example to begin with.
As Satoshi mentioned, in the OG Bitcoin paper, that cryptocurrencies will be attractive to Libertarians.
That's a fair assumption as one would start to notice a lot of activities involved in being part of cryptocurrency, atleast currently, requires lot of individual responsibilities, especially maintaining the wallet's credentials. Not to say that they can't be automated away.
Coming to terms with taking individual responsibilities in general is very hard. Most people want others (Government) to do it.
Even though naming the commands might be arbitrary choices, they can be practiced upon. One doesn't always have to fall in the semantic trap.
The main problem that I see with using git is that when you are part of a team, what kind of release and branching strategy should you use.
It's comparatively easy with one person team but becomes complicated with a team and even more if it's an open source project and now you have individual devs contributing their changes.
This is brilliant. Do you think it will be possible to have abstraction layers that can be commonly used by everyone?
Like dependencies/modules that can be imported and tweaked on giving them parameters.