Explore >> Select a destination
|
You are here 
|
mydeveloperplanet.com | ||
| | | | |
lackofimagination.org
|
|
| | | | | Think back to the last time you looked at an unfamiliar block of code. Did you immediately understand what it was doing? If not, you're not alone - many software developers, including myself, find it challenging to grasp unfamiliar code quickly... | |
| | | | |
martinfowler.com
|
|
| | | | | There are only two hard things in Computer Science: cache invalidation and naming things -- Phil Karlton (bonus variations on the page) | |
| | | | |
hilton.org.uk
|
|
| | | | | The hardest thing in programming and the great naming myth | |
| | | | |
everythingfunctional.wordpress.com
|
|
| | | The answer to the question of whether we should write automated test suites has largely been settled. We absolutely should write unit tests, and possibly even integration and end-to-end tests. But as acceptance of this practice grew, and adoption became more widespread, a follow-up question arose; How many tests should we write? How do we... | ||
