Scribes Oath
Uncle Bob is a little controversial, but does have interesting viewpoints on software development. If you have not heard his Scribes Oath before, it is worth a watch (blog post summary for those lazy). https://andreas-loizou.medium.com/the-scribes-oath-ac964c96a6b9
- I will not produce harmful code.
- The code that I produce will always be my best work. I will not knowingly allow code that is defective either in behaviour or structure to accumulate.
- I will produce, with each release, a quick, sure, and repeatable proof that every element of the code works as it should.
- I will make frequent, small, releases so that I do not impede the progress of others.
- I will fearlessly and relentlessly improve my creations at every opportunity. I will never degrade them.
- I will do all that I can to keep the productivity of myself, and others, as high as possible. I will do nothing that decreases that productivity.
- I will continuously ensure that others can cover for me, and that I can cover for them.
- I will produce estimates that are honest both in magnitude and precision. I will not make promises without certainty.
- I will never stop learning and improving my craft.
I like the oath and it generally resonates with me. But I am not a fan of 1 or 2, they seem strange and not actionable to me. But 3, 4, and 5 resonate with me as a developer, they are pretty much the definition of Agile and CI/CD. 6,7, and 8 are important from a team perspective. None of us could launch a system alone, it is only through our cooperativeness can we achieve success. Something tells me that 9 resonates with everyone of us, we are in the cutting edge tech space, arent we?