Explore >> Select a destination
|
You are here 
|
briankung.dev | ||
| | | | |
shermanonsoftware.com
|
|
| | | | | A developer recently confided in me, "I wanted to write good code on this project, but when I asked my manager he said we needed to do whatever it took to hit our delivery date." He was explaining why he shoved his changes into the existing, giant, untestable, functions instead of refactoring and writing tests.... | |
| | | | |
blog.thesoftwarementor.com
|
|
| | | | | ||
| | | | |
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.pullrequest.com
|
|
| | | Reading these foundational books will help you understand software development processes more, how to reduce technical debt, and contribute higher-quality code. | ||
