I go outside daily in red rural America and this is simply not true. People voted, like they always have and always will, on their wallet and expectations on who will make it a little heavier. The exact same will happen as it swings wildly back the other way if gas doesn’t come back to normal.
Article is too opinionated IMO. I enforce CC on my projects because I don’t have the energy to police horrendous commit messages. It’s easy to enforce the CC format on the repo merge policy. I do it with the addition of a required issue ID as well.
If I only worked with seasoned devs, I wouldn’t use it, but that’s just the reality of my work. It also has a bonus of forcing AI agents to write in the same form as well instead of their random personal flavor. Precommit hooks stop everything before it gets in front of my eyes for review.
> I enforce CC on my projects because I don’t have the energy to police horrendous commit messages.
And does it actually accomplish that goal? I've been on several projects where someone pushed CC on the team with this reasoning. Every time my experience has been that you get the same crappy messages with a tag that may or may not be accurate.
BTW, AI absolutely knows how to bypass pre-commit hooks and will do so when they come up with some reasoning why their situation is an exception to the rule. I've watched them do it. The only way I've found to strictly enforce things on an agent (tests, linting, whatever) is to use a claude pre-command hook that will block git commit if the checks don't pass.
This is a nice little project but I’m weary of sensationally inaccurate titles for stuff like this and the infamous caveman mode. It doesn’t save 91% of tokens: it reduced in one user case 91% of output tokens on the raw CLI output. I am being pedantic about this because these sorts of claims go viral and are inaccurate.
A proper benchmark will compare a large sample of identical prompting with and without the tool, against a specific harness. Once you apply Amdahl’s law, there is no way this saves 91% of tokens holistically, which the title implies.
I work in a non-tech company and these sorts of things keep going viral, with no understanding and with no comprehension of what is actually going on. Engineering is gone and cargo cult magical incantations are in.
Understood. Didn't mean as a click-bait or something. Just sharing my cli report summarize.
Target user here in HN should be tech-savy and this tool is not designed for non-tech because it is required highly customized from user to get the result user want.
Anway, would you mind putting the correct title here ? I will consider to update.
I’m eager to test this out. I have agent instructions to try to limit the worst of this already, but patterns still sneak through. I have a review agent run after every single edit looking for all of the following if you need more ideas for checks:
- DRY principle violations, multiple definitions of the same helpers or utilities.
- Changes that deviate from existing patterns and architecture already in the code, especially in nearby and related code
- Comments that add no context or simply restate the field name.
- Naming violations (enterprise factoryfactoryabstraction stuff, excessively long names, overly technical names, banned words like “seam”, “durable”, and no-value-qualifiers like “SaveGame” -> “Save”).
- Tests that check implementations instead of correct business behavior.
- Overly backwards-compatible unless asked for (this one is incredibly hard to keep under control, as AI loves to guard everything even if the previous code was never deployed and thus there is no contract break)
- Un-necessary guard code (this is hard to control, most common case is the AI not relying on the serializer error handler and instead adding guards that the library already handles)
- Changing public API contracts without express permission to do so (depends on the code, eg a library JAR or versioned REST service)
- Meta references to previous code versions, to tasks or todos, or to instructions and other non-code context (e.g you tell the AI the adder should ignore negative numbers and that meta fact enters the comments or code)
I usually hand review all changes myself but it’s incredibly tedious so I try to first pass with the review agent until it comes back clean. I hate wasting tokens on it though.
Oh my gosh, the guard code drives me crazy. In try so hard to get Kimi to put in asserts instead of silently swallowing corrupt values, but it keeps handling bad values poorly instead of crashing. I've even explicitly put in CLAUDE.md that correctness is more important then continuing to run, but it still keeps defensively programming when it should loudly crash.
The art looks very rendered, with pixel cleanup in something like photoshop. I was using 3ds Max on my norma PC circa 2001-2002. Game studios should definitely have had 3d studio in the mid to late 90s on their actual workstations if they were Windows based (or lightwave). Crucially, The Sims (3ds max) released quite close in time and we know 4k was also 3dsmax, so I think it’s fairly safe to say Maxis was a 3ds shop in this era. It was ubiquitous in pc gaming of the era.
In the 2000s SC4 was already using 3DS Max, but here we are talking about a game that started development in 97. And they already had 3D games before it...
In SC3k sprites you can also clearly see two different grid sizes, so at the very least the retouching and some props are "pixel art".
History is important here. React came at a time when so many frameworks used custom template libraries for variable binding, looping, conditionals, etc. Usually it was some HTML/XML-like markup language.
None of the 5 places I have worked is this possible, but they are also all highly regulated industries. Firewalls block virtually everything by default.
No way wealth tax covers the debt. It would be more of an asset seizure and forced sale or nationalization of a bunch of businesses and illiquid asset classes. The rich don’t hold enough cash to make it happen.
The other issue is the U.S. deficit is a feature not a bug. As long as the world buys the bonds, it’s “free” and no one will care until forced austerity happens.
Look into the end of the Gilded Age to see how this really gets fixed.
Nationalization is arbitrary and wrong. That's not what I'm proposing.
We'd largely be transferring shares in companies to the treasury bond holders, ie the people and orgs who hold US debt.
The federal government might for example force mega-sized private companies like Koch Industries to go public to get an accurate market valuation (or just sell it to private equity by starting a bidding war on it across many private equity investors).
The wealth tax cutoff would be determined by the national debt. It might fall to a relatively harsh / low threshold like 99.9% of assets over $20 million. Or maybe 99% of assets between $20 million to $1 billion, and 99.9% on assets above $1 billion.
Treasury bonds themselves would be subject to the wealth tax, so someone with $100 billion in T bonds might just see 99% of $80 million erased. So even the total number of T bonds payable will drop under this wealth tax.
But someone with $100 million in shares in private and public companies will see their shares transferred to the federal government, and then eventually sold.
Once every T bond has been paid off, Congress and the states could try to close the centuries-long chapter on debt by trying to pass a balanced budget constitutional amendment.
This should clear the path to the IPO and lead to a VERY profitable payday for those holding OpenAI equity. Millionaires and billionaires will be minted ~one year from now.
reply