Skip to main content

Economy Lessons

Stumbled upon some words that I couldn't translate from the passage below:

"The ancient policy of Europe was, over and above all this, unfavourable to the improvement and cultivation of land, whether carried on by the proprietor or by the farmer; first, by the general prohibition of the exportation of corn, without a special licence, which seems to have been a very universal regulation; and, secondly, by the restraints which were laid upon the inland commerce, not only of corn, but of almost every other part of the produce of the farm, by the absurd laws against engrossers, regraters, and forestallers, and by the privileges of fairs and markets." - Adam Smith, The Wealth of Nations.

"Engrosser" - one who takes the whole; a purchaser of such quantities in a market as to raise the price; a forestaller.
"Forestaller" - A person who forestalls, especially one who buys goods before they can be sold on the open market in anticipation of rising prices.
"Regrater" - 1: one that regrates supplies or necessities; b: a middleman who travels about the country buying up farm produce for market; 2: one that gets profits or credits due another esp. by irregular means
Labels:

Comments

Post a Comment

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 .
Post a Comment
Read more

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
Post a Comment
Read more

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
1 comment
Read more