On the timeline presented there is a framework called ServiceStack[0] which I successfully used to significantly simplify internal APIs, used by multiple internal systems, back in early 2011.
Recently we brought on a new developer whose first question was "Why didn't you use Microsoft's WebApi". I had to gently explain that I couldn't use something that didn't exist. So I definitely feel the author's pain.
I wish I had a good answer, but what I do is point out why we are using what we are using. When we have a disagreement about this kind of thing my way usually wins because I'm the team lead, but I wish that weren't the deciding factor in most of our tech choices. I let that particular coworker use the MS stuff on small internal tools type projects, but when it comes to longer term stuff, or things that are more central to our company, I will push for the solution I think is best.
6 comments
[ 3.5 ms ] story [ 25.5 ms ] threadRecently we brought on a new developer whose first question was "Why didn't you use Microsoft's WebApi". I had to gently explain that I couldn't use something that didn't exist. So I definitely feel the author's pain.
[0] - https://github.com/ServiceStack/ServiceStack/wiki