You're looking at Less Wrong's discussion board. This includes all posts, including those that haven't been promoted to the front page yet. For more information, see About Less Wrong.

cameroncowan comments on Open thread, Nov. 10 - Nov. 16, 2014 - Less Wrong Discussion

3 Post author: MrMind 10 November 2014 08:32AM

You are viewing a comment permalink. View the original post to see all comments and the full post content.

Comments (194)

You are viewing a single comment's thread. Show more comments above.

Comment author: cameroncowan 13 November 2014 09:24:47PM 0 points [-]

Unless from the beginning you create the system to accomplish a certain number of tasks and then work to create the system to complete them. That can mean creating systems and subroutines in order to accomplish a larger goal. Take stocking a store for example:

There are a few tasks to consider:

  1. Price Changes
  2. Presentation
  3. Stocking product
  4. Taking away old product (or excess)

A large store like Target has 8 different, loosely connected teams that accomplish these tasks. That is a store system within a building of 8 different subroutines to create a system that, if it works at its best, makes sure that the store is perfect stocked with the right presentation, amount of produce and the correct price. That system of 8 subroutines is back up by the 3 backroom subroutines that create the backroom system that take in product and make it available for stocking and that system is backed up by the distribution center system which is backed up by the transportation system (each truck and contractor working as a subroutine).

These systems and subroutines are created to accomplish one goal and that is to make sure that customers can find what they are looking for a buy it. I think using this idea we can start to create systems and subroutines that make it possible to replicate very complicated systems without losing anything.