Quote:
Originally Posted by kgun
That is called: - Minimalism.
- Kernal activity.
- Outsourcing.
David Ricardo called it " The principle of comparative advantage aobut a century ago and said that Norway may have a natural advantage in producing dried cod, while Brazil have a natural advantage in producing fruit and wine. Portugal may have a comparative advantage in producing wine, while England has a comparative advantage in producing cloths (now that is China). |
I'm sure that your explanation is correct but I was not talking about minimalism, kernal activity or outsourcing. Far from that. Those are completely different things. That's just trying to keep costs low through focusing.
Keeping things simple, to me, is more about not making things more complicated than necessary. Some simple examples:
- Don't create procedures for something simple like giving a new employee an email address. Just tell the guy that does this a new email address needs to be set up.
- When having to create optimized titles for a website, don't put them first in a word document so that later they can be added to the webpages. Just put them straight into the pages.
And on a more technical level:
- When building an optimized tableless HTML template for a website, don't create a CSS file of 1000 lines. Use the hiearchy of CSS to prevent having to redefine styles over and over again.
And on an analysis level:
- Always go for the most simple explanation, it's usually the correct one.
- Don't try to find relations between details, but try to understand the higher level goals through details. Don't explain through details, try to understand the objectives of why the details were created. Look at the details, go up in the hiearchy to explain,.. then go down again to understand why something somewhere was done. (this one is hard to explain, but it's what I do...
)