godzillafarts

Depends on your circumstances. I read it as a single male in university and loved it. Recently, I re-read it as an adult with two young sons. Absolutely devastating.

This doesn’t work in an org with stakeholders that don’t have access to the code base, I.e. most of the other company. You still need tickets, a way for stakeholders to follow, update, etc. those tickets, and a way to prioritize the tasks those tickets represent.

> For the tech industry, writing code is the main bottleneck of the business.

This couldn’t be further from my experience; producing code has never been the bottleneck.

There are not details on this website about how it works, what data it needs, etc.

All CTAs just lead to a signup page. Why do I need an account to check my weather forecast? A ZIP code, sure.

Also the "Core weather is free" qualifier leads me to believe that some features not in "Core weather" are paid? Which are those? I'd want to know that information before I go through the trouble of creating another account.

I just wrapped up the Murderbot Diaries series and am starting in on Dungeon Crawler Carl.

I normally read a lot of nonfiction and history and am trying to make a point to read more fiction this year.

I want to read this, but the ever-changing linear gradient of the background is too visually distracting. I tried to get around it by highlighting text I want to read, but since the background is changing underneath it, so is the highlight. My eyes hurt.

My org, like every org, is struggling with this as well. We find ourselves writing skills like `/decomment` and often running several "minimize" passes on PR descriptions, etc.

One thing that has markedly helped is tweaking our AGENTS.md prompt and prose-heavy skills like `/pr` or `/ticket` to specify that all technical output needs to be written in ASD-STE100 Simplified Technical English. It has helped us so much. We still have to `/decomment` or minimize to remove unnecessary stuff that's been written in ASD-STE100, but the output is a lot easier to digest.

OTOH, we have a guy in marketing that has taken it upon himself to use Claude to draft these wildly complicated and dense implementation specs that he doesn't understand for various things that he just hands off to my team to implement. He has no context for how our product is built, the various layers and their interactions, etc. so they're often flat out wrong and overly complex, invent systems that do not exist, all of that. Then he gets mad that we're not moving as fast as he wants, because he gave us the implementation spec! I have been struggling to come up with a way to diplomatically tell him that his actions are slowing us down, and if he'd just describe what he needs instead of speccing it himself, we'd be twice as fast...

Tend to the other agents

+1 this isn’t something new, it’s been possible all along in native git if you’re willing to do branch management and rebasing yourself. Just without the fancy UI / stack map.

“You cannot merge a PR in the middle of the stack before the PRs below it are merged.”

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.

> People who love using AI to create software are loving it because they don’t value the act of creating & understanding the software.

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.

> When you start a feature branch on your own, do you create an entirely new development environment to do it?

… 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.

My favorites this year, be genre:

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.