paperpunk
But there is another reason why some may prefer standard: due to the instant payment rules banks are not able to hold inbound payments for screening so if a payment trips a flip that requires screening then it will be rejected. Other payment rails will typically result in the payment being held for a manual review where it will be released shortly later. Instant payments will be rejected if not crediting the recipient in a few seconds.
As this disproportionately affects people with names in common with sanctions lists, to send money to/from those people sometimes a standard transfer is the only option.
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.
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 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.
- 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.
Is it high fees, is it overly burdensome sanctions/AML checks, something else?
I'm pretty sure this will work on day 1 on Vision Pro since Xbox Cloud Gaming already works on Safari with PS/XBox controllers paired to Macs/iPads/iPhones, and with the supposed higher quality display, passthrough, and user interface (the Quest hand tracking is insufferable) I expect it will be even better.
[1]: https://news.xbox.com/en-us/2023/12/13/play-xbox-game-pass-w...
Was able to do latency-sensitive gaming like VR gaming from a Shadow PC 200 miles away. Have happily streamed PC games to my phone whilst out and about on 4G networks. I suppose if you're comparing it to 4K ultra quality local gaming you might find it much worse, but for someone who only has a MacBook Pro I found it performed significantly better to stream the game from a PC elsewhere than to try to run Mac native versions of games – and also just let me open up high quality games very quickly from many devices without having to mess around with cables and device drivers and all that stuff.
My partner streams the Xbox games to her Surface laptop which is definitely not powerful enough to play them natively.
That said I know it's still fairly niche, but I think it has a shot of tapping into a much broader casual market than e.g. PC gaming and consoles which require people to already care enough to do a big upfront investment.
The linked article here talks about having structured, quantitive information, but I think this might be an engineer's view on medicine. The reality on the ground is much messier. We tried to give people enough information on medical practice, explanations on the biological/chemical mechanisms, and other resources to make their own informed choices about their treatment and care. For example, trying to explain the mechanics of taste, and texture for eating food so that people can understand what kind of adaptations they can make to improve their quality of life. I think we probably fall short of that goal sometimes because our material is overly technical or scientific but it's a work-in-progress.
There is I think. Something like Cmd+F3? I use this a lot.
- The monolith has to do all the work of the whole system when it starts, so start-up time is a lot longer, which makes rolling deployments much slower
- The monolith is much heavier in resource requirements, so it's much more expensive to spin up multiple of them
- The monolith has a much larger surface area, so post-deployment but pre-release verification is much more complex
- The migration path for a smaller service to support zero-downtime is simpler than for a larger service, so on average it's probably easier to get it working for an existing 'microservice' (although may be easier for the monolith than an equivalent full set of microservices)
We never reached an agreement but someone did make a claim, that I was unable to verify, that modern users don’t use the back button and therefore relying on it to allow users to find their way back is unacceptable. I wonder if anyone else has heard that (I suspect the HN crowd knows about the back button though ;))
Perhaps just because I've dedicated a lot of time to it but I think something like React makes it a lot easier for me to find where my performance bottlenecks are and eliminate them vs. mixed server-side dynamic HTML / progressive enhancement.
I'd still rather use hooks though :)
The CMS design comes into it because when you have a larger collection of non-technical authors you need an accessible way to manage the content. This was how it was initially conceived anyway - in practice more development time had to go towards handling the users' existing workflow (MS Word) rather than migrating them into the CMS directly. A real eye-opener for me about user-centred design..