Friday, December 23, 2022
Thursday, December 15, 2022
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
Monday, December 12, 2022
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.
Sunday, December 11, 2022
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
Saturday, December 10, 2022
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.
Thursday, November 17, 2022
Tuesday, November 01, 2022
Prism of TRIZ
Step 1
Describe the problem in simple language covering all the main points.
Step 2
Re-describe the problem in a more general, conceptual way, stripping out the detail.
Step 3
Locate existing answers to the very general problem using the TRIZ Solution Catalog
Step 4
Use the solution triggers + your knowledge and experience to find pragmatic solutions.
Theory of Inventive Problem Solving
1. Systematic ways for defining and understanding problems
2. Using the four solution catalogs to solve them
1. Inventive Principles - For solving contradictions (conflicting requirements)
2. TRIZ Trends - Predict the likely evolution of products
3. Standard Solutions - For dealing with harms, inefficiencies and problems to do with measurement
4. Effects - Answer how to questions using the Effects Database
Sunday, September 18, 2022
apitome ruby 3 compatibility
https://github.com/jejacks0n/apitome/issues/121
Based on some local testing, the apitome gem works fine on ruby 3.
PR merged: https://github.com/jejacks0n/apitome/pull/122
Thursday, September 08, 2022
Action Oriented vs Object Oriented
- Distribute system intelligence horizontally as uniformly as possible, that is, the top-level classes in a design should share the work uniformly.
- Do not create god classes/objects in your system. Be very suspicious of a class whose name contains Driver, Manager, System, or Subsystem.
- Beware of classes that have many accessor methods defined in their public interface. Having many implies that related data and behavior are not being kept in one place.
- Beware of classes that have too much noncommunicating behavior, that is, methods that operate on a proper subset of the data members of a class. God classes often exhibit a great deal of noncommunicating behavior.
- In applications that consist of an object-oriented model interacting with a user interface, the model should never be dependent on the interface. The interface should be dependent on the model.
- Model the real world whenever possible. (This heuristic is often violated for reasons of system intelligence distribution, avoidance of god classes, and the keeping of related data and behavior in one place.)
- Eliminate irrelevant classes from your design. Heuristic 3.8 Eliminate classes that are outside the system.
- Do not turn an operation into a class. Be suspicious of any class whose name is a verb or is derived from a verb, especially those that have only one piece of meaningful behavior (i.e., do not count sets, gets, and prints). Ask if that piece of meaningful behavior needs to be migrated to some existing or undiscovered class.
- Agent classes are often placed in the analysis model of an application. During design time, many agents are found to be irrelevant and should be removed.
Wednesday, September 07, 2022
The Building Blocks of Object Oriented Paradigm
- All data should be hidden within its class.
- Users of a class must be dependent on its public interface, but a class
- should not be dependent on its users.
- Minimize the number of messages in the protocol of a class.
- Implement a minimal public interface that all classes understand [e.g., operations such as copy (deep versus shallow), equality testing, pretty printing, parsing from an ASCII description, etc.].
- Do not put implementation details such as common-code private functions into the public interface of a class.
- Do not clutter the public interface of a class with things that users of that class are not able to use or are not interested in using.
- Classes should only exhibit nil or export coupling with other classes, that is, a class should only use operations in the public interface of another class or have nothing to do with that class.
- A class should capture one and only one key abstraction. Heuristic 2.9 Keep related data and behavior in one place.
- Spin off non-related information into another class (i.e., noncommunicating behavior).
- Be sure the abstractions that you model are classes and not simply the roles objects play.
Thursday, September 01, 2022
Saturday, August 27, 2022
Wednesday, July 06, 2022
Start with the Ideal Outcome
Start with the Ideal Outcome
Capture
1. All the benefits you want
2. The primary output of your system (the reason it exists)
Prioritize
3. What are the primary benefits?
4. Sort other benefits into 'must haves' and 'nice to haves'.
Action Item
Fill out the Ideal Outcome for Scoping New Inventions worksheet
What benefits do we want from an ideal provisioning and deployment system?
What benefits would an ideal system deliver?
Wave a magic wand over it and write down all the things you want.
Ideal Thinking
Imagine all the things you want without worrying about the constraints of any kind.
What are the downsides of the current systems in the market?
Context
Who needs to use this sytem?
In what circumstances?
Thursday, June 23, 2022
Wednesday, June 22, 2022
Heroku Reviews - June 22, 22
WHAT
Deploy full stack apps (FE + BE + DB)
Deploy full stack apps without the need of all the technical skills needed for AWS
Prototyping - quick deployment
Build an entire pipeline (dev, test and prod)
Ship web apps without a lot of effort
Build app very quickly
Build, deploy and run your app very easily
Very helpful to build highly large data apps
Easy to deploy full stack applications fast without worrying about configuring
HOW
Connect your app using a Git repo and it will handle the deployment
USE
Simple and intuitive interface
Simple and easy to use, even for users with minimal knowledge of application architecture
EASY
Easy to setup
You can set up an entire environment very fast
DEPLOYMENT SPEED
Instant deployment
One-step deployment process
Their auto-maintenance and auto-deploy services saves a lot of time and effort
DEPLOYMENT EASE
Makes it easy to deploy apps without having the knowledge of managing a server
CLI tool - easy to deploy
Quick and easy deployment
INTEGRATIONS
Seamless integration with Git
Ease with which we can deliver updated code and new features
Add ons
Marketplace
Easy installation of plugins and add-ons
Integrate third-party website with Salesforce
Connect database with a single click with the help of plug in
LEARNING CURVE
Less to learn for developers
COMPLEXITY
Complexity < (AWS or GCP)
SCALING
Scales with you
Autoscale based on usage
Autoscale our platform
TOOLS
Migration tool
Powerful metrics to monitor the app
ZERO DOWNTIME
No downtime
Rolling restarts (to fix delays in requests during deploy)
Perform a rollback to a previous version with just one click
TIME SAVINGS
Saves a lot of time in creating and deploying new apps
COST SAVINGS
Streamline the process for developers and saves costs on app development
Reduced the dependence small teams have on Devops (saves costs)
DOCUMENTATION
for:
using several environments
tuning memory usage
deploying from Dropbox
Detailed sample apps and code for starting a new app
SECURITY
Secure and protected ecosystem
Dev / Prod Environment Parity
Being able to switch from local to remote environment
You can work locally with remote database
WHO
Great for small teams and if you need to validate your product
Single developer or small teams can focus on the project and get it launched, without too much hassle
CONS
Once you get substantial traffic, you have to ask yourself whether your budget should focus on:
more dynos
code optimization
different platform
Support
Contract trap
License cose
Expensive
Gets expensive quickly
Non traditional server environment
Deploy fixed number of apps
Apps go to sleep if there is no user activity
Environment configuration setup is slightly complex (vs Netlify)
CI service is fairly limited (works fine with CircleCI & Travis)
Minimal language support
Low network performance
Upsell on features you may not need
To the uneducated, they will opt into unnecessary features that are otherwise free
Security add-ons like AWS would be nice
Need a separate service for repo like Github, rather than having everything inclusive
30 seconds restriction (not compatible with OS libraries)
Request gets stuck behind slow request
Hard to gauge the capacity needed
Hit by downtimes (not much to do once it goes down)
If AWS goes down Heroku will go down
SSH Basics
We learned a little bit about the SSH protocol and how to use the ssh program to connect to a remote server.
SSH protocol was introduced for secure communication using the pub- lic key encryption on the network. OpenSSH is a collection of programs implementing this protocol and available to us.
Connecting to a remote server can be as easy as running ssh $USER@$HOST. In the case we create a server with password authentication, we can use ssh-copy-id to put the public key to the server and take advantage of SSH-keys only access.
We learned about SSH keys management. We can find our keys in ~/.ssh, generate new ones with ssh-keygen. We explored how ~/.ssh/authorized_keys is used for authorizing access using these keys and how SSH host keys are stored in ~/.ssh/known_hosts.
scp and sftp are the go-to tools for secure file transfer over SSH. Although using scp has some security implications given its original design, it’s safe to use in simple commands. rsync is another popular option.
Monday, June 13, 2022
12 Factor App
Heroku, with its 12-factor application model, has changed the way we think about building, deploying, and hosting web applications.
The rise of containers, phoenix servers and continuous delivery has seen a move away from the usual approach to deploying web applications. Traditionally we have built an artifact and then installed that artifact into an application server. The result was long feedback loops for changes, increased build times and the not insignificant overhead of managing these application servers in production. Many of them are a pain to automate too. Most teams we work with favor bundling an embedded http server within your web application. There are plenty of options available: Jetty, SimpleWeb, Webbit and Owin Self-Host amongst others. Easier automation, easier deployment and a reduction in the amount of infrastructure you have to manage lead us to recommend embedded servers over application servers for future projects.
Cloud Native Apps
https://dev.to/syncsynchalt/safe-http3-experimentation-with-caddy-447f
https://requestmetrics.com/web-performance/http3-is-fast
Thursday, June 09, 2022
My notes
Secure Connection
- Establish secure connection from the workstation to the servers.
- Run deployment tasks
- Upload configuration files
- Log in
- Put the public key on the server
- Create a secure connection using the private key
- Avoid password based authentication
- Use SSH tunneling to reuse the connection for other services
SSH Keys
- Use ssh-keygen to make a new pair of SSH keys
- Create a virtual private server in the admin panel
- Copy the SSH keys using ssh-copy-id utility for providers that setup password-based authentication
Success Criteria
Remote Shell
- Install ssh-agent on Mac OS
- Connect to server from the client, use ssh command
- Define USER environment variable to specify hte user on the host
- Define HOST environment variable to specify the remote server's hostname or IP address
- The default configuration file used is ~/.ssh/config
- The default identity file (private key) is ~/.ssh/id_rsa
- The identity_file, login_name and port values can be specified per host in the configuration file (~/.ssh/config)
File Transfers
Steps
- Signup for hosting provider
- Create a node
- Provision a node
- Deploy code
- Maintain node
- Figure out which steps are done by the customer and which steps are done by the product.
- Establish secure
Wednesday, June 08, 2022
June 6, 2022 Tasks
Completed Tasks
- Deploy static blog for generating leads: https://www.deploygrid.live/
- Create the landing page and update the site: https://apigrid.dev/
Pending Tasks
- Create a demo of the product and ask for payment
- Search "company name sucks" to find the tradeoffs
- Breakdown the problem: What is the flow? Find the core problem.
- Solve one CORE problem
- Ask why five times and note down the answer for each why.
- Write an article and promote based on the answers for 8
- Build it fast
- Ship it
- Test the idea
- Tweak the initial idea
Tuesday, June 07, 2022
Deploy Grid Articles
- Brewfile
- DeMorgan's Law
- Jekyll + Tailwind
- Customizing DateTime format
- Cohesion
- Coupling
- 12 Factor Apps
- Naming methods by looking at Jira ticket description
- Avoid try and using the safe navigation operator
- Upgrading Puma, managing technical risk
- Procfile
- Foreman
- Install syntax highlighter in Jekyll
- Falcon server
- Using constants and moving all related constants to one file
- JSON Schema validator for request and response validation
- Breaking complex conditional into simpler methods to make the code expressive
- Traceability from requirements to code to database (all layers)
- Deploying the ToDo apps for different stacks (available as open source) using the deployment tool
Monday, June 06, 2022
The onegrid.run Commands
Grid CLI Commands
Compass
Who are the other players delivering the same functions?
Which player will win the inevitably win the IFR game in the long term?
What implications does this have on the business we are thinking of starting?
Saturday, May 28, 2022
Caddy Server Topics
Install Caddy Server
Caddy Server - Hello World
Caddy Server - API
Deploying Static Site using Caddy Server
Deploying Node.js app using Caddy Server
Deploying Zally using Caddy Server (Replace nginx and Apache with Caddy)
Caddy Server as Reverse Proxy for Micro Services
Using Caddy Server with a Rails app on EC2
Deploy a Dynamic Webapp on a Custom Domain using Caddy Server
Sunday, May 22, 2022
Bad Characteristics of the Developer Tool
Plays loud and horrible music on page load
Displays dropping snow flakes
Displays lot of banner ads
Loads lot of images very slowly
Broken images and links on the page
Has many distractions on the page
Loads a blank page on the screen
Loads flashing headlines on the page
Loads animated gifs
Overlay popup hides the page
Does not have any outcome
Links to unnecessary features
Lack of balance between design and content
Prompts installation of Java and flash to load applets and flash player
Not using web safe fonts
No button to click (no way to navigate)
Loading large images
Too much text
No whitespace
No clear user journey
Slow site speed
100% bounce rate
No one completes the entire flow
No SSL
Completed Tasks for Keyword Research of OpenAPI Developer Tool
- Search Google for "OpenAPI", check the results for relevance
- Search Amazon for "OpenAPI", check the results for relevance
- Search Google trends for "OpenAPI", worldwide and for the past 5 years.
Compare your keyword with: orchid care, improve memory, leadership skills, beekeeping and see if it falls within similar search volume. It falls within the profitable bandwidth.
Elevator Pitch for Zally
Zally is a linter for OpenAPI specifications.
- Capable of checking RESTful API design standards
- Gives early feedback for API designers
- Provides best practices and advices
Its standard configuration will check your APIs against the rules defined in Zalando's RESTful Guidelines, but anyone can use it out-of-the-box.
Web UI shows implemented rules and lints external files and inline API definitions.
Features
- Support for OpenAPI 3 and (Swagger) OpenAPI 2 specifications
- RESTful API, CLI and Web interface
- Rich Check configuration
- Ignore functionality (x-zally-ignore extension)
- Java/Kotlin API for new Checks + helper functions
Saturday, April 16, 2022
Monday, February 21, 2022
Installing mysql2 gem on Mac OS Monterey M1 chip
gem install mysql2 -- --srcdir=/usr/local/mysql/include
fatal error: Unable to locate credentials
Command:
$ aws s3 rm s3://YOUR_BUCKET/ --recursive --dryrun --exclude "*" --include "my-folder/*"
Run aws configure and provide the access key and secret key when prompted
Unsupported Python version detected: Python 2.7
Error:
Unsupported Python version detected: Python 2.7
To continue using this installer you must use Python 3.6 or later.
For more information see the following blog post: https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-python-2-7-in-aws-sdk-for-python-and-aws-cli-v1/
Change this command:
sudo ./awscli-bundle/install -i /usr/local/aws -b /usr/local/bin/aws
to
sudo /usr/bin/python3 ./awscli-bundle/install -i /usr/local/aws -b /usr/local/bin/aws
Thursday, February 10, 2022
pyspark Installation
Install Latest Python
sudo apt update
sudo apt -y upgrade
python3 -V
Install Development Tools
sudo apt install -y build-essential libssl-dev libffi-dev python3-dev
sudo apt install software-properties-common -y
sudo add-apt-repository ppa:deadsnakes/ppa
sudo apt install python3.10
Install PIP
sudo apt install -y python3-pip
Install pyspark
pip install pyspark
source ~/.profile
sudo apt install default-jdk scala git
Verify Spark Installation
pyspark
Python 3.8.10 (default, Nov 26 2021, 20:14:08)
[GCC 9.3.0] on linux
Welcome to SPARK version 3.2.1
Using Python version 3.8.10 (default, Nov 26 2021 20:14:08)
Spark context Web UI available at http://dollar.lan:4040
Spark context available as 'sc' (master = local[*], app id = local-1644524108365).
SparkSession available as 'spark'.
>>> big_list = range(1000)
>>> rdd = sc.parallelize(big_list, 2)
>>> odds = rdd.filter(lambda x:x %2 != 0)
>>> odds.take(5)
[1, 3, 5, 7, 9]