Concept | Definition |
---|---|
Autonomy | How well will this company give me autonomy to do my job? |
Freedom | How much freedom will I have to balance work and personal life? |
Responsibilities | What level of responsibilities will I have, and how extensive will they be? |
Culture | How well does this company's culture align with my values, and how open is the company to allowing me to contribute to the culture I believe in? |
Tech Stack | How closely does the tech stack used by this company align with my preferences, and to what extent is the company willing to allow me to use the stack I prefer? |
Personal Growth | How big is the potential of this company to help me keep growing? |
- Acronym
- Atomicity
- One operation per time, independent on which one (INSERT, UPDATE, DELETE etc), preventing any error to be persisted. Basically: every piece of your query should be ok "atomically speaking" to be considered a successful operation.
- If any part of the operation fails, it will roll everything back.
- Consistency
- Let you only write data that is predefined previously. Like a table modeling with specifics data types, constraints, cascades, indexes or any other modeled clause.
- Isolation
- Atomicity
- Each operation per time without interfere in other operations;
Made this example to show how to use Next.js router for a 100% SPA (no JS server) app.
You use Next.js router like normally, but don't define getStaticProps
and such. Instead you do client-only fetching with swr
, react-query
, or similar methods.
You can generate HTML fallback for the page if there's something meaningful to show before you "know" the params. (Remember, HTML is static, so it can't respond to dynamic query. But it can be different per route.)
Don't like Next? Here's how to do the same in Gatsby.
Ler e entender um pouco desse artigo. https://wiki.c2.com/?FeynmanAlgorithm
- Reconhecer como você pensa
- Descrever métodos que você usa para pensar
- Entender métodos diferentes de pensar
- Fazer perguntas sobre tudo(incluindo sobre perguntas)
const { query } = router | |
const queryParams = { | |
[field]: [value]?.concat?.(query[field] || []) | |
} | |
router.replace({ | |
query: { ...query, ...queryParams }, | |
}); |
These are the repos that helped me the most
author | repo | has server | has web client | has mobile client |
---|---|---|---|---|
sibelius | DM @sseraphini on Twitter about relay-workshop | yes | yes | no |
noghartt | fakeddit | yes | yes | no |
danilo | rbaf | yes | yes | no |
bia | koa-server | yes | yes | no |
akinn | amora | yes | no | yes |
xsadia | koa-todo-api | yes | yes | no |
Aviso: Muitas vezes detalhes de várias operações podem variar de banco para banco. Em questões onde fiquei em dúvida, este documento segue o funcionamento do PostgreSQL, pois é o banco que conheço melhor.
Antes de começar a escrever SQL, você precisa entender o modelo de como um banco de dados relacional funciona. Não precisa se aprofundar muito, mas você precisa entender como que dados e relacionamentos entre eles são representados. (Nota importante: Relacionamento e relação não são a
const assert = require('assert'); | |
const Value = (n) => ({ type: 'value', n }); | |
const Sum = (a, b) => ({ type: 'sum', a, b }); | |
const Prod = (a, b) => ({ type: 'prod', a, b }); | |
const Div = (a, b) => ({ type: 'div', a, b }); | |
const Sub = (a, b) => ({ type: 'sub', a, b }); | |
const sliceLast = (a, n) => a.slice(n > a.length ? 0 : a.length - n, a.length); |
// Multiplication comes from this issue: https://github.com/type-challenges/type-challenges/issues/5814 | |
type Reverse<A> = | |
`${A}` extends `${infer AH}${infer AT}` | |
? `${Reverse<AT>}${AH}` : A | |
type Digs = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9] | |
type DigsNext<I = Digs, R = {}> = | |
I extends [infer Head, infer Next, ...infer Tail] | |
? DigsNext<[Next, ...Tail], R & Record<Head, Next>> |
- Learn how Canvas works
- Learn how Create a scene
- Learn how to Positining elements in a scene
- Learn how to create 3D elements using code
- Learn how to use 3D assets, textures, maps HDRIs
- Learn how to interact based on events, click, scroll, drag
- Learn how Animate elements - Frames
- Learn how Map WebGL elements to DOM elements whilst scrolling
- Learn how Preload and prerender textures (replicates AssetLoader)
- Learn how Manage WebGL resources (create and destroy materials and geometries as needed)