A place to keep all my cheat sheets for the complete development of ASIC hardware or a software app/service.
Table of Contents,
- SOFTWARE CHEAT SHEETS
(For the goal of creating an App/Service)
- DEVELOPMENT
- DEVELOPMENT ENVIRONMENTS
- LANGUAGES
- OPERATING SYSTEMS
- SOFTWARE ARCHITECTURES
- SOURCE / VERSION CONTROL
- OPERATIONS TOOLS
- CONFIGURATION MANAGEMENT
- CONTINUOUS INTEGRATION / CONTINUOUS DEPLOYMENT
- ORCHESTRATION
- TELEMETRY
- SERVICE ARCHITECTURES
- SaaS - SOFTWARE AS A SERVICE
- FaaS - FUNCTIONS AS A SERVICE
- PaaS - PLATFORM AS A SERVICE
- CaaS - CONTAINERS AS A SERVICE
- IaaS - INFRASTRUCTURE AS A SERVICE
- SERVICE PROVIDERS
- AMAZON AWS
- GOOGLE GCP
- MICROSOFT AZURE
- DEVELOPMENT
- HARDWARE CHEAT SHEETS (For the goal of creating an ASIC)
- OTHER CHEAT SHEETS (Random things I'm interested in)
These cheat sheets contain info I gathered from other sources and figured out over time. It is an ongoing process. View my entire list of cheat sheets on my GitHub Webpage.
Various Apps and tools for the goal of creating an App/Service.
-
DEVELOPMENT ENVIRONMENTS
-
LANGUAGES
-
OPERATING SYSTEMS
-
LINUX
-
LINUX DISTRIBUTIONS
- coming soon
-
WINDOWS
-
MAC OS
-
-
SOFTWARE ARCHITECTURES
-
API
-
AUTHORIZATION
-
BLOCKCHAIN
-
CRYPTOGRAPHY
-
DATABASE
-
MESSAGING
-
MICROSERVICES
-
-
SOURCE / VERSION CONTROL
-
CONFIGURATION MANAGEMENT
-
CONTINUOUS INTEGRATION / CONTINUOUS DEPLOYMENT
-
ORCHESTRATION
-
BUILDS / DEPLOYMENT / CONTAINERS
-
CLUSTER MANAGERS / RESOURCE MANAGEMENT / SCHEDULING
-
DISCOVERY / CONFIGURATION
-
-
TELEMETRY
-
Overview
-
SaaS - SOFTWARE AS A SERVICE
-
FaaS - FUNCTION AS A SERVICE
- aws lambda (hello-go-deploy-aws-lambda repo coming soon)
- google cloud functions (gcf) (hello-go-deploy-gcf repo coming soon)
- microsoft azure functions (hello-go-deploy-azure-functions repo coming soon)
-
PaaS - PLATFORM AS A SERVICE
-
CaaS - CONTAINERS AS A SERVICE
-
IaaS - INFRASTRUCTURE AS A SERVICE
This illustration shows how various Apps and tools fit together for the goal of creating an App/Service,
Various Apps and tools for the goal of creating an ASIC.
-
HARDWARE ARCHITECTURES
-
LANGUAGES
-
SIMULATION
- coming soon
-
SYNTHESIS
- coming soon
-
TIMING
- coming soon
This illustration shows how various Apps and tools fit together for the goal of creating an ASIC,
Random other things I'm interested in.
-
APPLE
-
PC
-
TECHNOLOGIES
-
AMERICAN
-
WARS
This entire sections is a massive work in progress, it will take me quite a few years to finish.
-
APPLIED
-
NOTABLE EQUATIONS
-
PURE
-
CHANGES
-
FOUNDATIONS
-
NUMBER SYSTEMS
-
SPACES
-
STRUCTURES
-
-
CRYPTOCURRENCY
-
FULL NODE
-
MULTIPLE POOLS
-
POOLS
-
CELLULAR
-
WAN / LAN
-
BIOLOGICAL / LIFE SCIENCE
-
EARTH & SPACE SCIENCE
-
PHYSICAL SCIENCE
-
HUMMINGBOARD
-
RASPBERRY PI (RasPi)
For fun, I use concourse to automatically update my GitHub Webpage and alert me of the changes via repo status and slack.
The update is accomplished this by copying and editing/updating
this README.md
file to /docs/_includes/README.md
.
A pipeline file pipeline.yml shows the entire ci flow. Visually, it looks like,
The jobs
and tasks
are,
job-readme-github-pages
runs task readme-github-pages.sh.
The concourse resources types
are,
my-cheat-sheets
uses a resource type docker-image to PULL a repo from github.resource-slack-alert
uses a resource type docker image that will notify slack on your progress.resource-repo-status
uses a resource type docker image that will update your git status for that particular commit.
For more information on using concourse for continuous integration, refer to my cheat sheet on concourse.