Explore >> Select a destination
|
You are here 
|
qntm.org | ||
| | | | |
gist.github.com
|
|
| | | | | Swift Concurrency Manifesto. GitHub Gist: instantly share code, notes, and snippets. | |
| | | | |
jonathan-frere.com
|
|
| | | | | This review is largely in response to the article "It's probably time to stop recommending Clean Code", and the ensuing Reddit discussion. A lot of really interesting points were brought up, but the big question that the author themself wasn't able to answer was: "What should we recommend instead?" I believe the book we should be recommending is A Philosophy of Software Design by John Ousterhout. In this post I want to spend a bit of time reviewing it and giving an overview of the contents, and then I want to explain why, in my opinion, it is such a good recommendation. | |
| | | | |
blog.slaks.net
|
|
| | | | | ||
| | | | |
eyakubovich.github.io
|
|
| | | The guidance around function arguments and smart pointers is quite old, yet I still see it used incorrectly. In this post, we'll explore the guidance and the costs of not following the advice. C++ Core Guidelines make this point clear: F.7: For general use, take T* or T& arguments rather... | ||
