At least they’re forward about it - I’ve lost count of how many bike accessories claimed to be USB C, but they only charge when connected to their specialized cable that converts from USB A to C.
Double-sided USB-C connections require a handshake before sending voltage. USB-A ports can have the 5v line active at all times. Cheap USB C gadgets often don't make the handshake, they just use it as a 5V input, necessitating an A to C cable.
If you add 5.1kΩ pulldown resistors on the CC lines for USB-C, you can get the standard 5V without a handshake although current may be limited by some chargers without negotiation.
I think you're overstating this. The "handshake" is purely 2 simple resistors correctly installed. The problem is a lot of folks do it wrong for various reasons, most likely never testing with anything more than type a to type c cables.
One of the many deficiencies of usb-c (who knows what power your cable supports, charger supports, if you accessory will charge, of it will connect at all)
There is no handshake, all that's needed are two 5.1 kΩ pulldown resistors. By omitting them the manufacturer saved all of about 0.1c and made their device incompatible with compliant usb-c chargers.
To clarify, does this mean that Anthropic employees don't understand Claude Code's code since it's level 7? I've got to believe they have staff capable of understanding the output and they would spend at least some time reviewing code for a product like this?
This is why we need some kind of professional accountability for software engineers. This behavior is willful malpractice, and it only flies because they know they'll never face consequences when it goes wrong. Let's change that.
I'm not sure I believe them though, at face value anyway. Or at least, I would suspect the entire spectrum of levels 0-9 are constantly at play at Anthropic (or any sizeable company). Fully disavowing the code as a matter of policy seems needlessly reckless.
(Thanks for visidata btw, awesome tool that helped me with a side project not long ago.)
A friend who does game design gave me a good tip -- start with the core game loop first and only focus on that with low poly / representative shapes for game elements that you can refine in the future. Not until the core game loop is fun does it make sense to spend a minute of time on any other aspect of the game.
reply