Simplifying Code

Simplicity and ease of use is required to build this stack.

So how do you build ‘stack simple’?

Two forces compete:

  • One trouble is making things that people then have to learn rather than just using POCO.
  • The other trouble is using POCO only, does not build the stack.

(how to resolve this dilemma) – one way it to have a usable debugging scope at each level of the stack.


Try to use fewer mechanics in a program:
Mechanics include:

  • Views
  • Tables
  • Stored Procedures
  • Functions
  • Web Services
  • Frameworks
  • Enumerations
  • Dynamic SQL
  • SQL query construction inside .NET
  • Abstract tables
  • Services
  • Abstract classes
  • Inheritance
  • Delegates
  • Linq
  • Lambda calculus
  • Events
  • Master pages
  • MVC
  • etc.

These are all useful, but try to reduce the number of them you use. Remember, the goal is artificial intelligence. It is the whole point of simplifying. One mechanic – When one mechanic could replace more than one without adding much complexity, switch to using one mechanic.

The Stack is the Thing

As we are building This Stack, it makes sense to keep our eyes on the prize.

Does it make sense to keep rewriting programs?

Does it make sense to have programmers fiddling with UI details rather than building the next layer?

Does it make sense for programmers to focus their attention on learning more and more new and old technologies rather than figuring out how to build this stack?

There needs to be some balance.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s