Choosing Between Schedule, Budget, Scope, and Quality
Argumentum ad populum is that the best way to beat your competitor is to one-up him. If he has 2 features, you need 3 (4 would be even better). If he is budgeting 1 x $ on his solution, you need to spend 2 x $.
The API Train Wreck Part-2
In The API Train Wreck Part-1, I discussed API design factors such as KPI, performance measurements, monitoring, runtime stats, and usage counters. In this posting,
The API Train Wreck Part-1
Developing a commercial grade API wrapper around your application is not a trivial undertaking. In fact, in terms of effort, the development of an outbound
To ESB or not to ESB is the question. Or is it more noble to just ETL it?
To borrow a metaphor from Winston Churchill, for the mere mortal, the selection of application/platform/enterprise integration tools, is often “a riddle wrapped in a mystery
In Crowds We Trust
By the end of the first day of deliberations, the majority of the jurors decided to go with “First Degree Murder”. I argued that I couldn’t find a willful and premeditated intent to justify First Degree murder verdict. I also pointed out that from all the facts presented to us, it was clear that the “victims” were armed, had a history of violence, were wearing their “colorz”, and from the video footage, it seemed that they were itching for a “Gunfight at the O.K. Corral” style shootout.
Driving the Message
From an evolutionary point of view, it seems that the quadrant 1 and 3 messaging mediums (see chart) represent a form of r/K selection classification. Each trades between quantity and quality. The focus in quadrant 1 is to increase the quality of the content with higher expense per message. The focus in quadrant 3 is to increase the quantity of the content with a corresponding reduction in quality and lower expense per message.