‘what Jeff Dean and team have been up to at Google’. Reducing request latency in a network SOA architecture using backup requests, etc., via Ilya Grigorik
It’s common for even the best programmers to make simple mistakes. And commonly, a refactoring which seems safe can leave behind code which will never do what’s intended. We’re used to getting help from the compiler, but it doesn’t do much beyond static type checking. Using error-prone to augment the compiler’s static analysis, you can catch more mistakes before they cost you time, or end up as bugs in production. We use error-prone in Google’s Java build system to eliminate classes of serious bugs from entering our code, and we’ve open-sourced it, so you can too!
Links for 2013-11-11
permalink. Both comments and trackbacks are currently closed.. Bookmark the