turadg

Sounds like Magic Wormhole (https://magic-wormhole.io/). The readme acknowledges Warner at the end.

Key differences seem to be resumable transfers and proxy support.

Another is a single binary, whereas MW is in Python, but there’s now https://github.com/magic-wormhole/magic-wormhole.rs

I appreciate that the project acknowledges its inspiration. I wish it were more common for projects to provide detailed comparisons with similar ones for people trying to choose.

Funny that “GitHub should really support stacked diffs” led the Graphite team to a space colonization co.

2020: Leave Meta and start a company.

2020–2021: Spend ~18 months looking for PMF.

2021–2025: Build Graphite around stacked PRs, code review, and merge queues.

2025: Get acquired by Cursor because AI makes code review the bottleneck.

2026: Cursor gets acquired by SpaceX because Elon.

Not a startup arc I would have predicted from `gt stack submit`.

Broken promise 1 (Automatically generating CHANGELOGs) is spot on, especially in a monorepo with multiple released artifacts. A single commit could be a breaking change in one package and refactor in another. But the changelog tools see one commit and include it in both changelogs.

Another issue is that once the commit lands on trunk, you can’t revise the entry without editing history. You have to remember to fix it after the changelog is generated.

Changesets (https://github.com/changesets/changesets) is a much better approach. We adopted it in Endo (https://github.com/endojs/endo/tree/master/.changeset) and it’s been a clear improvement.

The new *deno pack* command is a nice addition for safe and simple packaging.

For those using Node.js, a similar single command is available with https://www.npmjs.com/package/ts-node-pack

Now that Node.js supports importing .ts modules, more repos can use them without a build step or putting any build artifacts in the checkout.

Git worktrees are awesome but they broke my workflow in a couple ways:

Resuming work. I used to `j <reponame>` then `gco <branchname>`. Now if I do that I get an error about the branch being checked out already in another worktree. I realized the branch names are pretty unique across repos so I made ` jbr <branchname>` that works from anywhere.

Jumping within repo. The other kink was when I wanted to focus on a particular package I’d do `j <subdir>` and it would usually be unique enough to jump to the one in my current checkout. But now I have dozens of concurrent checkouts and have to pick, even though I’m already in the repo. So `jd <subdir>` does like autojump or zoxide but only within the current checkout.

To power those shell functions I made a “where” extension for Git.

https://github.com/turadg/git-where

It’s working out nicely!

an allegory of SaaS in the AI age

Execa package works nicely for that. Zx has a good DX but is YA runtime.

https://github.com/sindresorhus/execa/blob/main/docs/bash.md

China begins assembling 2,800-satellite network of AI supercomputers

I was on a date when she asked “do you like magnetic fields?”. “Yes!” and we were both smitten.

Took us a few conversational turns to realize we had different capitalization. (This was in the old days when courting was mostly by speaking in person.)

I enjoyed the name Euphoria State University for his fictional model of UC Berkeley.

To combine this news with the AI zeitgeist, consider reading his 2001 novel, Thinks….

« Gen Zers, it turns out, are "not on a linear journey to evaluate the veracity of anything." Instead, they're engaged in what the researchers call "information sensibility" — a "socially informed" practice that relies on "folk heuristics of credibility." In other words, Gen Zers know the difference between rock-solid news and AI-generated memes. They just don't care. »

https://archive.is/BZIU8#selection-1855.0-1867.1

Same. I was curious what the differences are.

JSONPath can only pull data out, like XPath. jq can do much more, like perform transformations.

jq is also more concise:

  .book[0].title

versus JSONPath:

  $..book[0].title

Here's a discussion with more comparisons: https://github.com/serverlessworkflow/specification/issues/2...

Nice to see more systems architected on object capabilities. It's a more practical security model than ACLs: https://srl.cs.jhu.edu/pubs/SRL2003-02.pdf

Or more succinctly:

> Capability-based security enables the concise composition of powerful patterns of cooperation without vulnerability.

from https://github.com/dckc/awesome-ocap

  The requested URL was not found on the server.
    -- Old Apache saying

(I forget where I got it from for http://aleahmad.net/404 )

The weight-loss effects of GLP-1 drugs have little to do with the gut.

https://web.archive.org/web/20240305193736/https://www.theat...

Essay in "Possible Minds: 25 Ways of Looking at AI" from 2019.

Agree. It will be like text, which has always been trivial to conjure or alter.

It will be a blip in history that that there was a period in which producing a particular image required its contents to have existed in reality.

What we need going forward is a way to know provenance, where an image came from and what edits have been made. Then people can trust particular sources, as they do with text.

The Content Authenticity Initiative is working on that. https://contentauthenticity.org

This use case is a compelling use for blockchains https://research.adobe.com/news/content-authenticity-and-ima...

A recent article chronicling the rise and disillusionment of carbon offset trading:

https://web.archive.org/web/20231129175703/https://www.newyo...

A compelling case for a cause in the growth in teenage depression: reverse CBT.

> In CBT you learn to recognize when your ruminations and automatic thinking patterns exemplify one or more of about a dozen “cognitive distortions,” such as catastrophizing, black-and-white thinking, fortune telling, or emotional reasoning. Thinking in these ways _causes_ depression

The past decade these three beliefs have grown in prevalence:

1. What doesn’t kill you makes you weaker

2. Always trust your feelings

3. Life is a battle between good people and evil people.

They are all cognitive distortions and many schools today endorse them. Rather than teaching students skills of critical thinking, they encourage the distortions (reverse CBT).

This is a few hours old and probably won't get more comments. In case anyone else is curious, here are some articles that touch on the questions posed:

- Black developers tell how the US tech industry could do better https://www.infoworld.com/article/3571422/black-developers-t...

- What It’s Like to Be a Black Man in Tech https://hbr.org/2021/03/what-its-like-to-be-a-black-man-in-t...

- Being Black in IT: 3 tech leaders share their stories https://www.cio.com/article/193711/being-black-in-it-3-tech-...

Thanks for the soft critique.

I don't hold color blindness as an ideal. I know that human beings are hard wired to quickly determine in-group/out-group and skin color is a salient trait for that distinction. Not the only one of course, but we're never going to be blind to skin color.

What we can aspire to, you might call "color irrelevance". That in any particular endeavor, the relevance of one's skin color goes to zero. I don't believe we'll get there by ignoring the ways in which we individually and collectively, intentionally or not, let skin color shape our behavior and systems.

I'm surprised nobody has mentioned https://redwoodjs.com

Here's why I'd pick it:

1. One language for the whole stack. It's an MVP so the front and back are both changing fast, with changes made by the same person, and you don't want to context switch all the time.

1a. Javascript as that language because it's the most flexible. And with TypeScript you can gradually opt into type constraints where they help you.

2. An opinionated full stack like Ruby on Rails that integrates all the pieces I need to ship. When you assemble yourself, even small version bumps or outdated tutorials can send you down a rabbit hole, stealing time from testing PMF. You want someone to validate a combination in which all the pieces work together smoothly.

2a. Redwood.js closest to be being the Ruby on Rails of JavaScript. I've toyed with it before and got up and running quickly. Its opinions took a lot of unimportant decisions out of my hands and let me focus on what I was trying to produce. I didn't get so far as to confirm this but it also seems to make it easy to gradually drop the scaffolding if the opinions and simplifications ever get in your way.

How much should someone documenting an API be able to use it?

I've been interviewing for a technical writer and some very experienced people, who seem to be greater at the job of Technical Writer, don't have basic coding proficiency.

If my org needs a writer who can code too, should we be trying to find a _developer_ who wants to write too? Coding and writing seem like different careers paths so are we looking for a unicorn?

The gross receipts tax policy is from Proposition C. So decided by SF residents, not legislators.

https://www.vox.com/2018/11/7/18065086/san-francisco-prop-c-...

Fwiw there are some apps to hide menu bar icons:

- Open source https://github.com/Mortennn/Dozer

- Freemium https://matthewpalmer.net/vanilla/

- $15 https://www.macbartender.com/

The HTML is delightfully retro,

  <p align="left"><font size="+1" face="ARIAL,HELVETICA">
  Q: Interested in selling gail.com?<br>
  A: Sorry, no.</font></p>

> “He was a very enlightening person to think with — someone you would want to have a meal with at every opportunity,” Borgman said.

+1. He had (has?) an rare combination of intellectual humility with didactic ability and drive.

I remember getting to chat with him after he presented at Webzine. It was in an SF warehouse, exploring the sociotechnical phenomena we’d come to call blogs. It was 1999 IIRC because there was wine but I wasn’t old enough to drink it. He was happy to sit down with this kid, teach and listen.

This is a dilution of the meaning of "dark pattern". darkpatterns.org which coined the term (and Wikipedia cites) says, "When you use websites and apps, you don’t read every word on every page - you skim read and make assumptions. If a company wants to trick you into doing something, they can take advantage of this by making a page look like it is saying one thing when it is in fact saying another."

I don't see any of that in your observations. Moreover, what you attribute to some nefarious purpose is better explained by effective curriculum design. I haven't used edX lately but I worked at Coursera and I can tell you that the people who make that product have a passion to support learning in the world.

* Removing access to course materials: it's a course, not a content library. When you can access it anytime, you're less likely to do the work of learning. You also won't be part of a learning cohort, which is a valuable learning activity.

* Encouraging you to sign up for courses: this is a problem? Wouldn't someone who wants you to learn encourage you to sign up for courses? "Course began ($TODAY - 5)" that would be deceptive. Are you claiming that edX or Coursera does this?

* Breaking courses into chunks and quizzes. How the heck is this deceptive? This design decision is backed by learning science. Listening while doing dishes does not get you the best learning outcomes; it's a university-level course not a podcast.

* "Unsettling UI" "opportunity to pounce" I really don't know what to make of this one.

+1 to “one idea is one commit” philosophy (and article)

If you’re using GitHub try “Allow squash merging” https://docs.github.com/en/github/administering-a-repository...