As I wrote recently in another post…
I find it hard how every month there’s a new better way to do things, packages that change, packages that might save time but sometimes don’t work well, lots of packages that do the same kind of thing, new versions of meteor… Too much change.
I wonder, how do you approach staying up to date? Sometimes I go to the docs, but I don’t find something that was there yesterday, and I start wondering… am I going crazy? Did this always have this name? Things change and I see nothing mentioning “NEW” or “old way, new way”. If you keep your code as it is, and things keep changing, one year later other people may be unable to work with your code, because it looks very different to what the manual says. How do you stay informed about changes you should implement in your code? I find parsing the release notes to try convert them into decisions to update my code not very efficient and error prone.
Another question is, how do you deal with the possibility that updating meteor and other packages may break your application? Do you have tests for every possible interaction to detect that something starts to fail after an update?