They make a "universal charger" for this express purpose. It even has the adapter embedded in the holster, so you can either grab just the NACS connector, or the connector + J1772 adapter in one smooth motion.
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.
I had one, broke 2 screens before I gave up wearing it... It's really not meant to be work in daily life, which is sad because an e-paper screen makes a lot of sense on a watch.
Mine had been upgraded from 4GB of RAM to 8GB, and I replaced the HDD with an SSD, and replaced the DVD drive with the original HDD for more storage. Was a nice machine for uni, I really loved it.
A loop I've found that works pretty well for bugs is this:
- 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.
I switched to Zed from a tmux/nvim setup. I think Zed is the first editor I've tried that has a good enough Vim mode for me to switch and keep my built-up muscle memory.
It would obviously need to be accompanied with rigorous enforcement of employee classification. I know there would be a bunch of possible ways to game this, so there are a lot of other rules we'd need to add but I didn't want to make my comment too long.
Also, I wouldn't necessarily make a distinction between the full-time employees vs the part-time ones.
I think there should perhaps be a law that any corporation automatically has a new class of un-tradeable VOTING shares, worth 50% of the overall vote, held by the employees. Everybody with an employment contract with this company is entitled to 1 vote, no more, no less; whether they're the janitor or the CEO.
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.
Yeah, I saw "AI winter" mentioned elsewhere in the thread...
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.
Both can be true at the same time. Similar to the early days of the Internet, the dot-com bubble eventually popped, but the Internet (and dot-coms, for that matter) didn't go away.
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.
> If I can't get the materials to repair my building in a hurry, I go outside and I wait. Or I stay inside and I wait. And if I can't do that for my Venusian balloon city, I slowly sink into a zone that melts lead and bakes me alive. And if I get the materials after it has stared sinking, repairing it won't reinflate the balloon and have it rise again, because some significant fraction of the air has leaked out.
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.
My recent experience with getting an app deployed from Gitlab to a kubernetes cluster on DigitalOcean was exactly like this. There were like 3 or 4 different third-party technologies I was expected to set up with absolutely no explanation of what problem they're solving, and there was a bunch of steps where I had to supply names or paths as command-line arguments with no guidance on what these values should contain (is it arbitrary? Does it need to match something else?)
Mind you, I have relatively good Docker experience (wrote Dockerfiles, have a pretty extensive Docker-Compose - based home server with ~15 services) so I'm not new to containers at all. But man, the documentation for all these tools was worse than useless.
One area where it really shines for me is personal projects. You know, the type of projects you might get to spend a couple hours on once the kids are in bed... Spending that couple hours guiding Claude do do what I want is way quicker than doing it all myself. Especially since I do have the skills to do it all myself, just not the time. It's been particularly effective around UI stuff since I've selected a popular UI library (MUI) but I don't use it in my day job; I had to keep looking up documentation but Claude just bangs it out very easily.
One thing where it hasn't shone is configuring my production deployment. I had set this project up with a docker-compose, but my selected CI/CD (Gitlab) and my selected hosting provider (DigitalOcean) seemed to steer me more towards Kubernetes, which I don't know anything about. Gitlab's documentation wanted me to setup Flux (?) and at some point referred to a Helm chart (?)... All words I've heard but their documentation is useless to newcomers ("manage containers in production!": yes, that's obviously what I'm trying to do... "Getting started: run this obscure command with 5 arguments": wth is this path I need to provide? what's this parameter? etc.) I honestly can't believe how complex the recommended setup is, to ultimately run 2 containers that I already have defined in ~20 lines of docker-compose...
Claude got me through it. Took it about 5-6 hours of trying stuff, build failing, trying again. And even then, it still doesn't deploy when I push. It builds, pushes the new container images, and spins up a new pod... which it then immediately kills because my older one is still running and I only want one pod running... Oh well, I'll just keep killing the old pod until I have some more energy to throw at it to try and fix it.
TL;DR: it's much better at some things than others.
True, but it's harder to reject changes in one file, make a quick fix, etc. I like to keep control over my git repo as it's a very useful tool for supervising the AI.
I tend to have auto-accept on for edits, and once Claude is done with a task I'll just use git to review and stage the changes, sometimes commit them when it's a logical spot for it.
I wouldn't want to have Claude auto-commit everything it does (because I sometimes revert its changes), nor would I want to YOLO it without any git repo... This seems like a nice tool, but for someone who has a very different workflow.
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.