Tuesday, April 24, 2012

The organic project

You can have a inorganic projects. It has a deadline, and once deployed nobody touch it.
Maybe some maintenance and bux fixes there and here but that's all.
The environment does not change it over time.

It happens, and the objective is to freeze the code and make it works perfectly for this specific date.

I call parts of the project fixed in advance by an architect a conscious architecture.

However entrepreneur must work on another concept : the organic project.
It have deadlines, but it cannot have a conscious architecture.

When you start your own project, you never know as a CEO how it will evolve once in the hand of your customer. The fog will dissipe with time, but now you are blind.

If you are a CEO, how can you expect that your architect/developer knows better than you what to fix in stone ?
If you are an architect, how can you know better than the CEO what to fix in stone ?

Consider your new project as an organic project, it will  move forever, don't set things in stone yet, ship, pivot and evolve, make your product grows organically.
Your architecture will emerge organically from environment's input.
I call it the organic architecture.

Facebook did not have a guy from the start that said : "Ok, we'll make things scalable for unlimited number of users."

It became scalable with an organic growth of the codebase, one problem after the other, one refactoring after the other.

Be smart, don't forsee, just improve a bit the life of someone. One line of code at a time.
When you start your biggest ennemy is not bad code.
It's wrong product.

No comments:

Post a Comment