Huh? Some stacks need to land all at once and need to be reviewed (and merged) from the top down. It’s not uncommon, in my org at least, to review an entire stack and merge 3 into 2 and then 2 into 1 and then 1 into main. If 2 merges before 3, you just rebase 3 onto 1.

That's a pretty sweeping generalization. Just because I don't value the act of typing into a keyboard doesn't mean that I don't value the craft of creating and understanding software. I am not outsourcing my understanding to the LLM, I am outsourcing the typing of the code.

What you are describing is not engineering, it's (pardon the phrase) vibe coding. Claude Code is just a tool, and everyone is going to use that tool differently. There is nothing inherent in the tool itself that requires you to surrender your agency and understanding. If you do, that's on you, not Claude.

… yes? We have a few wrapper scripts around worktree operations that copy some docker volumes (pg data, bundle cache, etc.) from the base and spins up an entirely new stack on different ports with a host alias. We don’t have to install any deps beyond that because we copied over the ruby gems bundle cache and we’re using Yarn PnP + “zero installs” for client-side deps.

Sci-fi: Exiles by Mason Coile.

Fiction (Fantasy): The Bright Sword by Lev Grossman.

Fiction (post-apocalyptic / zombie): One Yellow Eye by Leigh Radford.

Non fiction: The Wager by David Grann.

We've taken those prompts, tweaked them to be more relevant to us and our stack, and have pulled them in as custom commands that can be executed in Claude Code, i.e. `/research_codebase`, `/create_plan`, and `/implement_plan`.

It's working exceptionally well for me, it helps that I'm very meticulous about reviewing the output and correcting it during the research and planning phase. Aside from a few use cases with mixed results, it hasn't really taken off throughout our team unfortunately.

Honestly I don’t see us going back to streaming. The content isn’t that compelling; most of what we watch is older (we have kids, so lots of Disney movies), and we’re not really interested in most of the newer shows that would warrant us paying a subscription in order to watch new episodes as they drop. Before we cancelled, I remember looking at the carousel on my Netflix Home Screen and being completely uninterested in any of the content they were pushing.

I’m also not worried about some licensing deal nuking one of my kids’ favorite movies from the catalog now. No ads is just the cherry on top.

When I'm on the go I don't really do any building, I'll add/edit a markdown file, push it to the remote in a branch. Cloudflare Pages will then give me a preview environment. If I like what I see, I merge the PR and it automatically deploys to "production."

Yes, there are problems with crime reporting. Yes, violent crimes have been on a downward trend since the 1990s. Things can be both bad and getting better at the same time.

Graphite is quite hostile to collaborating on stacked branches. If one dev restacks and a collaborator is working in a dependent branch, they’re hosed. If a collaborator pushes a change to a dependent branch and they're not using Graphite, hosed. I think one of the main problems is that Graphite abstracts out potentially dangerous git commands into a fancy CLI such that the dev doesn’t really know what’s happening under the hood. It makes things even worse if you’re trying to collaborate on stacked PRs and not all devs use Graphite. Just forget about it.

We could have just been using this tool “wrong” but we had to stop using it within our team because it became so disruptive. At the time it seemed like you should only use Graphite if:

1. You are the only person working on a stack. You do not expect collaborators to be pushing changes to any of the branches within the stack, and

2. Everyone on the team is using it too.

Maybe things have changed in the intervening time, but I’m always dubious of tools like this.

It’s just git. It’s a wrapper CLI around git with a nice GitHub PR integration and a dashboard. It’s already easy to stack branches in git.

Kind of difficult to take this seriously.

A SvelteKit[0] app hosted on Cloudflare pages. The repo is hosted on GitHub and hooked up to the Cloudflare Pages app [1]. On PRs, I get preview environments. On merge, the changes get deployed to my "production" website. I write blog posts and other content in markdown, which is then processed by mdsvex[2] with very minimal setup.

Mostly, my requirements were more focused around getting the actual framework, hosting, etc. out of my way so that I could focus on writing. Gatsby and Next.js were too configuration heavy and turned me off once I scratched beyond the surface.

[0] https://kit.svelte.dev/ [1] https://developers.cloudflare.com/pages/configuration/git-in... [2] https://github.com/pngwn/MDsveX

- Smil, Vaclav. How the World Really Works: The Science Behind How We Got Here and Where We're Going.

- Doucleff, Michaeleen. Hunt, Gather, Parent: What Ancient Cultures Can Teach Us About the Lost Art of Raising Happy, Helpful Little Humans.

Historically we’ve set aside a certain capacity, in almost every profession, to bring up and train the next generation. Apprenticeships, internships, etc. By definition, these people are shitty at their jobs, and that’s kinda the point. Were you brilliant at your first position?

> A similar vulnerability exists in Google’s Android mobile operating system.