It turns out that the organization that prided itself on beating the CIA in his ability to get stuff done for a fraction of the cost got hacked through the most benign means possible.
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 $.
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,
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 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
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.
Among the most prominent themes in the Hebrew Bible are the concepts of sin, punishment, repentance, and restoration. Chapter 28 of the book of Deuteronomy, known as the “blessing and curse”, makes it abundantly clear what the rules of the game are. Follow the law and you will enjoy fantastic entrepreneurial success and overflowing prosperity, disobey it, and you’ll be punished with the worst forms of war, exile, anarchy, and poverty.
So if you have been suffering from recursive algorithmic nightmares, or have never fully understood the concept of algorithmic efficiency, (or plan to interview for a position on my team), here is a short and concise primer on the subject.
To hit the market early and within budget, your feature development strategy must focus on creating the bare essential functionality. So in this vein, you should make it prove itself to be a “worthy survivor”. Your features need to be tough, resilient, and lean. I have come to embrace the U.S Navy SEAL’s “hell week” screening approach before letting any one of them into my development cycle.
It’s romantic to view the world as a wall, scaled heroically by pure self-esteem. But in complex endeavors you’re certain to fall, without the support of a team.