Skip to main content

Leadership

In small business owner is the dominant personality.
To max potential of business max to potential of owner
If business growing/stagnant its direct reflection of leadership

Biggest Obstacle
  If someone told you they would pay you 1million if you get 20 customers?
    - Apathy - is the biggest obstacle
  How to batter apathy
   Choice, Courage, Vision
  How to maximize potential
   max your time, effort, potential
 
1. Time
  Our challenges
     distracted, easy,
  Determine value?
    profit activity generates
    achieve business vision
    next level

 Pareto Principle
 Value   Input  Output  Return
  A         1%      50%       5000%
  B         4%      64%       1600%
  C        20%     80%         400%
  D       80%      20%         25%

If you do A, B, C for next 30 days, where will you be?
How to get high-value task done?
  - Identify, Scale-to-magnify & consistently get-done.

What task brought the most business?
   Deploy apps magically using compose
 
General high valued tasks
  - Developed lucrative ideas
  - Referral, partnerships
  - Events
  - Strategies

Tag tasks as A B C D
  - Delegate, Defer, Delete, Design out



2. Maximize Efforts?
  Upgrade peer group,
  expert in one thing
  decision that really count

Upgrading your peer group
Level                    1                 2             3              4        
Effectiveness  Ineffective Somewhat Effective Highly-Effective
Seek out the advice of the others

Be an expert and be a leader

Decisions
  On the fly decisions - win/loss
  Thought out pre-established criteria - most win, less loss

3. Potential
   - Scale strengths and shore up weakness
   - Surround with people who wants to grow
   - Measure the progress
   -



















 


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