636 karma · joined March 20, 2008
-I agree with the parent remark. You can't even give someone a link to a project.
-The Purchase and Ownership sections of the EULA are a bit odd.
-Discoverability of projects is poor.
-Interest tags seem a bit random. I want to add programming to my profile. What do I pick? programming? web dev? X language?
Here is an interview he did a while ago which go trough his work : http://www.budiu.info/blog/2007/05/03/an-interview-with-lesl...
* The law is inconsistent and possess contradictory rules. From contradictory premises, sound arguments
* It gives concrete examples of legal cases and how completely opposite judgments could be rendered, both being based on correct use of laws and analysis.
* Laws are not applied impartially, are not neutral, apolitical nor objectively applicable by judges. People who believe they live under "a government of laws and not people" tend to view their nation's legal system as objective and impartial. Obey and subject themselves.
* There is a cognitive dissonance between the laws and the people who make them. People generally believe that the law are generally good and should be obeyed. People generally believe that politicians tend to be corrupt and influenced. The people who make the law cannot be trusted but yet the laws they write should be.
6.2. User Interface RECOMMENDED
A user agent that implements Do Not Track SHOULD provide a user interface
for modifying preferences. The user interface design is left to the
user agent.
6.3. Default
A user agent MAY adopt NO-EXPRESSED-PREFERENCE or OPT-OUT by default.
It MUST NOT transmit OPT-IN without explicit user consent.
"The Counter-Strike developer has previously bragged its engine is "considered the most flexible, comprehensive". I hope it was a reference to the new engine and not the existing one which is fairly painful to work with. Hello map compilation which takes hours.
You'll be interested in this paper http://graphics.cs.cmu.edu/projects/whatMakesParis/
The cognitive phase where you think about what you are doing and develop strategies to complete the task. The associative phase where you practice, eliminate mistakes and learn what works. The autonomous phase where you don't have to think about what you are doing anymore.
It is likely you are reaching a plateau because you entered the autonomous cognitive phase. To get off this plateau you should : focus on staying in the cognitive phase by thinking about what you are doing. Set yourself goals in proficiency and most importantly, stay off you comfort by going (~10%)faster than your cruising speed or performing a task more difficult than you are comfortable with. e.g : repeat the harder parts of songs you haven't mastered yet instead of playing the same old song you have mastered, type 10% faster on the keyboard and note the mistakes you make,...
In 'the nature of the firm'[0] Donald Coase asked himself why there are businesses with employees at all when an entrepreneur could instead contract the work, a la Hollywood model. The ultimate answer is that the transaction cost of having to go to a market every time you need to get something done outweighs the inefficiencies of having employees. He got the Nobel prize for that.
I got acquainted of those notions trough the book 'Here 'Comes Everybody' [1]. It talks about the way the internet reduce transaction costs and allow new forms of sharing and collaboration that weren't possible before.
[0] http://en.wikipedia.org/wiki/Ronald_Coase#The_Nature_of_the_...
I have been interested in the subject ever since I read the part of Code Complete dealing with the notion of abstraction. If everytime you woke you had to think about the fact that a door is a bunch of atoms that together form different materials but together some of it being the doorknob you'd never be able to leave your bedroom. It ties closely with the notion of affordance
A teacher told me that the reason for the banning of pork in the Quran and the Bible is to prevent some diseases. Straigth up banning pork for health reason solved the problem. It's probably some kind of myth.
The rich and weak Frank empire, a bad combination, resorted to the disastrous policy of bribing the invaders to leave. It only served to mark the Franks as a good target and emptying the treasury. The Vikings would leave, plunder some other place and come back for more.
In the end, the Franks ended up giving part of their land on the coast : Normandy. This served to settle the invaders down while making THEM have to protect their newly acquired territory against other vikings.
The older, more mature, me with some real world experience, got back to a completely different book. What was dry is now engaging. Random opinions are now insights.
It also helps that my English is much better. The obscure vocabulary and outdated terms have become good writing and old fashioned (in a good way) style.
One thing that surprises me is the definition of architecture. To Brooks the architecture is the set of manuals needed for the user to use the system being created. It sort of is the (external) specification of the software. He clearly states that the architects must refrain from prescribing how the implementation should be. This is very different from today's definition of architect and software architecture. Why is it defined like this? Why isn't the conception of the (internal) architecture of the software a concern to Brooks?