Three rules to make decisions like a boss.
- Rule #1: Make quick decisions. It’s better to be 40% of the times wrong than 90% of the times undecided.
- Rule #2: Overcome the temptation to stick to yesterday’s wrong decision just to look more consistent. Nobody hired you for consistency, but people will fire you for sticking to wrong decisions.
- Rule #3: Accept that other people around you follow rule #1. If smart people reject your idea, it doesn’t mean it’s a bad idea.
- Keep the site up
- Whatever it takes
- Site unavailable? Our problem, whatever the reason
- Work at a Large Scale
- Many services
- Lots of data
- Many machines
- But not so many people (machines:admins > 4000:1)
- Balance competing demands
- Improve availability and reachability
- Enhance functionality
- Improve efficiency
- Take on new services (post-launch)
Ideally speaking, each corporate, department, and section objective should be:
- Specific – target a specific area for improvement.
- Measurable – quantify or at least suggest an indicator of progress.
- Assignable – specify who will do it.
- Realistic – state what results can realistically be achieved, given available resources.
- Time-related – specify when the result(s) can be achieved.
Object-Oriented vs. Procedural-Oriented
Procedural code gets information then makes decisions. Object-oriented code tells objects to do things.