bizzletk

Maybe they're better named Brazilian Staying-Put Spiders then

I've always enjoyed the "I sell onions on the internet" story:

https://www.deepsouthventures.com/i-sell-onions-on-the-inter...

CTOs have found reasons to standardize on k8s and it's not just for technical reasons. This was recently discussed last week:

https://notnotp.com/notes/what-job-interviews-taught-me-abou...

https://news.ycombinator.com/item?id=48546428

Not all bad behavior meets the threshold of police intervention.

Here's a nearly-strawman-but-definitionally-valid example: a landlord may want to remove a tenant who's being unusually hard on the place and accelerating the wear-and-tear. Could be serious enough that paying the tenant to go away would be cheaper than the cost to remediate the damage accrued over the length of the contract.

Wouldn't the real story be to get government contracts? Those are more immune to public fickleness and market competition and usually have truly ludicrous margins.

If they're the only ones who ̶a̶r̶e̶ ̶w̶i̶l̶l̶i̶n̶g̶ ̶t̶o̶ ̶b̶e̶ ̶t̶h̶e̶ ̶e̶n̶g̶i̶n̶e̶ ̶f̶o̶r̶ ̶a̶u̶t̶o̶n̶o̶m̶o̶u̶s̶ ̶k̶i̶l̶l̶b̶o̶t̶s̶ can draw a reciprocation dingle-arm to reduce soinosoidal repleneration, then "I'm sure the government will buy it" [0]

[0] https://youtu.be/Ac7G7xOG2Ag?t=89

Write your code in Go

Container not even needed, there's projects like Tamago [0] that let you run your golang application without even needing an OS

[0] https://github.com/usbarmory/tamago

And also the mandatory "Treaty, Yeah!":

https://www.youtube.com/watch?v=RPmDLR_M50M

someone needs to work with the business to extract the information. Typically it's not well documented.

LLM extraction of the information from the Product Owner is becoming the way to overcome poorly-documented business context.

Non-technical folk are using things like `/grill-me` [0] to seed the LLM with the long-tail complexities that they didn't know they didn't know they needed to put out.

[0] https://www.aihero.dev/my-grill-me-skill-has-gone-viral

Does Claude leverage the trailers automatically, or is usage initiated by you?

Trailers hint is in my global CLAUDE.md so it knows: when debugging, saying something like "didn't we already discuss this in a previous session?" it will know what to look for.

I also have a manually invoked `/search-session-transcripts` that I can use to natural-language inspect previous session by day, project, session id etc. Claude often uses this skill to narrow down on parts of the conversation that are relevant to the current query.

How often are you using the trailer lookups?

Mondays are usually the day I need to refer to previous sessions from the week before. Trailer lookups are also good for continuing buildout of adjacent features. They've also been excellent in incident post-mortems where the PR text and commit message aren't enough to gauge the "how" of decisions that led to issues.

Any idea how this relates to token usage?

I tested this. Session-transcripts are append-only so `/clear` and `/compact` don't clear out old messages, they stay stable and accessible. I also don't clean out my `~/.claude/sessions` ever so there's a lot in there, but the info is valuable and cheap.

I've been attaching to my commit messages a Git Trailer [1] of the Session UUID from the Claude Code conversation that created that commit.

It allows Claude to look back into the session where a change was made and see the decisions made, tradeoffs discussed and other history not captured by code, tests.

[1] https://git-scm.com/docs/git-interpret-trailers

Can you enumerate why?

https://en.wikipedia.org/wiki/Do_Communists_Have_Better_Sex%...

Something like this? https://github.com/brycehans/toolgate

Wait till you see the Honda Electro Gyrocator:

https://en.wikipedia.org/wiki/Electro_Gyrocator

Or humans are just the "sex organs" that work to bring about the artificial life-forms that come next.

How would you compare it to similar things in this space like Mog?

https://news.ycombinator.com/item?id=47312728

Can you enumerate some examples of when it having less information is better than having more?

What are some things that you'd build with Unity that aren't games?

How do you think your framework compares to the very popular Claude Superpowers framework? It looks like it has a lot of overlap.

https://github.com/obra/superpowers

Not sure all this AI-driven workflow is necessary. The dog could just create a muddy mess and it would be valid Perl:

https://www.mcmillen.dev/sigbovik/

Would you mind expanding on the scientific-ness of paganism? That sounds really interesting!

The article addresses this:

This made sense when agents were unreliable. You’d never let GPT-3 decide how to decompose a project. But current models are good at planning. They break problems into subproblems naturally. They understand dependencies. They know when a task is too big for one pass.

So why are we still hardcoding the decomposition?

I love this idea, and have immediately put it to use in my own work.

Would you mind publishing the `PROJECT_MIND_MAPPING.md` file that's referenced in `MIND_MAP.md'?

I don't recall having computer crashes out of the blue...

I think usually Windows machines crash into blue instead

If you have 100% confidence about this, you could make a lot of money on betting platforms like Polymarket.

I'm sure someone would take the other side of your odds, and if you're right, you win.

Programmers have the ability to write tools that make their jobs/lives easier. This is the perfect alignment of incentives where the person who benefits from the production of a high-quality tool has the ability to deliver one into their hands.

And once the tool has been made, many people just give it away for others to benefit from too.

It's easy to point to home runs as entertaining, but they a ultimately rather boring. For die hard fans, you want more hits that end up in play, with more strategy, and more opportunity for mistakes and drama. You're not going to get that from home run derbies.

There's a counter-example in Cricket.

The game used to be a 5-day long battle with daily skirmishes and tactical changes required according to the ebbs and flows of the weather, the players, the score each day. Sometimes you could win just by exhausting the other team, sometimes you could gain advantage by changing your play style transiently to force the other team to react. The players all wore white uniforms, national pride was wrapped up the success of the country's team and being a Good Sport was the highest ideal.

Then, the powers that be created a shorter variant, the One-Day Match. The players started wearing brightly coloured uniforms, the crowds grew louder and entire categories of strategy were rendered useless as the game finished in 20% of the time. Viewership increased, cricket became "exciting" and the players sometimes achieved rockstar status usually reserved for sports that more easily captured the Australian sporting imagination like swimming and athletics.

The trend was clear: the entertainment value of short-form cricket games were spectacular. In came a myriad of new sponsorship categories for things like domestic household goods ("It's Australia's Favourite Air"), energy drinks and Sports Utility Vehicles that would appeal to the demographic of viewers who only had a "day's length investment" in the game. They started playing popular music in between game pauses and the Gentlemanliness of the game's spirit gave way to Victory as the highest Ideal.

Then, Cricket had it's "YouTube Shorts" moment -- an even more abridged version of the game that only lasted 20 overs per side was born. This hyper-speed version of cricket favoured fast results, flying balls and fan participation like never before. There was now fireworks and rock music and after-parties and more. It was All Killer, No Filler. The goal was to Smash It Outta The Park as much as possible, and every time they did it, a quick ad-break got to play on TV while the fans in the crowd got to sing Seven Nation Army while cheering on whoever caught the ball this time. The domestic competition is even called the "Big Bash League".

Australian Cricket's archetype went from Twelve Magnificent Fellows in Baggy Green Hats to what feels like a monster truck rally with branded personalised beers, bucket hats, and brand-safe team rivalries. Sometimes they even drive a Ute truck around the stadium at half-time.

What I'm trying to say is that popular demand or the voices of those who claim to interpret it say that Spectacle Isn't Boring. They love the exciting moments, and maybe are only willing to tolerate the slow and strategic sides of the game to get to the next Home Run. This trend towards shallow spectacle seems to be happening to all forms of entertainment and I suspect that baseball is not immune.

People often ask why I hardly ever have any prod issues (zero so far this year).

It also helps that we're still only in January!

  Well I used to stand for something
  Now I'm on my hands and knees
  Traded in my God for this one
  And he signs his name with a capital G

[Astro](https://astro.build) is a production-ready alternative to Next.js and has been giving me great results.

You can render simple HTML/CSS/JS snippets where required, and go all the way up to Svelte/React/etc TSX components without ceremony when you need more complexity.