The Question of Massive Knowledge When Using Implicative Truth Synthesis
Every endeavor you are after will require a massive, but
structured knowledge. For instance, if you are a salesperson, you
will strive to know all your products, prices, discounts,
geographical and demographic sales performance, and be able to draw
conclusion about further actions based on your statistics and sales
reviews. If you are a software developer you will strive to know
relevant software libraries, classes, functions, software design and
architectural principles, and perhaps design patterns as well. If you
are a chef, you will strive to know as much recipes as possible, to
gain knowledge of special requirements for many kinds of meal
preparations - like adding the ingredients timing and setting and
changing cooking duration and temperature, all that while, perhaps,
supervising a team of cooks.
As you can see, in order to be called successful, every profession or entrepreneurial initiative requires massive relational knowledge. But, how can the Premise Based Implicative Truth Synthesis help you to achieve that?
Perhaps, the first thing to do is to eliminate frustration and pressure of being aware that you must learn so many things. However, how you will learn the skills and expertise is nothing like you have done in your school – Premise Based Implicative Truth Synthesis gives you a brand new approach.
As a first step you will determine and list which pieces of information can be accepted as axioms or starting premises for your field in question. This means determining axiomatic boundaries for your field. Now, when you accept something as a premise, you become aware of the fact that this can be accepted as initial truth – no additional knowledge within your profession can influence that initial premise. This very fact will have a relaxing effect on you; it will remove pressure and frustration when faced with somewhat large number of these initial facts – you will know that these premises have to be accepted a-priori, as the given starting points! These starting points, as you will see, actually define your profession – they will give you all necessary information to start getting results within your field . There is no other way. Once you determine your initial axioms or starting premises you stop questioning where do they come from – what is important is that you will use them “as is” in your projects in question. A way to determine what are the starting premises or axioms for your field is to find out which information can be used as a building component for others – but not the other way.
Example for these starting points for a salesperson are given products, prices, discounts, product properties. These things need to be learned by heart. They are your initial premises! They compose that “massive knowledge”. Don't worry, Implicative Truth Synthesis, as you may have already discovered, will not leave you alone on the island of sales – it will show you how the sales can be connected with other disciplines, how these other disciplines generate your starting premises, and how your sales results will link to the next level – your sales results will create starting premises for another system and in this way you will broaden your professional horizons and become more successful in your career. The first step, though, is to gain skills and expertise in the field of sales. To say again, while you can discover, and will discover, how other fields, outside your sales profession, can generate your starting premises and axioms, at this point you are not concerned about that – what you focus on is to learn all the initial premises you will use within the system called sales – products, prices, discounts, store names, stores' specifics. Once you have this in your mind you then can do the sales, learn intrinsic details about sales, and what constitutes success in sales. Even with this process of learning about, and executing, sales you may be distinguishing subsystems by their axiomatic boundaries, discover the sales component dependencies, and use them in your advantage. In order to be a good salesman or saleswoman you will acquire solid knowledge in math, psychology, marketing, and all these disciplines can be linked together using Implicative Truth Synthesis.
As a conclusion of this important part of the method, we emphasize that gaining massive knowledge means determining and learning initial, starting premises, or axioms that define the system – discovering the system's axiomatic boundaries. This is pure gold, because it will allow you to clearly see how any parts of the system can be obtained from these initial conditions which will lead to your overall success in the chosen profession.
I will illustrate this with another example I am very well acquainted with - software development.
To be successful in the field of software development you need to know hundreds and hundreds function calls and classes. Did I get stress with that fact? No, because I knew these are initial premises, starting axioms from which any of my software system can be built from. The very fact, coming from the Implicative Truth Synthesis method, that these libraries are given a-priori, had a very relaxing effect on me. I just imagine that all these functions are given, without any need for proof, and that can be used as such, allowed me by just reading tens of them, to remember them. Of course, you will always have documentation at your disposal, but reading in advance these function names and signatures helped greatly when required to use them. Even in the field of software development it is always about delineating the systems and subsystems along their axiomatic boundaries – knowing what is given in advance as oppose to what you are going to build with which was given to you. This is that massive knowledge factor in software development. Everything else will come into place. Other initial premises for software developer are given by business analysts or architects, but that knowledge is way easier to learn and accept when you know libraries, classes, and functions. You will gain this knowledge during the project, and it will be well structured and in relation to your knowledge of initial premises – classes, functions, function calls. Only when you know this you can move to the next level in software development – software architecture - but that's another role – software architects tell software developers what to do. The creativity in software development is in determining the sequence of the function calls. There is no other thing to do! Once you have “massive knowledge” of function signatures, you can easily combine them – program the calls to them in the desired sequence. That process is called software design and establishment of design patterns. You, of course, can have “massive knowledge” of design patterns too, but it is way easier to gain it once you know how it is connected with function calls via Implicative Truth Synthesis. Sooner rather than later, you will not see the new knowledge as massive at all. While it may look massive to someone outside your profession, for you it will be almost natural to know the details because you will now how each component relates to each other.
If you want to be a team leader, program manager, or your business' CEO (being it a small business or big company) the requirement still holds – you have to have massive knowledge of your business, but what constitutes the “massive” knowledge changes a bit. In order to be, say, a program manager supervising a multidisciplinary team, you don't necessarily need to have massive knowledge of each discipline (although the successful team members will have to). What you have to know is axiomatic boundaries of each discipline, what are the initial premises for each discipline, and possible results of each discipline, being aware that output from one discipline is the input for the next – first discipline defines, postulates starting premises for the second. This will amount to “massive” knowledge as well – because your team (or company) will have many disciplines, many teams, and many employees belonging to each team. The overall resulting goal from your axiomatic boundary knowledge of teams is the final product. And you really have to know it well so you can coordinate the efforts of all connected teams and steer the company in the right direction as Elon Musk and Steve Jobs did.
Check out my book on Amazon, "Power Reasoning for Success!"
As you can see, in order to be called successful, every profession or entrepreneurial initiative requires massive relational knowledge. But, how can the Premise Based Implicative Truth Synthesis help you to achieve that?
Perhaps, the first thing to do is to eliminate frustration and pressure of being aware that you must learn so many things. However, how you will learn the skills and expertise is nothing like you have done in your school – Premise Based Implicative Truth Synthesis gives you a brand new approach.
As a first step you will determine and list which pieces of information can be accepted as axioms or starting premises for your field in question. This means determining axiomatic boundaries for your field. Now, when you accept something as a premise, you become aware of the fact that this can be accepted as initial truth – no additional knowledge within your profession can influence that initial premise. This very fact will have a relaxing effect on you; it will remove pressure and frustration when faced with somewhat large number of these initial facts – you will know that these premises have to be accepted a-priori, as the given starting points! These starting points, as you will see, actually define your profession – they will give you all necessary information to start getting results within your field . There is no other way. Once you determine your initial axioms or starting premises you stop questioning where do they come from – what is important is that you will use them “as is” in your projects in question. A way to determine what are the starting premises or axioms for your field is to find out which information can be used as a building component for others – but not the other way.
Example for these starting points for a salesperson are given products, prices, discounts, product properties. These things need to be learned by heart. They are your initial premises! They compose that “massive knowledge”. Don't worry, Implicative Truth Synthesis, as you may have already discovered, will not leave you alone on the island of sales – it will show you how the sales can be connected with other disciplines, how these other disciplines generate your starting premises, and how your sales results will link to the next level – your sales results will create starting premises for another system and in this way you will broaden your professional horizons and become more successful in your career. The first step, though, is to gain skills and expertise in the field of sales. To say again, while you can discover, and will discover, how other fields, outside your sales profession, can generate your starting premises and axioms, at this point you are not concerned about that – what you focus on is to learn all the initial premises you will use within the system called sales – products, prices, discounts, store names, stores' specifics. Once you have this in your mind you then can do the sales, learn intrinsic details about sales, and what constitutes success in sales. Even with this process of learning about, and executing, sales you may be distinguishing subsystems by their axiomatic boundaries, discover the sales component dependencies, and use them in your advantage. In order to be a good salesman or saleswoman you will acquire solid knowledge in math, psychology, marketing, and all these disciplines can be linked together using Implicative Truth Synthesis.
As a conclusion of this important part of the method, we emphasize that gaining massive knowledge means determining and learning initial, starting premises, or axioms that define the system – discovering the system's axiomatic boundaries. This is pure gold, because it will allow you to clearly see how any parts of the system can be obtained from these initial conditions which will lead to your overall success in the chosen profession.
I will illustrate this with another example I am very well acquainted with - software development.
To be successful in the field of software development you need to know hundreds and hundreds function calls and classes. Did I get stress with that fact? No, because I knew these are initial premises, starting axioms from which any of my software system can be built from. The very fact, coming from the Implicative Truth Synthesis method, that these libraries are given a-priori, had a very relaxing effect on me. I just imagine that all these functions are given, without any need for proof, and that can be used as such, allowed me by just reading tens of them, to remember them. Of course, you will always have documentation at your disposal, but reading in advance these function names and signatures helped greatly when required to use them. Even in the field of software development it is always about delineating the systems and subsystems along their axiomatic boundaries – knowing what is given in advance as oppose to what you are going to build with which was given to you. This is that massive knowledge factor in software development. Everything else will come into place. Other initial premises for software developer are given by business analysts or architects, but that knowledge is way easier to learn and accept when you know libraries, classes, and functions. You will gain this knowledge during the project, and it will be well structured and in relation to your knowledge of initial premises – classes, functions, function calls. Only when you know this you can move to the next level in software development – software architecture - but that's another role – software architects tell software developers what to do. The creativity in software development is in determining the sequence of the function calls. There is no other thing to do! Once you have “massive knowledge” of function signatures, you can easily combine them – program the calls to them in the desired sequence. That process is called software design and establishment of design patterns. You, of course, can have “massive knowledge” of design patterns too, but it is way easier to gain it once you know how it is connected with function calls via Implicative Truth Synthesis. Sooner rather than later, you will not see the new knowledge as massive at all. While it may look massive to someone outside your profession, for you it will be almost natural to know the details because you will now how each component relates to each other.
If you want to be a team leader, program manager, or your business' CEO (being it a small business or big company) the requirement still holds – you have to have massive knowledge of your business, but what constitutes the “massive” knowledge changes a bit. In order to be, say, a program manager supervising a multidisciplinary team, you don't necessarily need to have massive knowledge of each discipline (although the successful team members will have to). What you have to know is axiomatic boundaries of each discipline, what are the initial premises for each discipline, and possible results of each discipline, being aware that output from one discipline is the input for the next – first discipline defines, postulates starting premises for the second. This will amount to “massive” knowledge as well – because your team (or company) will have many disciplines, many teams, and many employees belonging to each team. The overall resulting goal from your axiomatic boundary knowledge of teams is the final product. And you really have to know it well so you can coordinate the efforts of all connected teams and steer the company in the right direction as Elon Musk and Steve Jobs did.
Check out my book on Amazon, "Power Reasoning for Success!"
Comments
Post a Comment