Unless you work with small children or large animals, the expectation of staying dry at work is pretty high. I know my workstation is very not water-resistant.
So when Blake Thorne (our product marketing manager) pitched me an article about DRY, I had no idea what he was talking about. According to our three wise men in engineering, that’s to be expected. The DRY principle is almost exclusively used in software development; those of us outside don’t have much cause to consider it.
Or do we?
And this is what Blake wanted to get at. “It’s the principle of ‘don’t repeat yourself,’” he explained. “Cut out all the unnecessary, repetitious code.”
“But one of our values is to overcommunicate,” I countered. “Everything. Twice, even. Don’t those two concepts cancel each other out?”
“Maybe,” he conceded. “But what if they actually don’t?”
I am a sucker for a good what-if.
Here I’ll go over the principle of DRY – plus WET and AHA (oh, those rascally devs) – and how here at Process Street we manage to overcommunicate without repeating ourselves. Because I’m such a nice guy, I’ll also point out the 4 best features to get you on the same path.
- The 3 principles of programming (when you’re not a programmer)
- Process Street’s DRY-est features
- At the risk of repeating myself…
Let’s get to it!