I have a harness for Claude Code "hooks" (https://code.claude.com/docs/en/hooks) which in my case execute a Go tool in a separate project which runs changes made by claude through a validator with various rules that can be defined (regex, semgrep, etc.). They can warn claude or they can block changes outright.
When I find claude is using tools or approaches that I have replaced with more specific ones, I ask claude to add a hook to prevent doing this in the future and point it to the instructions of what to do instead.
And of course I wrapped all that up in a Skill so it knows what approaches to take to add things to hooks.
It becomes fairly trivial to incrementally stop it making repeated mistakes like this.
Tangential but when reading books like Lord of the Rings with songs periodically written in the text, I’ve always enjoyed trying to sing the songs out loud and set a melody for them that feels appropriate for the universe. It really makes the songs come alive.
Your comment is past tense - does that mean they’ve stopped doing this? Please, Lord. I had to set my ATV to go to screensaver in a ridiculously short amount of time to preempt the YouTube one.
I love Valve games and I love that they are spending their resources in areas I care about and that feel underserved by other companies, but I don't think the moral comparison is so clear cut. They were also pioneers in micro-transactions, loot crates, software distribution tax, and turning Counter-Strike skins into a speculative frenzy.
It’s not about the table element, it’s about the API to construct and manipulate that element with a columns and rows interface which is largely superseded by general DOM manipulation.
I feel like I could very easily write this list in the opposite direction.
1. I'll just fix it – as a junior you can get away with not working on something unless you're told to. As a senior you're expected to take ownership. Cut through organisational malaise. See a thorny bug not being solved because it sits slightly across team boundaries? Fix it.
2. Working nights and weekends – as a junior you can expect to just turn up during your work hours and nobody will bat an eyelid. As a senior sometimes you'll have to make sacrifices. Stay on late to deal with that incident. Monitor a vendor migration over the weekend.
3. Asking a lot of questions – as a junior you can get away with being shy and avoidant. As a senior you're going to need to push through the discomfort and ask the important questions, challenge people, and have gotten over your fear of looking stupid to ensure you always have the right information.
4. Being "Extra" Helpful – as a junior you can very much just focus on your project work. As a senior you're expected to find impact beyond what is given to you in JIRA tickets. You need to review other PRs, manage other projects, unblock team members questions. Your job is beyond just closing tickets now.
5. Loud enthusiasm – as a junior you are not likely to have the political capital to get your org to take a risk on a new framework, language, tool. As a senior you are expected to have the experience to be able to take those risks when they are appropriate for the situation.
It's true though that you need be thoughtful about whether your behaviour is what is valued in your job. Regardless of seniority, different managers, different companies can value traits that other companies punish, and visa versa. You can really suffer if you're not aware of what it is your managers actually want from you.
> In designing the digital ID scheme, the government will ensure that it works for those who aren’t able to use a smartphone, with inclusion at the heart of its design.
I was only disputing parent assertion that trust is a solved problem and that banks don't "need" a solution.
I haven't the foggiest if stablecoins solve these problems any better. In theory I think all participants having visibility into the ledger would at least answer the problem of "where actually is the money", but I'm not even sure of that though because of fiat on/off ramps, custodial arrangements, roll-ups that might happen off chain, etc.
I don't know if you could use smart contracts to encode a recall/dispute resolution process into transactions but that's very hand-wavey and possibly collapses under scrutiny!
All in I've no idea if crypto helps us here but I do think we have a long way to go either way.
It's not for lack of trying that traditional, "database driven" cross-border payments are costly and unreliable. SWIFT have thrown technology at this problem: GPI, Swift Go, ISO20022, etc.
Unfortunately the ecosystem has an extremely weak technical culture. Banks rarely follow the standards as written – your perfectly crafted API payment may be re-keyed by a low-paid human operator on a slow, buggy UI written a decade ago.
I could believe that the developer experience and technical standards of the participants is where the value lies right now.
The one thing I'm not sure on is to what extent those ecosystems depend on reduced regulatory scrutiny compared to banks.
I wouldn't really say trust is a solved problem in cross-border transfers. Why only today I've seen transactions where:
- an intermediary credited another institution only to realise later they didn't have the money, and have to beg pretty-please to return the payment over a SWIFT message (there is no guarantee here, at best there is "market practice" which is basically just manners, but for banks)
- an intermediary failing to credit the next institution because of a processing error, but when inquired from remitter claiming they had in fact credited it
Many of these cases are very expensive to resolve. Far more expensive than the value of the payments in question. And for that reason they are often left unresolved.
Now I don't know if I'm convinced on stablecoin remittance, I find many of the counter-arguments extremely compelling, but some days I sure do think gee it would be nice if everyone was transacting on a shared public ledger and I could have some certainty of the status of a transaction.
When I find claude is using tools or approaches that I have replaced with more specific ones, I ask claude to add a hook to prevent doing this in the future and point it to the instructions of what to do instead.
And of course I wrapped all that up in a Skill so it knows what approaches to take to add things to hooks.
It becomes fairly trivial to incrementally stop it making repeated mistakes like this.