InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Presentation: Social Programming A Pyramid

Posted by Abel Avram on Feb 19, 2009

Sections
Architecture & Design
Topics
Architecture ,
Module Systems
Tags
Large Projects ,
OOPSLA ,
OOPSLA 2008

In this presentation filmed during OOPSLA 2008, Mark Lehner, an Egyptologist, talked about ancient Egyptian cultures as seen through the discoveries made on the Giza Plateau and made some connections with software engineering.

Watch: Social Programming A Pyramid (1h 30 min.)

ZA, a hieroglyph representing the cattle’s four legs tight together by a rope. It was traduced by ancient Greeks with “phyle” which means “tribe”. They represent “a social unit that seems modular, replicable, which you can encapsulate in larger organizations.”

There are similarities between Egyptian work organization and software. A phyle was made up of 200 men or 20 men according to other sources. There was hierarchy with a commander over a phyle, and a higher commander over 5 phyle commanders. There also was encapsulation, each phyle being able to perform their own set of tasks without needing the help of others. Modularity was expressed by having separate phyles for the 5 different types of tasks. Polymorphism was manifested by using the phyles for different types of projects: temples, boats, pyramids.

Lehner’s presentation continued with their search for the “great city” buried beneath the sand. It was supposed to be a city inhabited by pyramid workers, and the findings showed life sustaining elements like a bakery. A bakery would have fire places where the bread was baked and a number of vessels used to prepare the dough. In order to feed an estimated 20 to 30 thousands people, they had to scale and they did that not by creating one large bakery, but rather replicating the small one into many placed into close proximity.

In the rest of the presentation, Lehner’s talked about uncovering the great city and in the end answered questions from the audience.

Great insight by Mouneer Rabie Posted
  1. Back to top

    Great insight

    by Mouneer Rabie

    thanks for the great presentation.
    I live 30-minutes drive from the great pyramids; now when I visit the area next time, things will certainly look different; also when I help building a piece of software, my perspective will also be diferent.
    Mark, if you will be reading the comments here, and whenever you are in Egypt next time, I will buy dinner :)

Educational Content

Jesper Boeg on Priming Kanban

In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.