stillhacking

I think it was back in March that I first blogged about DropWizard .  DropWizard is one of those funny technologies that I find falls into the category of sometimes making folks uncomfortable.  This usually initially comes off as looking down upon unconventional solutions but if you can have a conversation about it there may be something more. Sure there are organizations full of folks who won't discuss anything that's either "not supported" or even slightly off the beaten path.  It's not always part of the reason but it's worth keeping the "resume padding" factor in the back of your mind when having these discussions.  The other thought from days gone by is the "No one ever got fired for recommending ____________" (fill in the blank with your favorite currently popular and profitable software giant). The last time I blogged about DropWizard it was still new to me but I got it pretty quickly and I think you will too if it fits your use ...

Not too long ago I was catching up on some Java Posse episodes and I came across the Dot War (what is it good for?) episode. This episode, recorded live at the Roundup, was not what I expected.  Maybe I was not paying attention before I started listening but I thought a Java/.Net discussion was coming.  Instead I was pleasantly surprised to hear the guys talk about container-less application development. Initially I was not so much interested in using any particular technology among those discussed.  It was the idea that we should not necessarily build software using a specific pattern, framework or technology because it's popular or because we know it (insert "hammer-nail" analogy here).  We should, as we once said, do some analysis and design work (a little learning is not a bad idea). What first came to mind was that portion of the software development heritage which took us from single user applications to the internet.  Roughly speaking the single u...