CUPID is a framework for creating "joyful code" that humans can understand and enjoy working with. As Martin Fowler noted: "Good programmers write code that humans can understand."
Prisma does not suffer from the same unordered migrations problem that affects Kysely. While Kysely strictly enforces alphabetical/chronological ordering of migrations and fails when migrations are executed out of order, Prisma uses a more flexible approach that tracks migration history in the database and provides tools to handle divergent migration histories.
When multiple developers work on feature branches simultaneously, they often create migrations with timestamps that become out of order when merged. This is a common scenario:
- Developer A creates migration
20240112_1200_add_users.sql
on their feature branch - Developer B creates migration
20240112_1201_add_products.sql
on their feature branch - Developer B merges first, production runs the 12:01pm migration
- Developer A merges second, but now there's a problem...
https://graphbrainz.fly.dev lets you do cool GraphQL queries.
query {
lookup {
artist(mbid: "144ef525-85e9-40c3-8335-02c32d0861f3") {
Created with bpb:
-----BEGIN PGP PUBLIC KEY BLOCK-----
mQAzBGTipBYWCSsGAQQB2kcPAQEHQK/+Oj+06V3IFv4BEdKuXQ5godXI0Wg8cRqDXcamiIXOtQAn
S2V2aW4gQ2hlbiA8a2V2aW5taWNoYWVsY2hlbkBnbWFpbC5jb20+iQB7BBMWCAAjFiEE0kLROtLI
1OXia6+OP7v1LOaxiH4FAmTipBYCGwMCF4AACgkQP7v1LOaxiH5IxgD+IsUdRudiISj9DYgKUPTf
E2qKrrPfMCgCVthFwEAYHVAA/iXnG0LyF0yHn9plrV4Y3DiS09V+lVekLzXH3DSFSDgI
=4ktF
# lives in ~/.tmux.conf | |
set -g activity-action other | |
set -g assume-paste-time 1 | |
set -g base-index 0 | |
set -g bell-action any | |
# had to comment this out to g et it to work | |
#set -g default-command | |
set -g default-shell /usr/bin/zsh | |
set -g default-size 80x24 | |
set -g destroy-unattached off |
{ | |
"meta": { | |
"theme": "elegant" | |
}, | |
"basics": { | |
"name": "Kevin Chen", | |
"label": "Software Developer", | |
"picture": "https://avatars3.githubusercontent.com/u/5129994?s=400&v=4", | |
"email": "kevin.chen.bulk@gmail.com", | |
"phone": "(202) 738-4916", |
Source: https://medium.com/@jsoverson/exploiting-developer-infrastructure-is-insanely-easy-9849937e81d4
The compromised dependency in event-stream
was flatmap-stream
.
flatmap-stream
would ingest a data file that it was bundled with the following "Bootstrapping Code":
var r = require,
t = process
function e(r) {