At my small startup, we've been codifying our design and engineering principles to a much greater degree ever since COVID forced us remote.<p>You can find them here: https://www.shapedlikeat.com/articles/a-few-design-principles<p>My question is, is this something folks outside the large Ubers and Airbnbs are doing and, if so, how useful have you actually found it? Is it something that is referred to often? Or does it become a relic that's lost in the depths of Notion.<p>Curious to get a pulse on how much of our current documentation spree is warranted and how much is overkill.<p>Cheers!
We use them in my current company. I've found them useful and they have great buy in across the engineering org. There does need to be a certain level of commitment to make it worthwhile, feedback needs to be taken onboard and processes and reward need to align to the principles also.<p>Engineering Principles: <a href="https://github.com/Skyscanner/engineering-principles" rel="nofollow">https://github.com/Skyscanner/engineering-principles</a>
Some background (may be slightly out of date): <a href="https://medium.com/@SkyscannerEng/an-update-on-our-engineering-principles-80405a96383a" rel="nofollow">https://medium.com/@SkyscannerEng/an-update-on-our-engineeri...</a><p>In summary - definitely useful, but to avoid the issue you raised around documentation like this becoming a relic you need to commit as an organisation to living by the principles and reviewing them often enough<p>(*all my opinions - not the necessarily the opinions of my employer)