Such ultra-liberal approach seems to project unfriendly collaboration culture..?
It seems to incentivize the contributor to try our proposing their patch multiple times repeatedly with varied introductory words just to test if the maintainer had a good day to accept the improved code.
Yup, it was mostly pleasure AI coding a company codebase in Scala. I'm considering it for next projects for this reason although my understanding and intuition for Scala code is much weaker than for Python.
Quick question: Can you split any key, like the password to my LUKS or password manager? Is there any limitation for the content of the file to be split?
First impression to me was that it is some sort of modern kinetic projectile[0] from aircraft weapons' testing. I've read US army used something of that shape in recent conflicts, but probably of smaller size.
That is a misunderstanding and a simplistic depiction of the inner structure inside the event horizon sphere.
True is we have no observations of the internals but time ending is in contradiction to the cones of particles ejected from the "hole", observed by astronomers.
You have high-stake operations in relatively small code base, so you better pick a language and tools compatible with formal verification or even supporting it natively.
That's what you should have QA pipeline ready to check before you'll be able to apply the config, right?
Secrets should be encrypted in git to my best awareness.
It seems to incentivize the contributor to try our proposing their patch multiple times repeatedly with varied introductory words just to test if the maintainer had a good day to accept the improved code.