Magic words:
psql -U postgresSome interesting flags (to see all, use -h or --help depending on your psql version):
-E: will describe the underlaying queries of the \ commands (cool for learning!)-l: psql will list all databases and then exit (useful if the user you connect with doesn't has a default database, like at AWS RDS)
| Android Emulator usage: emulator [options] [-qemu args] | |
| options: | |
| -sysdir <dir> search for system disk images in <dir> | |
| -system <file> read initial system image from <file> | |
| -datadir <dir> write user data into <dir> | |
| -kernel <file> use specific emulated kernel | |
| -ramdisk <file> ramdisk image (default <system>/ramdisk.img | |
| -image <file> obsolete, use -system <file> instead | |
| -initdata <file> same as '-init-data <file>' | |
| -data <file> data image (default <datadir>/userdata-qemu.img |
| go get -u golang.org/x/crypto/bcrypt | |
| go get -u golang.org/x/crypto/blowfish | |
| go get -u golang.org/x/crypto/bn256 | |
| go get -u golang.org/x/crypto/cast5 | |
| go get -u golang.org/x/crypto/curve25519 | |
| go get -u golang.org/x/crypto/hkdf | |
| go get -u golang.org/x/crypto/md4 | |
| go get -u golang.org/x/crypto/nacl/box | |
| go get -u golang.org/x/crypto/nacl/secretbox | |
| go get -u golang.org/x/crypto/ocsp |
The standard way of understanding the HTTP protocol is via the request reply pattern. Each HTTP transaction consists of a finitely bounded HTTP request and a finitely bounded HTTP response.
However it's also possible for both parts of an HTTP 1.1 transaction to stream their possibly infinitely bounded data. The advantages is that the sender can send data that is beyond the sender's memory limit, and the receiver can act on
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <title>Web Components</title> | |
| <style> | |
| body { | |
| font-family: 'Helvetica Neue'; | |
| } | |
| </style> |
This is a story about how I tried to use Go for scripting. In this story, I’ll discuss the need for a Go script, how we would expect it to behave and the possible implementations; During the discussion I’ll deep dive to scripts, shells, and shebangs. Finally, we’ll discuss solutions that will make Go scripts work.
While python and bash are popular scripting languages, C, C++ and Java are not used for scripts at all, and some languages are somewhere in between.
Vertical decomposition. Creating cohesive services
One of the biggest misconceptions about services is that a service is an independent deployable unit, i.e., service equals process. With this view, we are defining services according to how components are physically deployed. In our example, since it’s clear that the backend admin runs in its own process/container, we consider it to be a service.
But this definition of a service is wrong. Rather you need to define your services in terms of business capabilities. The deployment aspect of the system doesn’t have to be correlated to how the system has been divided into logical services. For example, a single service might run in different components/processes, and a single component might contain parts of multiple services. Once you start thinking of services in terms of business capabilities rather than deployment units, a whole world of options open.
What are the Admin UI
| // roughish AMP attribute types for JSX/TypeScript | |
| // Source: https://playground.amp.dev/amphtml-hint.json | |
| // https://github.com/Microsoft/TypeScript/issues/15449 | |
| // https://stackoverflow.com/questions/50585952/typescript-and-google-amp-property-amp-img-does-not-exist-on-type-jsx-intrin | |
| import * as React from 'react'; | |
| // why null ? | |
| type _ANY = any; | |
| type _ANYS = any; | |
| declare module 'react' { | |
| interface HTMLAttributes<T> { |
