I couldn't agree more. And using Plan mode was a major breakthrough for me. Speaking of Plan Mode...
I was previously using it repeatedly in sessions (and was getting great results). The most recent major release introduced this bug where it keeps referring back to the first plan you made in a session even when you're planning something else (https://github.com/anthropics/claude-code/issues/12505).
I find this bug incredibly confusing. Am I using Plan Mode in a really strange way? Because for me this is a showstopper bug–my core workflow is broken. I assume I'm using Claude Code abnormally otherwise this bug would be a bigger issue.
I’ve been working on a site/app that displays river flows. This is something that is important for fly fishing (helps determine which flies to use, where to fish, etc.)
My goal is to keep the OPEX as low as possible and not charge for it or run ads. Currently running using a combo of Vercel and GitHub Actions for $0 / month.
On the grid there are lots of different types of producers (solar, diesel, wind, nuclear, etc.). Each has its strengths/weaknesses. A big weakness of nuclear plants is that it's very expensive to turn them off. So much so that when electricity demand temporarily goes down (and with it prices), it is actually more profitable for them to continue keep the plant running but pay someone to offset their excess production.
There are people that arbitrage this--moving water up a hill is actually how many of them do it.
This stuff is really confusing. My brother trades electricity and has explained it to me numerous times and it's still a little fuzzy.
hey minimaxir, the commands should still work if you have python and/or conda installed. if you have any issues you can post here: https://github.com/yhat/rodeo/issues.
Good question. We support R and Python right now, however we're planning to extend support to other languages in the future. We've found that while PMML sounds good in theory, ta tough to use in the real world (esp. With data transformations).