wh33zle

9 ms·

1. 61.▲
   by wh33zle 6y ago

   I think I understand what you mean. At the same time though, one crucial takeaway for me from Ian's talk is that my tests might be on a too small scale if they are not useful whilst I am changing the implementation strategy. For exampl
2. 62.▲
   by wh33zle 6y ago

   To be fair though, if your tests are at the right abstraction level, the specific approach you are choosing for the implementation shouldn't matter for the test. Writing the test first also forces you to think abouy what API do you act
3. 63.▲
   by wh33zle 6y ago

   For example, my CI provider might want to execute my build in a docker container for security reasons but I also want to run/build a docker container as part of my CI.
4. 64.▲
   by wh33zle 6y ago

   A case where it is unavoidable is when you want to refer to an associated type in your struct declaration. In most other cases, putting bounds on impls leads to less repetition of those bounds and better error messages! Another related topi
5. 65.▲
   by wh33zle 6y ago

   Adding to this, copy/pasting things works especially well if the code is contained within another abstraction that is much more unlikely to change. For example, say your service has a REST API. It doesn't matter much, how the func
6. 66.▲
   by wh33zle 6y ago

   As in, create an abstraction so everyone gets to do it their way and you don't have to debate?