My sentiments exactly. If they have a well-built internal library that is heavy on specific design patterns I'd expect them to give me a hard time over it becau

My sentiments exactly. If they have a well-built internal library that is heavy on specific design patterns I'd expect them to give me a hard time over it because I could break some serious stuff or waste a ton of money writing ineffective code. Or maybe if they use heavy black-box builder tools that require some delicate coding to leverage the power of the internals. (In this case again, though, it's still dangerous to hire based on experience with a specific tool because you may get spaghetti code that happens to work within the confines of that tool -- trust me I've seen it.) But open source frameworks & js libraries are much closer to the realm of pet tech. The internals aren't too heavy & conceptually difficult, and most of the classes I see being written by developers are pretty run-of-the-mill regardless of the language/framework. The strange thing is that often the fact that companies are so up-to-date with current trends gives away the fact that they are writing tons of throwaway code. Nobody is maintaining a really mature library that depends on a framework that has been stable for 4 months. Employers would never admit that though, lol.