Shitlist Driven Development (2016)
sirupsen.com
Shitlist Driven Development (2016)
1–10 of 148 posts
Re: Shitlist Driven Development (2016)
#2In case you wonder what shitlist means:
> “shitlists”: a whitelist of deprecated behaviour. Existing deprecated behaviour is OK and whitelisted.
Re: Shitlist Driven Development (2016)
#3This is an excellent way of using your (hopefully) already existing testing and CI infrastructure to change a social problem into a technical problem. As we all know, technical problems are by far the easier of the two. :)
We used this technique to great effect at my previous day job, though under the more neutral name of "ratchet".
Re: Shitlist Driven Development (2016)
#4Brilliant. It's a really good compliment to strangling certain parts of a large code base.
As always the key is getting the information to the right people at the right time, and making it more difficult to make the wrong choices then the right choices.
Re: Shitlist Driven Development (2016)
#5whitelist triggered
Re: Shitlist Driven Development (2016)
#6Here, a “shitlist” tracks existing uses of deprecated behavior within a large code base. It prevents new uses of deprecated behavior without disrupting legacy code. This is a temporary measure used to facilitate refactoring large code bases.
Re: Shitlist Driven Development (2016)
#7Shitlist driven migration/refactor, maybe. If it's development it means you're always deprecating something and that's a significant organizational smell.
Re: Shitlist Driven Development (2016)
#8I kept a personal shitlist in one project but it was rather a collection of "worst practices" - things I vowed never to do.
It was personal because the idea didn't get a lot of attention when I brought it up.
Re: Shitlist Driven Development (2016)
#9'Shitelist' would rhyme better with 'Whitelist'
Re: Shitlist Driven Development (2016)
#10We used a similar approach when we pushed to get -Werror enabled in a large C++ code base I worked on years ago.