Yes, that, accuracy, speed, and single computer-use.
I find those to be the limiting factors to speed.
I have extensive rules, I do extensive planning. Yet at implementation, the rules are not respected, errors are introduced, etc...
I spend more time fixing than writing code.
Then speed... Because of the fixes and bad code quality even with frontiers model speed makes a very big difference. I (agents) spend hours daily doing reviews and fixes. 5x speed boost would make me much more productive.
And when working super fast with agents, having only one computer is limiting. Even worktrees don't solve problems because I use things like convex, chrome use, etc... and it conflicts with each others all the time.
Still many problems to solve. It's already evolved so much in the last two years.
Also, I believe that if Apple is working on blood glucose estimation, it's probably not the way described in this article.
I could be wrong that Apple will do it this way, but the current hardware supports different wavelengths PPG, (as well as the Samsung Watch Galaxy 8), which might be able to use to estimate blood glucose variations. But it's pretty complex, especially to generalize.
I wouldn't be surprised if they start like blood pressure, just estimations as to how it's going up and down.
I know that because I'm literally working on this with https://trackourhearts.com, using an AI model I created to estimate blood glucose, though I'm doing it in a personalized way so I can provide more absolute estimates but it's still incredibly hard from PPG as the wavelengths available aren't the most optimized for this.
Oh yes, I've been actually looking at integrating this and other mmwave research into my startup https://trackourhearts.com
Non-intrusive technology which can work at home to monitor people' vitals is a game changer, there are so many applications to this. Research is at the beginning.
Indeed there are privacy issues with big providers doing this, but then this really opens up so many possibilities if done well.
When you own a NFT and it's in your wallet it shows that you own something. This can be used for membership for example where the owner of that NFT is automatically granted access to ... something...?
There are also smart contracts associated with NFTs... Can encode royalties and other things.
For example a creator of an NFT could encode a 5% royalty associated. This means that when that NFT is sold subsequently the original author will make 5% of the sale price.
Some people are starting to sell NFTs like a commitment to give a % of a particular revenue. It's a digital contract.
But sure. Part of owning a NFT you can often display something... Visual. Because well, we live in a visual world.. and right now it's the foundation of many NFT collections.
It's so much more than just art. The smart contract allow many more use cases in the future to prove that you own something, or are a member of something.
I think the author is completely unaware of how things work and this piece is basically a rant on cryptos. The long version starting with saying cryptos are a scam. This sets the tone for the rest of the article.
A personal opinion vs something rooted in facts.
NFTs can be created on two primary blockchains. Ethereum and Solana. The author manifests no knowledge of those.
Solana is already proof of Stake.
Ethereum is going to move to proof of Stake with Eth2.
PoS requires so much less computing power (therefore electricity) than Proof of Work. It's in fact relatively environmentally friendly.
NFTs have the potential to be a game changer. The author here sees NFTs as "Art". They're really not. Sure often NFTs are associated with Art but it's really... ownership of those pieces of Art.
But NFTs are really certificate of ownership. With smart contracts.
There is so much that can be done with NFTs. Memberships. Distributed voting. Royalties embedded in contracts so when NFTs are resold the original creator can get remunerated.
Lark.com is an AI platform to manage chronic health conditions based on a virtual coach. We're moving all of our stack to one platform with TypeScript.
I find those to be the limiting factors to speed.
I have extensive rules, I do extensive planning. Yet at implementation, the rules are not respected, errors are introduced, etc...
I spend more time fixing than writing code.
Then speed... Because of the fixes and bad code quality even with frontiers model speed makes a very big difference. I (agents) spend hours daily doing reviews and fixes. 5x speed boost would make me much more productive.
And when working super fast with agents, having only one computer is limiting. Even worktrees don't solve problems because I use things like convex, chrome use, etc... and it conflicts with each others all the time.
Still many problems to solve. It's already evolved so much in the last two years.