I just use the tea CLI. There is pretty good compatibility between tea and forgejo. The only place I’ve found it to be incomplete is forgejo’s actions api was missing some endpoints.
The bike analogy is pretty funny. Electric bikes are great at increasing accessibility, but have two major downsides I've seen: they damage trails faster than regular bikes and enable untrained riders to get hurt and…
I feel like I’m missing something between what is explained here and claims that agent driven coding massively speeds up output. Certain parts of this like Day 2s decomposition into steps and Day 3s context packet seem…
It would be interesting to also report Alpha and Beta for the portfolios. Absolute returns are great but don’t tell the whole story. Perhaps also average holding duration.
I get conflicted feelings about dismissing detailed prose as doing nothing more than wrapping weak ideas in flowery disguise. Certainly, it’s very possible to write pretentiously. And more than that I’d argue it is…
[dead]
I just use the tea CLI. There is pretty good compatibility between tea and forgejo. The only place I’ve found it to be incomplete is forgejo’s actions api was missing some endpoints.
The bike analogy is pretty funny. Electric bikes are great at increasing accessibility, but have two major downsides I've seen: they damage trails faster than regular bikes and enable untrained riders to get hurt and…
I feel like I’m missing something between what is explained here and claims that agent driven coding massively speeds up output. Certain parts of this like Day 2s decomposition into steps and Day 3s context packet seem…
It would be interesting to also report Alpha and Beta for the portfolios. Absolute returns are great but don’t tell the whole story. Perhaps also average holding duration.
I get conflicted feelings about dismissing detailed prose as doing nothing more than wrapping weak ideas in flowery disguise. Certainly, it’s very possible to write pretentiously. And more than that I’d argue it is…
[dead]