Don’t use snapshots of evolving libraries

Some advice to fellow developers: don’t be tempted to use a local snapshot of a rapidly evolving library, like Polymer.

One of our team members was doing this because he thought it would hasten his compilation when he needed to do new builds of Kerika (he is located in an area with somewhat slow Internet connections).

This might, sort of, work with a very stable library, but with something that is evolving fairly rapidly (like Polymer), you run the far greater risk that you snapshot’ed a somewhat buggy version.

That’s what happened to us, leading to a perplexing day of debugging: we had a version of Polymer that didn’t work well with Internet Explorer 11.

Just our luck that our developer took a snapshot of that particular build and then kept it on his local machine…