Ask HN: How to make sure developers do not change public API?

  • In addition to normal unit tests, you can write tests whose job is a warning to a human being "you are about to do something dangerous, are you sure?" With a way to say "yes I meant to do that" when necessary.

    Whereas unit tests test the product, these tests are oriented towards the development process.

    https://codewithoutrules.com/2016/03/01/process-reminders/ has an example.

  • So basically, you don't trust your developers to do their job properly. Do I understand that correctly?