This leads us to the odd conclusion that strict control is something that matters a lot on relatively useless projects and much less on useful projects.

So, how do you manage a project without controlling it? Well, you manage the people and control the time and money. You say to your team leads, for example, “I have a finish date in mind, and I’m not even going to share it with you. When I come in one day and tell you the project will end in one week, you have to be ready to package up and deliver what
you’ve got as the final product. Your job is to go about the project incrementally,
adding pieces to the whole in the order of their relative value, and doing integration and documentation and acceptance testing incrementally as you go.

Consistency and predictability are still desirable, but they haven’t ever been the most important things.

Hire With Your Head

Lack of clear expectations is one of the biggest causes of employee turnover and poor performance

Focus on the _doing_, not the _having_ (skills), to improve hiring accuracy

As long as the compensation package is reasonable, most top people don’t consider it the number-one criteria

Success = Talent * Energy2 + Team Leadership + Comparable Past Performance + Job-Specific Problem Solving

The best ppl consistently deliver more results than expected, and they do it on time, all the time.

Accurate interviewing is abt peeling the onion & digging deep in2 an accomplishment, not asking bunch of clever questions 

Don’t settle for anything less than high energy, good team skills, & a good dose of talent or the ability to learn

Job change is a strategic decision based on opportunity and growth, not just a tactical decision based on salary

The team is a very important consideration for a top person. 

Class-based architectures can impose a degree of structural rigidity on a system that can stifle its evolution. This is because they do not allow the kind of dynamic system reorganization that prototype-based architectures permit. This rigidity can be particularly harmful in mature, successful systems that must then evolve further to meet a host of new requirements. It is essential that the structure of a system be able to evolve in such a way that it matches that of the problem itself. (Form must continue to follow function.)

In a class-based object-oriented language, in general, state is carried by instances, methods are carried by classes, and inheritance is only of structure and behaviour. In ECMAScript, the state and methods are carried by objects, and structure, behaviour, and state are all inherited.