From 8487eac3c9f6ddcb379e3fe4956c073714fe0afa Mon Sep 17 00:00:00 2001 From: Radoslav Georgiev Date: Mon, 1 May 2023 17:43:15 +0300 Subject: [PATCH] Add clarity to the `mypy` section - Drop tweet link - Resolve #126 --- README.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index a6b6fad..ebe1fb0 100644 --- a/README.md +++ b/README.md @@ -2741,10 +2741,14 @@ A section with various things that can make your Django developer life better. ### `mypy` / type annotations -When it comes to using type annotations, alongside [`mypy`](https://mypy.readthedocs.io/en/stable/index.html), [this tweet](https://twitter.com/queroumavodka/status/1294789817071542272) **resonates a lot with our philosophy.** +When it comes to [`mypy`](https://mypy.readthedocs.io/en/stable/index.html), we have the following philosophy: -- We have projects where we enforce `mypy` and are very strict about it. -- We have projects where types are looser and `mypy` is not used at all. +> Use it, if it makes sense for you & helps you produce better software. + +In HackSoft, we have: + +- Projects where we enforce `mypy` and are very strict about it. +- Projects where types are more loose and `mypy` is not used at all. Context is king here.