> * I make the library and release it with an MIT license This might get you into trouble. Basically, anything you touch during your work hours is tainted by y

> * I make the library and release it with an MIT license This might get you into trouble. Basically, anything you touch during your work hours is tainted by your employers copyrights. You're not allowed to decide which license that code should be under. So either you write that whole library in your spare time (and on top of that do your regular day job) or get your employers permission to release the code. In general the approach is sound and I'd support it, but others might or might not.