Vision: What does success look like? Humanity: What do you need to succeed? Process: How do we ensure everyone gets what they need?
Wide Open (or, Are You In?)
He's my hero. THIS is how I dream of running my own projects / company.
This is Probably a Good Time to Say That I Don’t Believe Robots Will Eat All the Jobs …
The mechanics of jobs will be automated, which is why the jobs of the future will rely on us being more human to each other.
How to Have and Resolve An Argument
Premise We hold certain positions because of what we: A. Experience -> B. Encode -> C. Evaluate -> D. Emphasize -> E. Express Corollary If someone disagrees with us, it is because they differ from us in one of those five areas, aka: A. Facts -> B. Definitions -> C. Reasoning -> D. Values - > E. Style Implications... Continue Reading →
The Multi-Minion Machine
A Function of Scale Draft 1, Ernest Prabhakar, 2013-08-08 The Sequel to "The Minion Machine" The Premise Real systems aren't linear, but have scales where the cost is fixed below, but astronomical above. The Goal Extend/Restrict the Minion Machine to capture what it means to operate at "optimal scale". The Concept Define a Multi-Minion Machine as a... Continue Reading →
The Minion Machine
The Action of Complexity Draft 2, Ernest Prabhakar, 2013-08-07 Inspired by a proposal from Christy Warren The Premise Using concepts derived from physics such as Energy and Time, we can gain insight into the nature of computational complexity. The Goal Devise the simplest possible physical system that captures the aspects of computation relevant to complexity... Continue Reading →
Summary: Retrospective Thoughts on BitC
In my opinion, BitC is the most innovative take on systems programming we've seen since the invention of C. While sad that it failed, I am deeply impressed by the thoughtful post-mortem by Jonathan S. Shapiro. Here are links to the various threads of his analysis (and the equally thoughtful responses): [bitc-dev] Retrospective Thoughts on BitC... Continue Reading →
RIBS: Marrying the REST and MVC Design Patterns
[Diagram updated on 10/27. Thanks to @frozencanuck for his feedback.] The RIBS diagram is my third attempt to extend the wildly-succesful Model–View–Controller design pattern to encompass first the The DCI Architecture and now the REST architectural style. This time, I started by reverse-engineered the design principles behind the Ki Statechart Framework, particularly their use of statecharts as coordinating controllers.... Continue Reading →
SIDA: Moving Object-Oriented Design beyond Model-View-Controller
[Update: this post has been obsoleted by RIBS: Marrying the REST and MVC Design Patterns « iHack, therefore iBlog] SIDA stands for "State • Interface • Data • Algorithm", and is a refinement of my earlier "DIDA" model (where the "D" stood for Design). DIDA in turn was an expansion of the well-known Model–View–Controller design pattern based on... Continue Reading →
DIDA: Reinterpreting MVC object modelling in light of DCI
[UPDATE: This post has been obsoleted by SIDA: Moving Object-Oriented Design beyond Model-View-Controller] I recently read about The DCI Architecture: A New Vision of Object-Oriented Programming, a successor/complement to the original Model–View–Controller design pattern, by one of the original authors. The DCI stand for: Data Context Interaction I was both impressed and confused. Impressed because I've been thinking for... Continue Reading →
iHack, therefore iBlog 
You must be logged in to post a comment.