βρυκόλακαςαλχημιστής ‏@bitemyapp Mar 22

@balajis you can avoid the necessity of specific examples if you understand the general principles of what is and is not kosher.

βρυκόλακαςαλχημιστής ‏@bitemyapp Mar 22

@balajis to cherry-pick a near-at-hand example, the Monoid. "empty" and a binary associative operation. Definitionally. Delimits the API.

βρυκόλακαςαλχημιστής ‏@bitemyapp Mar 22

@balajis leveraging both positive and negative space for design is necessary for excellence.

Balaji S. Srinivasan ‏@balajis Mar 22

8/Reinventing agriculture? Build new kind of farm, w/ solar panels & self-driving tractors. Control all factors, show that code cuts costs.

Jordan S. Terry ‏@The_Analyst Mar 22

@balajis how are we going to re-employ all the low-cost manual labor/repetitive-task folks when they're replaced with technology?

Balaji S. Srinivasan ‏@balajis Mar 22

10/By doing it end-to-end, you see things. First, sometimes a good reason beyond tradition (eg regulatory, logistical) for legacy practices.

Dan Farfan ‏@DanFarfan Mar 22

@balajis Well, you can’t do those things WELL until .. what you said. ;-)

Balaji S. Srinivasan ‏@balajis Mar 22

11/Second, your control of adjacent layers may eliminate the initial problem you were trying to solve. Analogous to: http://en.wikipedia.org/wiki/Telescoping_series …

Dan Farfan ‏@DanFarfan Mar 22

.@balajis Another reason for N2N, you better realize the info model that everyone believes rules, constrains all from breakthroughs

Balaji S. Srinivasan ‏@balajis Mar 22

12/Third, solving whole problem builds respect in your vertical. Now you can recruit best people. Their experience + your code = invincible.

Balaji S. Srinivasan ‏@balajis Mar 22

13/Fourth, your margins improve nonlinearly once you control the full stack. Simply having all orders in DB from day one is transformative.