The following are proofs that I've got great eyes for technology tools (A.K.A, I'm not your cheap-ass tech dude!):
Yesterday, we had some folks from Microsoft came around to discuss with my development team (Quickteller team) about Windows Azure Notification Hub. It went so cool that the Quickteller product manager concluded on the spot that we were going to use it and started wondering why we hadn't adopted Windows Azure since.
I felt great!
Having used Windows Azure for Tiketmobile for almost two years now (since 2012), I'm the most experienced Windows Azure developer in my team. But that's not why I felt great. I felt great because, being responsible for the technology decisions on Tiketmobile, I had seen the prospect of Windows Azure and adopted it for our product. Even then, it was against the advice of our supporters, who suggested we go with Rackspace or AWS, because everyone in the hub was using those. Also it came with little local support... in fact, when we first started using it, it wasn't even available for Nigeria yet. I had to figure-out a lot of things, including roping-in PHP to the Cloud Service, from Visual Studio.
I'm glad that that skill of mine won't suddenly get redundant after all... Well, I would have used it during my nightshift anyway!
My CIO shared a professional report with TechQuest yesterday which listed the frameworks that are in-vogue for developing web applications in Java, with their pros and cons, using several metrics. On the top 3 was Play! Framework. Vaadin was first, Grails was second and Play! was third.
Apart from me wondering why the fuck I hadn't heard of Vaadin before yesterday, I also felt great because, when I move to my nightshift (which is every night, after my 9 to 5), I'm mostly hacking off on Play! Framework... with Scala programing language though, not Java.
CIO (of life!) also shared a great article about Reactive Application Development, which argued that it wasn't just hype, but would help applications better handle stress/load. I had earlier tried to bring-up the discussion of reactive programming with some of my colleagues, as a means of better understanding it, being a learner myself. Reception wasn't so great, so I relaxed my learnings to my personal space and when I'm on my nightshift.
I guess this is a little blessing of some sort to talk about how TechQuest could adopt Reactive app development in our methods... even if it's only talk we talk about it. Understandable, old systems might not need to be touched, I mean, why fix something that isn't broken? But new systems could benefit from the new cool ;)
Alternative title of this post:
Why it pays to have a CIO who's in-vogue (A.K.A hippie CIO aiye!)