iamjfu

The CLI is actually useful. It gives the skills a way to deterministically interact with the spec. For example, it can validate the shape without having to spend tokens reading the files.

You can’t always control what your children or family do. You are in control of what you buy.

If I ask, "I want to wash my car. The car wash is 50 meters away. Should I walk or drive?"

It says, "Walk — it's 50 meters, about a 30-second stroll. Driving that distance to a car wash would be a bit circular anyway!"

However, if I ask, "The car wash is 50 meters away. I want to wash my car. Should I walk or drive?"

It says, "Drive — it's a car wash! You kind of need the car there. "

Note the slight difference in the sentence order.

I am interested by this link: https://blog.fsck.com/blog/2025/superpowers/superpowers-demo...

``` Claude Code v2.0.13 Sonnet 4.5 (with 1M token context) Claude Max /Users/jesse/tmp/new-tool/.worktrees/todo-cli ```

How does this person have access to Sonnet 4.5 with 1m token context? I don't see this referenced anywhere when I search or when I ask Claude about it.

From a related nature article (https://www.nature.com/articles/d41586-024-02383-9), "null or negative results — those that fail to find a relationship between variables or groups, or that go against the preconceived hypothesis." According to this definition, I think both examples you provided are null results. Particularly here, where the context is the file drawer problem.

Nice work!

I wonder if instead of complexity you should call this a cheaper alternative to a smart doorbell?

I don't think many of us think of smart doorbells as particularly complex. However, they could be out of budget for many.

Alternatively, you could market as privacy respecting, where a smart doorbell is always recording.

I created this nozzle pattern package as an alternative to the circuit breaker pattern. Would appreciate hearing any ideas on how to improve it and if there are already circuit breaker alternatives out there!

It is not.

In this case, complaining made me aware of the issue. I've known about patent trolling but not this particular kind. So complaining is a form of raising awareness which could be a good first step if system reform is needed.

I'm sorry for all the negative comments you're receiving in this post. I'm sure you worked really hard on this and I know it sucks when you share something like this and all people say is negative things.

My team and I have actually been looking for something like this. Not to judge engineers productivity but to understand workload imbalances. For example, say we notice 2-3 people are doing all the PR reviews (something I think we could detect with this). Maybe the other engineers need training on PRs or we need to set expectations that everyone reviews PRs or maybe our PR load balancer isn't set up correctly.

So, good work and good luck. I'll definitely be showing this to my team. Thanks for sharing this with everyone!