> Site designed by the author's granddaughter, who did the work while avoiding the far more weighty assignment of her literature test.
Impressive for 1995, he must've thought her HTML and how to use a computer first
HTML 2.0 came out in 1995
373 karma · joined January 13, 2021
> Site designed by the author's granddaughter, who did the work while avoiding the far more weighty assignment of her literature test.
Impressive for 1995, he must've thought her HTML and how to use a computer first
HTML 2.0 came out in 1995
https://danielfalbo.com/university.md
[1] https://en.wikipedia.org/wiki/University_training_credit
I feel like Apple Music Hi-res + my DAC and headphones sounds way better than either of the samples from the test
You're right, but there are coffee shops that are actually friendly to work at. When I was living in Rome, I compiled for myself a maps list of work-friendly bars https://maps.app.goo.gl/8nZUdYEbs7H8MCDd7 - Now I moved to London and I'm doing the same
> [...] Telling a Story with Commits [...]
> [...] it should take the average reviewer 5-10 minutes [...]
Jane Street code review system kinda solves this problem by
- making each commit a branch,
- stacking branches on top of each other (gracefully handling rebases and everything that comes with it), and
- reviewing one iteration at a time
So one reviews single commits independently (takes probably around 5mins), and "forces" the reviewer to re-live the story that led to the bigger diff.
I do not work at Jane Street but I frequently find myself pondering on how broken the common code review system/culture is. I've heard of tools like graphite.dev that build on top of git to provide a code review system similar to the Jane Street one, but I'm not an active user yet (I just manually stack PRs, keep them small and ask for review to one at a time to my colleagues, and handle the rebasing etc. manually myself for now).
PaulXStretch software: https://sonosaurus.com/paulxstretch/
export const GET = funcToRoute(sayHello)