the bababooey saga continues

The proper way to do IDs

1. Auto incrementing primary key
2. ULID visitor key

You shouldn't let anyone outside of the system know about the auto incrementing ID. This means you shouldn't use it in URLs, you shouldn't return it in your API responses. For all the above cases you should use a visitor key, which you store along wih the auto incrementing key. It's use is interfacing with the outside world, like in URLs and stuff. And finally you should only use the primary key for table relations.

but real men use a global variable as a db
their code never crushes and
they just buy more ram when they ran out

Somebody should rewrite sqlite-web in rust with a better UI.

error page or art, choose both

Hyphenation shouldn't be a thing, just write the word on the next line.

This is a very futuristic thing to do now and they were doing it in 1995.

[Lisp in Web-Based Applications]

"Like the creators of sitcoms or junk food or package tours, Java's designers were consciously designing a product for people not as smart as them." - Paul Graham

[Java's Cover]

EPUB > PDF

We all knew this was happening. If yall are interested in lisp, join this group.

https://t.me/lisp_et

"The most important part of design is redesign."

"mr tik-tak-toe"

Governmental
NSFW

😂

shouldve been bababooye

For anyone interested in the video he made: https://www.youtube.com/watch?v=hDJ5vXRPZCE

Stop naming generic type params, with one letter variables. Use descriptive names as you would for regular variables.

"A person is smart. People are dumb." - Agent K

Sam Altman + All-In
Today's gonna be a great day.