Skip to main content

The 10X Rule: The Only Difference Between Success and Failure by Grant Cardone - (Notes)

Claims to teach:

  1. How to define correct goals and estimate efforts.
  2. Why most people never achieve success.
Chapter 1:
  Says did 10x more effort compare to others in everything (sales presentation, phone calls, property searches)

  2 Rules of 10x
  1.   10X more thought/thinking
  2.   Set 10 times high target and work 10 times harder to achieve it.

  4 Mistakes people make when setting goals:
  • Mistargeting by setting objectives too low
  • Severely underestimating what it takes in terms of actions, resources, money, and energy to accomplish the target.
  • Spending too much time competing and not enough time dominating their sector.
  • Underestimating challenges to attain target.

Chapter 2:
  What reactions manager have when not hitting their targets - Reduce the targets.
  When you start excuses for not hitting your target what that should indicate to you? - Getting off the track.
  The 10x Rule assumes the target is never ___. Any target attacked with the right __ in the right __ with persistence is ___?

Chapter 3: Success
Chapter 6: Assume control of everything
 Successful people accept very high levels of accountability for creating and having success for themselves. They hate blame game, better to make it happen - good or bad.

Chapter 7: Massive action - creates new problems. 
Chapter 8: Average is failing formula.
Chapter 9: 10X Goals
Chapter 10: Competition is for sissies
  Competition limits ability to think creatively
  Dominate your sector
  Stay ahead of the pack.
  Study others and take it to the next level.
  Do something others can't do - because of their size, commitment to other projects and then exploit it.
Competition is healthy then domination is immunity

Chapter 14: Expand - Never contract
Some ways you can expand that only requires energy and creativity and not money 
When have you ever benefitted from contraction

Chapter 17: Customer Satisfaction

Increasing customer is the right target, not customer satisfaction.
If your service doesn't satisfy customers then you're a criminal - Always over deliver.
First, dominate space and get all the attention before other things.
Customer first, customer satisfaction next.

Clients how didn't buy your product survey

Have you ever been surveyed by a company that you didn't buy from?
What is more important than customer satisfaction?
Why do most business fail?
What might be some survey questions you could see when you don't acquire a customer?



Popular posts from this blog

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

public class Users implements Serializable {

    private static final long serialVersionUID = 1L;
    @GeneratedValue(strategy = GenerationType.AUTO)
    private Long id;
    private List<String> certifications = new ArrayList<String>();

    public Long getId() {
        return id;

    public void setId(Long 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");

Generated Tables

Column --> ID
    Row             1


ArrayList vs LinkedList vs HashSet Performance Comparision

ConclusionsInserting & Reading sequentially from Collection prefer LinkedList/ArrayListInserting & Reading/Deleting by Search/equals from Collection prefer HashSetInserting, ArrayList & LinkedList performs best while HashSet takes double the timeReading, HashSet performs best while ArrayList & LinkedList are marginally lessDeleting, HashSet performs 10 times better than ArrayList & ArrayList performs 4 times better than LinkedList. LinkedList is slow because of sequencial search Bottom line : unless you are not going to iterate using for(Integer i : list ) then prefer HashSet
Inserting/Reading/Deleting integer's from zero till countJDK7Collectionactioncounttime msArrayListInsert1000/1LinkedListInsert1000/1HashSetInsert1000/1ArrayListInsert100005LinkedListInsert100004HashSetInsert100007ArrayListInsert10000011LinkedListInsert10000011HashSetInsert10000021ArrayListGet/Read1000LinkedListGet/Read1000HashSetGet/Read1000ArrayListGet/Read100004LinkedListGet/Read100003Has…

Validating CSV Files

What is CsvValidator ?
  A Java framework which validates any CSV files something similar to XML validation using XSD.

Why should I use this ?
  You don't have to use this and in fact its easy to write something your own and also checkout its source code for reference.

Why did I write this ?
  Some of our projects integrate with third party application which exchanges information in CSV files so I thought of writing a generic validator which can be hooked in multiple projects or can be used by QA for integration testing.

What is the license clause ?

Are there any JUnit test cases for me checkout ?
 Yes, source

How to integrate in my existing project ?

Just add the Jar which can be downloaded from here CsvValidator.jar and you are good.

Instantiate CsvValidator constructor which takes these 3 arguements

         // filename is the the file to be validated and here is a sample         // list - defines all the fields in the above csv file ( a field has index, type, isOptional, rege…