Skip to main content

The Hard Thing About Hard Things 



Peacetime CEO knows that proper protocol leads to winning. Wartime CEO violates protocol in order to win.
Peacetime CEO focuses on the big picture and empowers her people to make detailed decisions. Wartime CEO cares about a speck of dust on a gnat’s ass if it interferes with the prime directive.
Peacetime CEO builds scalable, high-volume recruiting machines. Wartime CEO does that, but also builds HR organizations that can execute layoffs.
Peacetime CEO spends time defining the culture. Wartime CEO lets the war define the culture.
Peacetime CEO always has a contingency plan. Wartime CEO knows that sometimes you gotta roll a hard six.
Peacetime CEO knows what to do with a big advantage. Wartime CEO is paranoid.
Peacetime CEO strives not to use profanity. Wartime CEO sometimes uses profanity purposefully.
Peacetime CEO thinks of the competition as other ships in a big ocean that may never engage. Wartime CEO thinks the competition is sneaking into her house and trying to kidnap her children.
Peacetime CEO aims to expand the market. Wartime CEO aims to win the market.
Peacetime CEO strives to tolerate deviations from the plan when coupled with effort and creativity. Wartime CEO is completely intolerant.
Peacetime CEO does not raise her voice. Wartime CEO rarely speaks in a normal tone.
Peacetime CEO works to minimize conflict. Wartime CEO heightens the contradictions.
Peacetime CEO strives for broad-based buy-in. Wartime CEO neither indulges consensus building nor tolerates disagreements.
Peacetime CEO sets big, hairy, audacious goals. Wartime CEO is too busy fighting the enemy to read management books written by consultants who have never managed a fruit stand.
Peacetime CEO trains her employees to ensure satisfaction and career development. Wartime CEO trains her employees so they don’t get their asses shot off in the battle.
Peacetime CEO has rules like “We’re going to exit all businesses where we’re not number one or two.” Wartime CEO often has no businesses that are number one or two and therefore does not have the luxury of following that rule.



Take Care of the People, The Products, and the Profits — in That Order



Firstly, hire people with the right kind of ambition; otherwise, your company would turn into the political equivalent of the U.S Senate. The right kind is ambition for the company’s success; with the executive’s own success coming on only as a by-product.
Secondly, maintain strict policies and processes on organizational design, performance evaluations, promotions, and compensation
Thirdly, you should promote experienced employees by measuring results against objectives, management skills, innovation, and their ability to work well with others.
Fourthly, ensure one-on-one meetings between employees and managers. These are an excellent platform for employees to discuss their as yet unheard brilliant ideas, pressing issues, and chronic frustrations.

Chapter 9: The End of the Beginning

Continuing his personal story Horowitz recalls that after selling Opsware, he went to work for Hewlett-Packard, but he still knew he wanted to do something else. He decided to set up a firm designed to help technical founders run their companies. Technical founders are the best people to run technology companies. All long-lasting technologies thrived when led by their innovator ; Intel, Amazon, Apple, Google and Facebook had been run by their founders and in some cases still are to this day


Comments

Popular posts from this blog

Access multiple Databases in JPA

According to JPA specification we can define multiple "persistence-unit" elements (i.e. like below) in persistence.xml file and can easily refer them inside Dao layers as this. public class PolarDaoImpl {     @PersistenceContext(unitName="PolarPU")     protected EntityManager entityManager; -- } public class BearDaoImpl {     @PersistenceContext(unitName="BearPU")     protected EntityManager entityManager; -- } Checkout sample persistence.xml <?xml version="1.0" encoding="UTF-8"?> <persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">     <!-- Database 1 -->     <persistence-unit name="PolarPU" transaction-type="RESOURCE_LOCAL">         <

JPA 2 new feature @ElementCollection explained

@ElementCollection is new annotation introduced in JPA 2.0, This will help us get rid of One-Many and Many-One shitty syntax. Example 1: Stores list of Strings in an Entity @Entity public class Users implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @ElementCollection     private List<String> certifications = new ArrayList <String> ();     public Long getId() {         return id;     }     public void setId(Long id) {         this.id = id;     }     public List <String> getCertifications() {         return certifications;     }     public void setCertifications(List <String> certifications) {         this.certifications = certifications;     } .. }         Users u = new Users();         u.getCertifications().add("Sun Certified Java Programmer");         em.persist(u); Generated Tables    Users    Co

Reuse JPA Entities as DTO

Note : Major design advantages of JPA Entities are they can detached and used across tiers and networks and later can by merged. Checkout this new way of querying entities in JPA 2.0 String ql = " SELECT new prepclass2.Employee (e.firstname, e.lastname) FROM Employee e "; List<Employee> dtos = em.createQuery(ql).getResultList(); The above query loads all Employee entities but with subset of data i.e. firstname, lastname. Employee entity looks like this. @Entity @Table(name="emp") public class Employee implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @Column     private String firstname;     @Column     private String lastname;     @Column     private String username;     @Column     private String street;     @Column     private String city;     @Column     private String state;     @Column     private String zipc