emilecantin
Joined 12 years ago
Joined 12 years ago
Lithium batteries in contrast only need a ~10% buffer, and don't care about being topped off except for calibrating the BMS in certain variants (the only reason why LFP cars want you to charge to 100% regularly), so you don't have to over-provision as much. End-of-life is being sorted out as we speak, recycling companies are popping up as discarded batteries from cars are becoming common. Some may even pay you for them too.
It's not that niche, if you've been online a little bit you'd know this expression.
Just don't try to use that adapter on another NACS connector like the Mobile Connector, it'll get stuck and you'll have to do some magnet shenanigans to get it off (ask me how I know...)
NACS on Level 2 has the same number of pins, but speaks a different protocol than J1772, so just a normal "dumb" adapter won't work. You either need a Connector that can speak J1772, or a TeslaTap.
"Specifically modifying" as in "not even touching that part of the code in the fork"...
Publish through homebrew like a civilized person, please!
- Ask Claude to look at my current in-progress task (from Github/Jira/whatever) and repro the bug using the Chrome MCP.
- Ask it to fix it
- Review the code manually, usually it's pretty self-contained and easy to ensure it does what I want
- If I'm feeling cautious, ask it to run "manual" tests on related components (this is a huge time-saver!)
- Ask it to help me prepare the PR: This refers to instructions I put in CLAUDE.md so it gives me a branch name, commit message and PR description based on our internal processes.
- I do the commit operations, PR and stuff myself, often tweaking the messages / description.
- Clear context / start a new conversation for the next bug.
On a personal project where I'm less concerned about code quality, I'll often do the plan->implementation approach. Getting pretty in-depth about your requirements ovbiously leads to a much better plan. For fixing bugs it really helps to tell the model to check its assumptions, because that's often where it gets stuck and create new bugs while fixing others.
All in all, I think it's working for me. I'll tackle 2-3 day refactors in an afternoon. But obviously there's a learning curve and having the technical skills to know what you want will give you much better results.
Also, I wouldn't necessarily make a distinction between the full-time employees vs the part-time ones.
Employees of a company are the ones who are the most affected by the company's decisions, it's only fair that they have a say.
IMO there is a real qualitative difference between AI and crypto in terms of the durable impact it's going to have on the world. Does that mean I've bought into the AI hype? Maybe. But I think the signs are there.
What people are saying is that this mad race to throw cash at anything that has "AI" in it will eventually stop, and what will remain are the useful things.
It's more similar to a boat than a house. If your boat has a leak, you need to repair it very quickly or it ends up at the bottom of the ocean. Yet we've managed to do it relatively reliably.