I assume he is referring to the uptick in stablecoin adoption. USD Stable coins are US dollar-backed cryptocurrency tokens that are intended to always hold a value of $1 USD.
Stablecoins are not backed by a central bank. Instead their source of value comes from a private company that holds actual US dollars or USD-equivalent reserves (like treasury bills, etc).
"Developers talk not just about how the AI output is often flawed, but that using AI to get the job done is often a more time consuming, harder, and more frustrating experience because they have to go through the output and fix its mistakes."
This has not been my experience. Sure it feels like more work to fix the AI code problems sometimes - it is a different skillset than writing code from scratch. But the speed that I can deliver software has significantly increased by using coding agents.
A "few seconds" to pay in bitcoin? So the captain is supposed to be watching for a response via email with his finger hovering over the pay button? Is the recipient address static? Surely they would use unique payment addresses if they have any hope of obfuscating payments.
This all sounds more like a TV show script than an actual thought-out plan to me.
I use YNAB. I thought about building my own now that AI coding make this feasible. But the moat that I can't cross is the integration with my bank accounts. Plaid and the like are too expensive and don't cater to one-off users like me.
Has anyone been able to find a personal financial data provider that has a reasonable price?
While I applaud this effort for flagging AI slop generators, I would caution users to not always ignore your "foes".
Reading opposing viewpoints is so important and is becoming a lost art in our society. I encourage you to understand and empathize with people you don't agree with. It will help all of us in the long run.
The second half of that argument was not in this article. The author was just relating his experience.
For what it is worth, I have also gone from a "this looks interesting" to "this is a regular part of my daily workflow" in the same 6 month time period.
AWS Amplify was supposed to solve this. It is built on the AWS CDK. But I found it too clunky and slow and gave up on it.
These days I use SST (https://sst.dev) which is built on top of Pulumi. I find this to be a manageable infrastructure-as-code solution for AWS deployments.