seve's skills and patterns · source for this file

Skills and Patterns

These are skills and patterns for my team's developers. They should be used as a reference wherever possible or useful.

Why did we pick XXX over YYY?

Open a PR, start a discussion. The patterns and technology here are mostly based on @seveibar's years of building open-source and startup applications, with several applications used by hundreds of thousands of people. Eventually it'll be based on a collective discussion.

Proposing Changes

Open a PR to start a discussion.

Technology choices and patterns are always opinionated. Patterns and technologies evolve and so should these documents. Still, you must be an expert in what you are replacing to make a case for it's replacement. So if you want to replace Postgres with MongoDB, or Material UI with Semantic UI, or $PROVEN_TECH with $TECH_OF_MONTH, you'll need to have serious chops in BOTH technologies.

Read Online

You can view these online and quickly reference by typing sp.seve.blog/<abbreviated pattern name>.

All Patterns:

___vc
auth0
ava-testing
avoid-try-catch
bail-early
bidirectional-sql-relationship
burnable-projects
cloud9
continuous-integration
curl
docker
eslint
exporting-react-components
fat-or-minimal
flowtype
git
good-readmes
handler-pattern
how-to-build-hooks
javascript
json-web-tokens
knexjs
lerna
material-ui
micro
micro-testing
navigating-a-react-project
ngrok
pm2
postgres
postgres-json
postgres-testing
postgrest-api
postgrest-testing
prefer-yarn
prettier
react-app
react-library
react-optimization
react-state-management
react-storybook
react-styling
readme-customer-release
row-level-security
seamless-immutable
sql
stupid-simple-migrations
superstruct
tldr
traefik
two-parameter-limit
ui-inspired-data-driven-architecture
use-reducer-toggle
user-empathy
vercel