I truly believe we're here because of Facebook.
3,818 karma · joined March 15, 2012
webmaster @ notion
email me! scalesjordan@gmail.com
I truly believe we're here because of Facebook.
This creates 45 degree corners on the borders which are an uncanny valley to me [1]. Feel free to lift any CSS you need from https://jdan.github.io/98.css/, it's MIT licensed. I used a box-shadow hack to get the "staircase" look.
> box-shadow: inset -1px -1px #0a0a0a,inset 1px 1px #fff,inset -2px -2px grey,inset 2px 2px #dfdfdf;
[1] https://notes.jordanscales.com/98-css-reflections#when-butto...
> Find three diverse, substantive Hacker News articles submitted within the previous 24 hours. Prefer readable linked articles rather than discussion-only, video, paywalled, or repository pages. For each selection, extract a clean UTF-8 XHTML-compatible article fragment and use dotepub's API to create an EPUB under public/books/ with a descriptive `Title - Author.epub` filename. Fix any EPUB 2 packaging or markup problems, including an invalid `xml:lang` on the OPF package element, and require every file to pass `epubcheck` with no errors before upload. Avoid duplicates already present locally or in the production OPDS catalog. Upload only the three newly created EPUB files to `hetzner:/opt/opds/public/books/`; never sync or delete the whole directory. Then verify production `/up` returns 200, unauthenticated `/opds.xml` returns 401, authenticated `/opds.xml` returns 200 and includes all three titles, each download returns `Content-Type: application/epub+zip`, and deployed copies pass `epubcheck`. Report the selected article titles and URLs, filenames, and verification results. Follow the repository AGENTS.md instructions and keep production credentials secret.
> Tabs should be managed by adding custom javascript code. All you need is to add the [aria-selected=true] attribute to the active tab.
The evidence that per-token inference _is not_ subsidized is... a quote or two from Dario and Sam Altman
Things programmers forgot to do before AI started writing a bunch of software:
1. Learn how to review code
Some tools exist, some of them are even quite good! Large organizations have tried to build best practices to balance urgency with correctness, but programmers are still quite bad at this.
2. Compare program A vs program B
In a similar vein, we simply do not know how to measure one program vs another. Or a function against another. Or even one variableName vs another_variable_name.
"It depends" Depends on what? We never sorted this out.
3. Talk to other professions
We are not the first profession forced to coordinate with Automation as a coworker, and we certainly won't be the last. We're not even the first knowledge workers to do so.
How did other laborers deal with this? We don't know because we were busy making websites.
[0]: https://bsky.app/profile/did:plc:wh7bie3ld7bmg3cz76sbjkwj/po...
I wonder what his life in Tokyo was like! Did he ever write about it?
Corporations absolutely have an effect on all of this, you can bet they'd save time and money by focusing their efforts elsewhere if they thought it was pointless.