techniques

share & follow

Share this post with your community:

TwitterFacebookLinkedInXingVKRedditHackerNews

I'm active on various platforms. Watch this space or follow me there to get notified when I publish new content:

RSSTwitterDiscordMediumYouTubeTwitchGitHubStackOverflow

s+f

Share this post with your community:

TwitterFacebookLinkedInXingVKRedditHackerNews

I'm active on various platforms. Watch this space or follow me there to get notified when I publish new content:

RSSTwitterDiscordMediumYouTubeTwitchGitHubStackOverflow

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 hand2019-06-03

.postCard-module--image--2R1yV.gbi-333197263-9pzhfXevjbGjQYuBh1W9zm:before { opacity: 1; background-image: url('/static/4120ab9bccb8d734198940819e7c18b0/03d69/disy-code-reviews-iii.jpg'); }

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.2016-10-26

.postCard-module--image--2R1yV.gbi-1747259315-gj9XHJeTzw386Tw1mu7AMf:before { opacity: 1; background-image: url('/static/8c3577d62489c2c62ae327396f824394/03d69/disy-code-reviews-ii.jpg'); }

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.2016-09-26

.postCard-module--image--2R1yV.gbi-1182355883-sPg2hdnaJPw6NUrhsGEr6d:before { opacity: 1; background-image: url('/static/bd3cc45433366d1a0c08149e918a9fa1/03d69/disy-code-reviews-i.jpg'); }

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.2016-08-15

.postCard-module--image--2R1yV.gbi-2049214425-kovoAdAmAgmLATyigHAJ8b:before { opacity: 1; background-image: url('/static/58be581c5cfc9fe814007205d8f1dec5/9ffd6/doomed-code-review.jpg'); }

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.2016-04-26

.postCard-module--image--2R1yV.gbi--783967825-uY7k3zcwfoBUgyWiyVF8Rr:before { opacity: 1; background-image: url('/static/2578ac4eac6efe34b58c390ff2cbb5c9/03d69/anonymous-classes.jpg'); }

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).2015-04-17

.postCard-module--image--2R1yV.gbi-1064013582-ckNmbcsjUXjCYQiX2eV8pv:before { opacity: 1; background-image: url('/static/e77a3c69619026edf15612c682c0838a/03d69/workflows-of-refactoring.jpg'); }

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.2014-09-25

.postCard-module--image--2R1yV.gbi-1461046565-sBKkdteNfL5t1DT5fukemg:before { opacity: 1; background-image: url('/static/3d419a442b2ac1c13d822ee386af66eb/03d69/foobar.jpg'); }

Foobar#post#meta#techniques

A foobar post that may accidentally teach you about Foobar.2014-06-27

Looking for this?

Looking for this?

#techniques