Refactoring taken too far – a case for simplicitykenneth-truyers.net3 points·by Kennethtruyers·9 ปีที่แล้ว·0 comments
Iterators and Generators in JavaScriptkenneth-truyers.net2 points·by Kennethtruyers·10 ปีที่แล้ว·0 comments
Technical debt: managing code qualitykenneth-truyers.net2 points·by Kennethtruyers·10 ปีที่แล้ว·0 comments
NPM Gate: a different approach to prevent itkenneth-truyers.net1 points·by Kennethtruyers·10 ปีที่แล้ว·0 comments
Testing RestClient with an in-memory serverkenneth-truyers.net1 points·by Kennethtruyers·10 ปีที่แล้ว·0 comments
The test pyramid, and when to ignore itkenneth-truyers.net3 points·by Kennethtruyers·11 ปีที่แล้ว·0 comments
Running SpecFlow Acceptance Tests in Parallel on BrowserStackkenneth-truyers.net1 points·by Kennethtruyers·12 ปีที่แล้ว·0 comments
Kennethtruyers·8 ปีที่แล้ว·discussThat's indeed true for the default interface implementation, but I believe for nullability it's just compiler warnings. At runtime, nothing will be left in the IL for this. It just isn't possible to do that and maintain backward compatibility
Kennethtruyers·10 ปีที่แล้ว·discussYes, yield return (and iterators in general) are the coroutine implementation in c#.Here's some more info (although outdated): https://en.wikipedia.org/wiki/Coroutine#Implementations_for_...Thanks, glad you enjoyed it!