Save Draft Formio

 Formio Save Draft

TRIZ books

 1. Engineering of Creativity Introduction to TRIZ Methodology of Inventive Problem Solving (Semyon D. Savransky)

2. TRIZ For Dummies (Lilly Haines-Gadd)

3. Innovation AlgorithmTRIZ, systematic innovation and technical creativity (Genrich Altshuller)

4. Lean TRIZ how to dramatically reduce product-development costs with this innovative problem-solving tool (Harrington, H. James)

5. TRIZ for Engineers: Enabling Inventive Problem Solving (Karen Gadd)

6. Advances and Impacts of the Theory of Inventive Problem Solving The TRIZ Methodology, Tools and Case Studies (Sebastian Koziołek, Leonid Chechurin etc

7. Innovation on Demand New Product Development Using TRIZ (Victor Fey, Eugene Rivin)

8. Inventive Thinking through TRIZ A Practical Guide, Second Edition (Michael A. Orloff)

9. Modern TRIZ A Practical Course with EASyTRIZ Technology (Michael A. Orloff

10. Modern TRIZ Modeling in Master Programs - Introduction to TRIZ Basics at University and Industry (Orloff, Michael A)

11. Research and Practice on the Theory of Inventive Problem Solving (TRIZ) Linking Creativity, Engineering and Innovation (Leonid Chechurin)

12. Simplified TRIZ New Problem Solving Applications for Technical and Business Professionals, 3rd Edition (Kalevi Rantanen, David W. Conley, Ellen R. Domb)

13. Trimming, Miniaturization and Ideality via Convolution Technique of TRIZ A Guide to Lean and High-level Inventive Design (Saurabh Kwatra, Yuri Salamatov)

14. TRIZ POWER TOOLS Job 1 Discovering Markets Carving out New Turf in Saturated Markets (Larry Ball and others

15. TRIZ POWER TOOLS Job 2 Choosing Features What Features Will Excite the Target Market (Larry Ball and others

16. TRIZ POWER TOOLS Skill 1 Resolving Contradictions The Skill that Will Give You the Confidence to Do the Rest

17. TRIZ. Theory of Inventive Problem Solving Level 1 (Vladimir Petrov)

18. Trizics Teach yourself TRIZ, how to invent, innovate and solve impossible technical problems systematically (Gordon Cameron)

19. Triz the Right Solution at the Right Time A Guide to Innovative Problem Solving - Yuri Salamatov

Software

 Just like nature does not have any distinct fields like Physics, Chemistry, Biology etc. The software does not really have distinctions like front end, backend, machine learning etc. The examples used in this book will not have such arbitrary distinctions. So the concepts will be illustrated using devops such as Kubernetes. Because in reality the software is just software and the chosen example illustrate the principle really well. 

The evolution might have occurred without being aware of these principles in action. The purpose of this book to bring those concepts from the realm of experts and make it available to anyone at any skill level.

Trends of Technical Evolution

 Migration of function to super systems. Side car in Kubernetes was extracted into the Linux operating system. This is an example of the function migrating from system to super system over time. 

pnpm

 Appended new lines to /Users/bparanj/.zshrc

Next configuration changes were made:

export PNPM_HOME="/Users/bparanj/Library/pnpm"

export PATH="$PNPM_HOME:$PATH"

To start using pnpm, run:

source /Users/bparanj/.zshrc

Physical Contradiction in Software

 The web app began with a simple UI with no buttons on the home page. After a few years, it had lot of buttons, similar to how Microsoft Word looks like. Not so good! How to design a product that is having the buttons and at the same time not having any buttons but provides all the features we need? Can we remove all the buttons to make the design simple and at the same time provide business value?

The general form of physical contradiction looks like:

X must have A and X must have -A

The thing X must have some property and the opposite property. We can break this contradiction by asking:

1. Do we need both A and -A at the same time?

2. Do we need both A and -A in the same space?

In the web app design case, we can choose the time as a way to separate the opposing properties. We can apply the Separation in Time principle to resolve this physical contradiction.

The design must be modified by removing all the buttons or as many buttons as possible on the home page. The button should appear only when the context is right during the use of the product. One of the reasons why the product became messy page with many buttons is that the app was very CRUD based.

It lacked clear messaging to the users when using the product and did not provide any next action to take during the workflow. By making the messages actionable, we can include the links that provides them a clear action to take to complete their task.