20131218


Some thoughts, links and tutorials I used in my quest to build an MVC WEB WEB API With EF Framework
 Date:   Wednesday, January 30, 2013 10:44 AM


Tutorials:
Here is a nice, clean tutorial on MVC and EF (NOT with WEB API!!!):

http://www.itorian.com/2012/08/code-first-approach-in-entity-framework.html#.UCZ4Op0gd94

MSDN Tutorial on code first (Familiarizes you with Migrations, Data Motion, and custom SQL):

http://msdn.microsoft.com/en-us/data/jj591621.aspx

 And here is a database first tutorial (Again, NOT with WEB API!!!):

http://www.c-sharpcorner.com/UploadFile/abhikumarvatsa/database-first-approach-in-entity-framework/

**** Actual EF Code First WEB API Tutorial by Jason Zanders (Microsoft all star):

http://blogs.msdn.com/b/jasonz/archive/2012/07/23/my-favorite-features-entity-framework-code-first-and-asp-net-ewb-api.aspx

View and Layout Information/Tutorials:

http://www.asp.net/mvc/tutorials/mvc-4/getting-started-with-aspnet-mvc4/adding-a-view

 Configuring ASP.NET WEB API - routing, global, service, per-controller configuration(Media Types, parameter binding, etc…) Tutorial and info:

http://www.asp.net/web-api/overview/extensibility/configuring-aspnet-web-api

 
WEB API Dependency Resolver (Dependency Injection) (Volatile Interfaces)

http://www.asp.net/web-api/overview/extensibility/using-the-web-api-dependency-resolver


REST API vs RPC API - overview, best practices, and design articles:
***Josh Reuben - ASPNET WEBAPI REST *** EXCELLENT ARTICLE on best practices considerations:

http://geekswithblogs.net/JoshReuben/archive/2012/10/28/aspnet-webapi-rest-guidance.aspx

http://encosia.com/rest-vs-rpc-in-asp-net-web-api-who-cares-it-does-both/


Web API Testing Links:
http://blog.jonathanchannon.com/2012/11/29/asp-net-web-api-testing/


Routing and Route Constraints for ASPNET and WEBAPI:
http://www.asp.net/mvc/tutorials/controllers-and-routing/creating-a-route-constraint-cs

IoC: 
I abandoned NINJECT IoC Containers for dependency injection after experiencing numerous problems.  I decided to go with Microsoft Unity as outlined here:

http://www.asp.net/web-api/overview/extensibility/using-the-web-api-dependency-resolver

Instead of using the ASP.NET Unity Web API package, I used the new Unity MVC4 package via NuGet.  This worked extremely well and was much less cumbersome to implement.

ID Server:
Thinktecture ID Server: I'm still playing with this, but hav not yet put anything up into a production setting.  A good video outlining the basic steps in setting everything up:

http://vimeo.com/51088126

Other Notes:
StackOverflow comment regarding MVC-WEB API and EF

http://stackoverflow.com/questions/13408659/build-asp-net-application-with-web-api-and-database-first-strategy


Get the EF Power Tools from Microsoft (Very Useful!)

http://blogs.msdn.com/b/adonet/archive/2012/04/09/ef-power-tools-beta-2-available.aspx

If you run into connection and/or connectstring issues:

http://stackoverflow.com/questions/3218208/entity-framework-v4-code-only-connection-string

http://stackoverflow.com/questions/689355/metadataexception-unable-to-load-the-specified-metadata-resource

20131125

IoT, APIs, Apps and the morass of our present

So I've been spending an inordinate amount of time contemplating the current morass of software, apps, APIs, mashups, data protocols, and such out there in the Ether that are applicable to my industry (insurance).  For the past year I've been focused on learning as much as I can regarding BYOD, app stores, mobile, SaaS, PaaS, Cloud, APIs, Mashups, etc... and I've come to the view that this whole thing is quickly becoming an imbroglio for us all. 

Consumers have a plethora of options available to them and that is great.  Despite the fact many of us struggle with the volume and variety, I still largely consider this volume of choice to be good, not bad.  Everyday introduces new and interesting solutions to help us manage the ever growing number of apps and solutions we desire. 

And yet, for every new Cover App, a dizzying array of new Apps are brought to market each day. Each with their own idiosyncrasies, inconsistencies, and contrivances. For anyone who's been paying attention to the unfolding events in the technology universe comes the realization that we are fast approaching the cusp of a catastrophe.  The unwieldy volume of information and interfaces available through the ever-increasing multitude of vertical solutions, components, etc..., is out-pacing any one individual or organizational ability to keep up.  Further, the divergence of standards across App and API offerings makes interconnection optimization nearly impossible.

This past week while reflecting on the chaotic state of affairs we are facing, a colleague shared an article via LinkedIn by  regarding her musings on IoT and the complexities of vendor lock in when concerning the Smart Home.  I chuckled as I nodded in agreement while comparing her thoughts to my own regarding the insurance industry and the complexities faced in developing innovative new technology services for our customers.

 As Stacey astutely surmises: "The key question so far is: Is the connected home going to be a vertically integrated Apple-like ecosystem or an open system where data flows freely between devices in the cloud?" - Stacey Higginbotham 

This question takes on increased urgency and meaning when you look at the situation from the enterprise IT perspective.  The multitude of disparate vendor solutions available quickly overwhelms even the most tenacious of us.  Considerations of discoverability, interoperability, openness, algorithmic consistency, manageability, and  incalculable technical considerations/risks paint B2B technology purchasing and implementation decisions in an entirely new and worrisome light.



Sites such as Programmable Web, the Google Play Store, and Code Academy are making good faith efforts in making information available in an organized and meaningful way, yet the volume of innovative information and application offerings is outpacing their ability to keep up.  And let's face it, even if they could keep up with all of the publicly available APIs and/or Apps offered, their libraries are not going to help me with APIs available for my industry that are not publicly shared, nor are they necessarily going to provide me information on the latest Apps available to replace members of my current App stable. 

What's more, I doubt any solution currently available can tell me how the earned premium KPI calculation varies between MyFavAPI and MyOtherAPI, something I need to consider if I'm building solution bridges across verticals, and feeding a SaaS analytics solution expecting a specific approach.  Solutions such as Google Play Private Channel are a good start, but far, far from complete.  Industry needs much more.  Heck, I don't even know if the date format being provided from MyFavAPI is going to work seamlessly across all the devices I intend to support with Apps from our internal App store. 


And there again... just what devices am I supporting?  How many different code bases do I need to support to bring my RESTful API-enabled mobile App to my customers?  Am I really going to support 5-10 codebases to satisfy the 95th percentile of users and their devices in an austere era and deflationary budgets?  What if my best customer's device choice falls outside that percentile?  I read and his thoughts on the matter.  He has some interesting insights there from a technological perspective.  I'm not going to guess as to whether HTML5 becomes THE solution to our App management problems, it is too soon for such prognostications.  But I will state that the current hap hazardous approach is not sustainable.

So why are you reading this blog?  What do I suggest as a solution?  Well, I'll start by admitting that I'm not sure.  I've flirted with the idea of taking a step back in time when we talked about "industry standards" and attempt to apply such concepts to the problems of the day.  I've considered suggesting the creation of a "single source of truth" for our particular industry.  A clearing house if you will.  Perhaps an independent organization whose primary function would emulate that of the Programmable Web, yet specific to the industry.  Folks like Novarica try to fill this need through consultation services, and they are an extremely talented group.  There are inherent difficulties in outsourcing strategy development, which is what we are talking about here.  And while Novarica and the like offer some great services to the industry, I've yet to see anything like the "Programmable Web and App Store for the Insurance Industry" come from them, at least not yet.

So I close with the typical set of questions:  What do you think?  How does business navigate constant change and keep themselves ready to seize opportunity with so much tumult?  Would an independent organization whose focus would be providing a library of information and insight to industry specific technology considerations be redundant or just what is needed?  Is the "Programmable Web and App Store for the Insurance Industry" necessary or superfluous?  Could Novarica or other such service providers fill this need?

Just My Thoughts... I welcome yours...

20120630

Be a tree, not a rock

I've been struggling for a while now on what my first fleshy topic should be about... 

Did I want to confront the collaboration problems in the modern enterprise?
Did I want to talk about the IT/biz divide and how to overcome it?
Should I just dive into a tech-heavy how-to on Hadoop or SharePoint?
Should I go into some long diatribe about the P&C insurance industry and all the problems it has?
Or should I just get my feet wet with a review of one of the recent seminars, summits, articles, or webcasts I've recently experienced?

With so many options, and so little experience writing blogs, one quickly becomes mired in the decision-making trap.  So I waited... and waited... and waited.  It was sometime after the 2nd month of no content on my "new" blog that I realized I was never going to be a good blogger.  I don't have what it takes:

  • I'm lazy by nature - I'm always looking for the most efficient way to get something done, and rarely do I bother to document all the things I do.
  • I'm not very good at writing - I tend to overuse commas, and misuse other characters in favor of attempting to emote a feeling(!) or express some communicative construct such as time passing(...).
  • I'm and extremely unfocused individual -  I've been accused of having ADD by my loved ones, and quite frankly I think they are right. 
  • I get bored easily - Once I figure something out, I'm moving on to the next big thing.  Rarely do I want to actually have to put in the more mundane hands-on efforts required in implementing sophisticated enterprise systems. Not to say I can't or that I don't, for both would be untrue. Its more that I'd prefer not to.  I'd rather pass those efforts on to someone who enjoys the detail work. Of course that's not always possible, so every now and then I actually have to create something pretty cool.  Hmmm... maybe I can do this blog thing...

So what I decided was enough was enough.  No more waiting... poor grammar and all, I'm going to put something out there and let you people decide if I should continue or not, if what I have to say is valuable or not.  I'll let you decide if I "have what it takes" to draw you in, and keep your interests. Or if I should pack it in and go back to my usual quiet.

So with all that behind us (permanently I hope!), Here is the first thought I wanted to share with you:


Be a tree, not a rock


I remember growing up and having to continually be faced with the references to our pop culture fascinations with rocks.

I used to hear people talk about how he/she was "rock" for his/her family.

People would always talk about how he/she was a "rock-solid" individual.

People were enthralled with "rock stars" and "rock and roll".

The cars and trucks we were told to buy had to be "Like a Rock".

and on, and on, and on...

 Well... I've thought about this and decided that a rock is not what we should choose to be.  This whole fascination with rocks needs to end.  A rock is static.  A rock is inflexible.  A rock does not move nor does a rock change without external force and pressure. A rock is not very colorful (well OK, some rocks are quite colorful, but most are boring, bland things with little aesthetic charm beyond being a rock. Am I stereotyping here?  Perhaps. But I'm betting on not offending the rock population severely enough to warrant legal action). Rocks are generally inert.  Quite simply, rocks should NOT be emulated.

If we insist on objectifying ourselves, let it be through something worthy of our uniqueness. The human spirit is the most beautiful of things.  Indomitable and implacable, the human spirit perseveres through strife and conflict.  Humanity rises to meet challenges, is undaunted in the face of impossibility, resilient in the face of defeat. We are strong without doubt, yet within us exists the ability to rationalize and empathize. We are not so rigid as a rock.  Trees on the other hand... trees are remarkable things, worthy of our emulation.


The characteristics of a tree align well with the best attributes of humankind. Some thoughts on trees:

  • Strong yet flexible, a tree is unyielding in the face of a storm, yet a tree will bend to the wind without concern for pride and ego.  A characteristic many humans can embrace for their betterment.  Be firm in your values, yet allow yourself to bend to the wind, be flexible, and accept change as inevitable.
  • From its first days, a tree will grow every day, and never stop growing until its last day. Each day that passes provides you the opportunity to stop, to quit, to be nothing beyond where you currently are. It is easy to be a rock.  Being a tree is more difficult.  Growth is more difficult, but quintessentially human in nature.
  • A tree produces oxygen, and removes carbon dioxide.  I've known many individuals who seem to have the exact opposite capability... nonetheless I posit it important to add value to your world instead of commandeering it.
  • Trees are prolific. They are a wellspring of fruit and progeny. Humans have such capabilities within them, if allowed to flourish in their environment. A human who goes forth into the world openly and honestly, spreads their seeds of knowledge and insight unhindered and unencumbered by the world itself.  Be prolific and share.

There are so many other unique and wonderful attributes of trees one could associate to the machinations and elements of human nature an entire book could be written.  Alas, this is not my goal.  I've far too many interests, and am far too unfocused, to spend a year or two writing a book about trees and their relation to human sociological and psychological constructs. My goal is to get you to see the value in trees, to worship trees(OK that's over the top) and think differently in regard to your role in the world.

 So to keep true to the description of this blog, and relating this blog back to technology, business, or strategy, I say be a tree, and not a rock in your dealing with people everyday.  A strategy born from collaborative thinking, sharing, and mutual dependence, trust and values will inevitably be a winning strategy for you, your firm, and your colleagues.  Open up, be unafraid to share your ideas, be creative and thoughtful, ask questions, answer questions, COLLABORATE & GROW! 

COLLABORATE & GROW!  These are our Trees of Valinor.  Humankind will not advance if we all retreat to our islands and shut ourselves off from the world. We must be willing to take a chance and put ourselves out there.  We must be willing to listen and change when called for. We must seek out change, grow, and help each other grow.  We must lower our egos and cast aside our self importance.  Each tree ties itself to the axis-mundi for certain, yet it is through the overlapping and intertwining root system that true understanding can be achieved.  Emulating trees bring us all closer to that central point of being.



20120402

First Blog!

Hello, Bernie K. here.  Long time techie/geeky type who's been working in the Insurance sector for most of his professional career.  I've spent the last few years in IT management, trying to be a "strategic thinker".  I've had some successes, some failures, and a lot of fun.

I have, for a long time, contemplated starting a blog. Somehow I always came up with an excuse why not to do it.  Well, no more. I've got a good bit of experience and some insights to share. Its time I quit keeping my thoughts to myself. It may be this blog is never read by anyone, or it may oneday become a huge success. I have no idea, and that is not what is driving me to do this.

I'm not sure what precisely I'm going to blog about... but the near term plan is to discuss stuff in the open air that add value, trouble me, provide reason to think, or lend themselves to making business a more effective vehicle for social and economic change.

I want to share my thoughts and expand my thinking through participatory discussion.  I've been a vocal advocate for team-based approaches to business problems for my entire career.  I still am.  Now I want to take that philosophy to its natural next level, and expand the universe of people with whom I can interact with and gain greater perspective.