If using a development process that consists of multiple stages of maturity, development mainly progresses in one branch only. I often use a process that consists of the three branches ‘develop’, ‘staging’ and ‘master’, so in my case the development mainline is ‘develop’. You might want to check out my post on how to enforce or safeguard such a development process.

Git pre-commit hooks can be used to enforce version control best practices.

RFC 4122 requires the use of MD5 oder SHA-1 to generate name-based UUIDs, prefering SHA-1 when possible. Since the standard has not been updated since more than a decade, more robust hash functions are not included in the standard. SHA-256 for example has a better resistance against preimage and collision attacks than SHA-1 and should retain these properties even after truncation. For that reason I developed the following class using SHA-256 to create the message digest, instead of MD5 or SHA-1.

Here’s another one of my world-class recipes, the lasagna “Paradigm Disruptor”.

This post lists some measures that can be taken to secure/harden a CMS (content management system) installation.