Explore >> Select a destination
|
You are here 
|
www.markhneedham.com | ||
| | | | |
briankung.dev
|
|
| | | | | The first thing I do when I encounter a strange code base is run the test suite. I do this because I can get an idea of: the exact use cases that the developers envisioned the actual usability of the APIs the overall health (read: test coverage) of the project and get an idea of... | |
| | | | |
andreabergia.com
|
|
| | | | | Recently, I have started working on a large code base. It can reasonably considered "legacy" in many parts, given that some of the core files that I'm touching are around 20 years old. Also, there aren't anywhere near enough unit tests - even if there are a good numbers of integration tests. This has led me to think back to one of the best programming books I have ever read, Working effectively with legacy code by Michael Feathers. | |
| | | | |
www.mikekasberg.com
|
|
| | | | | The Myth of Code Reuse, a quick video by Iain Lowe, became quite popular on Reddit in /r/programming a few weeks ago. I think the... | |
| | | | |
www.planetgeek.ch
|
|
| | | Active patterns make using a Regex in F# neat: The matched groups are returned in the list after the pattern. Here is an example from our codebase: Pattern found at Active Patterns - F# | Microsoft Learn: In this example, I use the regex active pattern to map JSON parsing errors to a Result with... | ||
