Sometimes I feel that I am not suited to group discussions. Everyone puts forward their own one-sided views, which are unoriginal and cannot stand up to close scrutiny.
The web3/crypto space taught me a harsh lesson as someone who adheres to a long-term investment philosophy. Project teams might simply choose to abandon the project; they won't stick with you and stick to long-term principles.
Furthermore, there's little responsibility for failed projects in the crypto space; the project team can simply move on to the next one.
This is what I've learned over the past few years.
My personal AI programming experience😂:
1. Cursor programming is like manual driving.
2. Claude Code local programming is like semi-autonomous driving.
3. Codex remote control + automated tasks are like autonomous driving.
I have tried using ios app to control mac to code.
It would be better if we can also use codex app in one mac to control another mac running codex app.
I feel more tired with ai coding:
1. More things want to do
2. Do much more brain context switch than before
3. No deep think like before, just arrange things
One small observation, for Claude Code, debugging a bitcoin node using a remote server seems smoother than debugging locally because it doesn't require frequent permission requests.
I am pleased to announce ✨mine✨, a complete, no-frills IDE for Coalton and Common Lisp. It's a brand new IDE that has the essential interactive programming workflow all Lispers talk about, built-in. It is the easiest way to get started with Coalton/CL for Win/Mac/Linux. 👇
I am currently experimenting with using Opus/GPT to assist in designing and optimizing protocols (to see if it is feasible). Compared to using these tools for writing code, the level of uncertainty is significantly higher—primarily because it is impossible to empirically verify whether the protocol functions correctly—and consequently, the volume of manual review required is much greater.