Note:
When this guide is more complete, the plan is to move it into Prepack documentation.
For now I put it out as a gist to gather initial feedback.
If you're building JavaScript apps, you might already be familiar with some tools that compile JavaScript code to equivalent JavaScript code:
| import { Prisma } from './../generated/prisma'; | |
| import { readFileSync } from 'fs'; | |
| // add to yarn: | |
| // "seed": "dotenv -e .env -- ts-node ./src/seed/seed.ts" | |
| const prisma = new Prisma({ | |
| endpoint: process.env.PRISMA_ENDPOINT, // the endpoint of the Prisma DB service (value is set in .env) | |
| secret: process.env.PRISMA_SECRET, // taken from database/prisma.yml (value is set in .env) | |
| debug: false // log all GraphQL queries & mutations |
| import React from 'react' | |
| function Login({onSubmit}) { | |
| return ( | |
| <div> | |
| <form | |
| data-test="login-form" | |
| onSubmit={e => { | |
| e.preventDefault() | |
| const {username, password} = e.target.elements |
| package main | |
| import ( | |
| "fmt" | |
| "sync" | |
| "sync/atomic" | |
| ) | |
| // Fill Channel with int values | |
| func fillChan(number int) <-chan int { |
In order of first appearance in The Morning Paper.
| /* | |
| |------------------------------------------------------------------------------- | |
| | Custom 'module resolver' for Jest | |
| |------------------------------------------------------------------------------- | |
| | | |
| | Forked from Jest, this is the default 'resolver' with the added benefit of | |
| | remapping the "main" field to the value of the "module" field, when present. | |
| | | |
| */ |
| // | |
| // MIT License | |
| // | |
| // Copyright (c) 2018 Ali Sharif | |
| // | |
| // Permission is hereby granted, free of charge, to any person obtaining a copy | |
| // of this software and associated documentation files (the "Software"), to deal | |
| // in the Software without restriction, including without limitation the rights | |
| // to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | |
| // copies of the Software, and to permit persons to whom the Software is |
From time to time, Musk will send out an e-mail to the entire company to enforce a new policy or let them know about something that's bothering him. One of the more famous e-mails arrived in May 2010 with the subject line: Acronyms Seriously Suck:
There is a creeping tendency to use made up acronyms at SpaceX. Excessive use of made up acronyms is a significant impediment to communication and keeping communication good as we grow is incredibly important. Individually, a few acronyms here and there may not seem so bad, but if a thousand people are making these up, over time the result will be a huge glossary that we have to issue to new employees. No one can actually remember all these acronyms and people don't want to seem dumb in a meeting, so they just sit there in ignorance. This is particularly tough on new employees.
That needs to stop immediately or I will take drastic action - I have given enough warning over the years. Unless an acronym is approved by me, it should not enter the SpaceX glossary.
