This might not be the answer you're looking for, but.... I am the sole technical person and am pretty much responsible for all technology for my library. I actu

This might not be the answer you're looking for, but.... I am the sole technical person and am pretty much responsible for all technology for my library. I actually don't get much of anything done on any given day. But most importantly, I maintain people's confidence in our systems and assuage their fears so that everything continues as normal. I am lying to them half the time (our downtime is almost always unexpected issues in "the cloud" and all we can do is wait. When implementing new systems, if I feel they're good, I assume it'll work out and promise success with a hiccup here or there), but it's necessary and important part of keeping us going. Simultaneously, I have developed several apps on the side. I guess the point I am trying to make is that productivity is relative. It's what matters to you and your company. If features are important to your company, then you should be knocking them out. If you're a university with 15,000 students and thousands of full-time employees, not doing much and making sure people still trust you is more important. With that said, I have recently been worried about my skills and have been working hard to be sure I'm keeping fresh. I used to get hung up on design, but lately I realize I can code up a horrendous site but 100% functional site, and make it look pretty later - saving myself hours and hours of work. Also, I'm working on writing tests so that I do not spend much time tracking down regressive bugs. It's amazing how useful a comprehensive test suite is to determine your next task, ensuring that you regularly press forward.