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.

Rails Links Nov 17, 2022

 Status Checks

Removing Columns

Migration Squasher

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

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

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.

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.

Ruby Links for Sep 1, 2022

 1. Callback Nightmare

Neuromorphic Computing

Neuromorphic-Computing-Guide 

Neuromorphic Tech

Neuromorphic Course

Neuron Simulator

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?

Tomo Deployment Tool

Deploying Rails using Tomo

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.

Create a Node on VPS

1. Signup for VPS provider such as Linode
2. Create a node

Provisioning, Booting, Running

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

My notes

 

Secure Connection

1. Establish secure connection from the workstation to the servers.
2. Run deployment tasks
3. Upload configuration files
4. Log in
5. Put the public key on the server
6. Create a secure connection using the private key
7. Avoid password based authentication
8. Use SSH tunneling to reuse the connection for other services

SSH Keys

Setup passwordless login on the server

• 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

Login using SSH as root

ssh root@server-hostname-or-ip-address

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

1. Signup for hosting provider
2. Create a node
3. Provision a node
4. Deploy code
5. Maintain node

• Figure out which steps are done by the customer and which steps are done by the product.
• Establish secure

MVP

 

June 6, 2022 Tasks

Completed Tasks

1. Deploy static blog for generating leads: https://www.deploygrid.live/
2. Create the landing page and update the site: https://apigrid.dev/

Pending Tasks

1. Create a demo of the product and ask for payment
2. Search "company name sucks" to find the tradeoffs
3. Breakdown the problem: What is the flow? Find the core problem.
4. Solve one CORE problem
5. Ask why five times and note down the answer for each why. 
6. Write an article and promote based on the answers for 8

Practice building solutions. Build something in the chosen space. Product discovery is parallel to building a prototype.

1. Build it fast
2. Ship it
3. Test the idea
4. Tweak the initial idea

Deploy Grid Articles

1. Brewfile
2. DeMorgan's Law
3. Jekyll + Tailwind
4. Customizing DateTime format
5. Cohesion
6. Coupling
7. 12 Factor Apps
8. Naming methods by looking at Jira ticket description
9. Avoid try and using the safe navigation operator
10. Upgrading Puma, managing technical risk
11. Procfile
12. Foreman
13. Install syntax highlighter in Jekyll
14. Falcon server 
15. Using constants and moving all related constants to one file
16. JSON Schema validator for request and response validation
17. Breaking complex conditional into simpler methods to make the code expressive
18. Traceability from requirements to code to database (all layers)
19. Deploying the ToDo apps for different stacks (available as open source) using the deployment tool

The onegrid.run Commands

Grid CLI Commands

Initialize a project and setup SSH keys

grid init

Create your first node

grid create node-name

View the current status of your node

grid status

View the health status of all the servers in your node

grid health

Push the source code to the node

grid deploy

Run any unix command on the production instance and view the output

grid run <unix command>

Example:

Show all the environment variables and their values

grid run ENV

Go to rails production console in sandbox mode:

grid console