I really hate getting invested in a big chunk of code that I didn’t write only to find out later that something didn’t work quite the way I expected. The web needs a straightforward resource that helps developers decide what libraries and tools they should use. To help accomplish this, I’ve started a wiki called Dev Diligence to collect real life experience with code. Check out the wishlist that I’d like to hear about, or read the full blog post for more back story.
Tags
/dev/epoll
Assertions
Audiogalaxy
Berkeley DB
Bloom Filters
consistent hashing
Dev Diligence
dynamo
FolderShare
Google
History
ideas
intolerance
memcached
Message Passing
MS Manners
MySQL
partitioning
prizes
productivity
RIAA
Skip Lists
Soft Deletes
Startup Lessons
startups
STS
Toolbox
Unrolled Linked Lists
uptime
VEB Trees
0 Responses to “Dev Diligence”