I think it's worth investing in an ongoing effort to write bugs for old code (because that's the code we'll be modifying), especially if it's like...stuff that we're going to restructure, while wanting to make sure that we don't break old expected behavior (if we do do that. I'm not sure if there's anything currently on the plate?).
But a better investment, and one that's less likely to fizzle out/burn out, is to try to code stuff for new modules, as you code them. I still need to sort my thoughts out for how to write something appropriate for dw_dev, but it's something I'd like to encourage!
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
mmmag
no subject
Date: 2010-02-09 05:28 pm (UTC)But a better investment, and one that's less likely to fizzle out/burn out, is to try to code stuff for new modules, as you code them. I still need to sort my thoughts out for how to write something appropriate for dw_dev, but it's something I'd like to encourage!