Skip to main content

Economy Lessons - Value


Interesting indeed:

"A rich country, in the same manner as a rich man, is supposed to be a country abounding in money; and to heap up gold and silver in any country is supposed to be the readiest way to enrich it. For some time after the discovery of America, the first inquiry of the Spaniards, when they arrived upon any unknown coast, used to be, if there was any gold or silver to be found in the neighbourhood? By the information which they received, they judged whether it was worth while to make a settlement there, or if the country was worth the conquering. Plano Carpino, a monk sent ambassador from the king of France to one of the sons of the famous Gengis Khan, says, that the Tartars used frequently to ask him, if there was plenty of sheep and oxen in the kingdom of France? Their inquiry had the same object with that of the Spaniards. They wanted to know if the country was rich enough to be worth the conquering. Among the Tartars, as among all other nations of shepherds, who are generally ignorant of the use of money, cattle are the instruments of commerce and the measures of value. Wealth, therefore, according to them, consisted in cattle, as, according to the Spaniards, it consisted in gold and silver. Of the two, the Tartar notion, perhaps, was the nearest to the truth." - Adam Smith, The Wealth of Nations

Comments

Popular posts from this blog

Wine - 2011 Brown Brothers Crouchen Riesling

Very nice wine with fruity taste - peach and pear: Consumed with Hungarian salami. Tasting notes .

Scrum - Team Culture and Wall Manifesto

In the Scrum framework one of the key components is the wall and daily stand-up. In some organisations I worked with the whole concept of the wall is not accepted by many developers, because of the stand-up necessity and "time waste". Very often all that methodology is used for the sake of methodology and not to achieve what we actually do - adding or creating value to our customer (usually called "The Business"). I can understand frustration that is caused by the wall and stand-up process. From the software developer perspective it is really a waste of time for the following reasons: 1. In 95% of cases developers are head down working like hell delivering valuable outcomes that they are accountable for. Extra effort to go to the wall, staying there for 15-30 minutes and listening or not listening to what others were doing yesterday and will be doing tomorrow is annoying for them; 2. The mere fact of having to do something mandatory to do that looks like

Mastering The Multitasking

There is usually two distinct perspectives on multi-tasking: 1. Multitasking is counterproductive. We get distracted by multiple tasks that all get our way and fight for our scarce attention, time and resources. This leads to a common fallacy that if you do multiple activities “at a time” you are not doing good work in any of those. 2. Multitasking is a way of getting many things done in a short period of time or in a long run. Indeed it can be either a disaster or a great helper depending on how it is used and practiced. Most recent research shows that we don’t do multiple tasks purely in parallel or simultaneously. That means we don’t purely multi-task, but switch between tasks and execute them one at a time, but by spending very small timeframes on each task. A good example from the history is a story about Julius Caesar capabilities in that area. Plutarch writes, “Caesar disciplined himself so far as to be able to dictate letters from on horseback, and to give directi