Archives

All Posts

• The Law of Demeter and unit tests
• 'Privatize' your classes for better unit testing
• Tests should be isolated from each other; not coupled
• In unit tests, I favor Detroit over London
• Defining unit tests: two schools of thought
• Primary attributes of unit test suites and their tradeoffs
• The big WHY about unit tests
• Unit test the brains and not the nerves
• Mocks, Stubs, and how to use them
• DRY unit tests are bad... mkay
• Do not index on test coverage metrics
• Beware of using patch.object to test your Python code
• When I first realized my privilege
• Reuse Code, Not Objects
• Code reuse can prevent bugs
• Tale of two departures
• Donts of processes for upward communication
• Responding to concerns as a people manager
• Git may not be the best for SaaS companies
• When should you build for survival?
• Are you building for Survival or Excellence?
• Object Composition for Service Migration
• folly:Future, onTimeout(), and a race condition
• Scripts and their undo
• Merits of unit tests — part 5
• Unit tests FTW! — Part 4
• The merits of unit tests — Part 3
• The merits of unit tests — Part 2
• My code is bugfree! Why should I unit test?
• Small town Bulgaria
• Shipka Memorial Church
• Troyan Monastery
• Hitar Petar
• Tsarevets: a photo essay
• Airfare booking and pricing, demystified!
• Solvability-based comparison of failure detectors
• Stabilizing Dining with Failure Locality 1
• Moving to Google
• Wait-Free Stabilizing Dining Using Regular Registers
• Leader Election Using Loneliness Detection
• Asynchronous Failure Detectors
• Failure Detectors Encapsulate Fairness
• Tunisia, December 2010
• A successful defense
• Proposing a new radio show
• Big Bend Nov 07
• Tryst with Kudremukh