Everything about

#techniques

Best Practices Considered Harmful#talk#techniques
A lightning talk about how best practices promote a one-size-fits all mentality that harms our ability to create solutions that are tailored to the problems at hand
Code Reviews At Disy - Observations#post#code‑review #techniques
After reviewing almost all code we wrote for 18 months, completing some 1'500 reviews, we want to share some recommendations.
Code Reviews At Disy - How We Review#post#code‑review #techniques
After setting out to create a peer review culture we came up with a workflow and picked a tool (yes, Crucible) that would help us get there.
Code Reviews At Disy - Where We Were And What We Wanted#post#code‑review #techniques
At Disy we review almost all the code we write. Here, we want to share why that was not always the case and how we started with code reviews.
A Doomed Code Review#post#code‑review #techniques
Code reviews should be brief, short, and focused. This is the story of how I fucked up on all those accounts and we still made it work.
Getting Rid Of Anonymous Classes#post#java‑8 #lambda #techniques
Anonymous classes are verbose and obfuscating. Functional implementations can oust them from their last strongholds (mainly abstract classes).
Impulse: "Workflows of Refactoring"#post#impulse #techniques
Discussing the keynote "Workflows of Refactoring" by Martin Fowler at OOP 2014, where he categorizes different reasons for and ways of refactoring.
Foobar#post#meta #techniques
A foobar post that may accidentally teach you about Foobar.