Turns out it was just X being down
Turns out it was just X being down
I've been throwing at it problems that Cursor with Claude3.5 wouldn't solve or where I assume Claude would fail.
You can iterate 3 times with Claude in the time o1-pro provides a response
I've been throwing at it problems that Cursor with Claude3.5 wouldn't solve or where I assume Claude would fail.
You can iterate 3 times with Claude in the time o1-pro provides a response
Does Claude also have similar issues? 19s makes this feature often unusable and will have to plan for fallbacks probably
Does Claude also have similar issues? 19s makes this feature often unusable and will have to plan for fallbacks probably
- user has one device with system clock -1d from real clock, the other is correct
- they are both used offline and at some point they sync
What strategy do you use to make sure things are represented as in the real world?
E.g. phone at -1d, pc at correct time
- user has one device with system clock -1d from real clock, the other is correct
- they are both used offline and at some point they sync
What strategy do you use to make sure things are represented as in the real world?
E.g. phone at -1d, pc at correct time
Back to normal life to save my sanity.
Back to normal life to save my sanity.
I don’t know what changed, but the app feels sooo much better than Twitter. I still need to “train” the algo, but even typing a “tweet” now is a beautiful and non-buggy experience.
I don’t know what changed, but the app feels sooo much better than Twitter. I still need to “train” the algo, but even typing a “tweet” now is a beautiful and non-buggy experience.