A similar tool, open source and portable Linux/Mac/Windows is Cyme. It works wonderfully well.
A macOS terminal command that tells you if your USB-C cable is bad
41–50 of 197 posts
Re: A macOS terminal command that tells you if your USB-C cable is bad
#42Two years ago, I wouldn’t have bothered with the rewrite, let alone creating the script in the first place. The friction was too high. Now, small utility scripts like this are almost free to build. This aligns with the hypothesis that we should see and lots lots of "personalized" or single purpose software if vibe coding works. This particular project is one example. Are there a ton more out there?
I see it differently, no need to assign learning tasks to juniors that can now be outsourced to the computer instead.
This is currently the vibe on consulting, possible ways to reduce headcount, pun intended.
Re: A macOS terminal command that tells you if your USB-C cable is bad
#43> The script parses macOS’s system_profiler SPUSBHostDataType2 command, which produces a dense, hard-to-scan raw output I couldn’t find source (the link in the article points to a GitHub repo of a user’s home directory. I hope for them it doesn’t contain secrets), but on my system, system_profiler -json produces json output. From that text, it doesn’t seem they used that.
internally uses the same root command btw. in fact this recently changed for Tahoe (as the article mentions). started out as a shell script but switched to a go binary (which is what is linked).
I hope this doesn't become a trend. Moving it to go means you need to compile it before you run it, or blindly run an uninspected binary from some random guy
It's not like the performance of this could have motivated it
Re: A macOS terminal command that tells you if your USB-C cable is bad
#44Re: A macOS terminal command that tells you if your USB-C cable is bad
#45Re: A macOS terminal command that tells you if your USB-C cable is bad
#46Please update the title to mention that this is MacOS only; I got excited to try this out, but I only have laptops running Linux and Windows.
what do you mean, all developers only use macs!
(/s)
Re: A macOS terminal command that tells you if your USB-C cable is bad
#47[deleted]
Re: A macOS terminal command that tells you if your USB-C cable is bad
#48Side question : what font are you using in your screenshots? I find it really nice looking
Re: A macOS terminal command that tells you if your USB-C cable is bad
#49It's more complicated than "this cable is good/bad". I had a suspicion about one of my cables for months, but just last week I confirmed it with a device that shows the volts/amps/watts/total kwh passing through it: I have a USB-C cable with orientation. Plugged in one way it transfers about 5x more power than the other way, and in the lower orientation it's low enough for the earbud case I use it with to not charge.
Could you elaborate on "orientation"?
Let's say for C-to-C, are you talking about swapping the head/tail? Or simply connecting at a different angle (180 degrees)?
Re: A macOS terminal command that tells you if your USB-C cable is bad
#50Two years ago, I wouldn’t have bothered with the rewrite, let alone creating the script in the first place. The friction was too high. Now, small utility scripts like this are almost free to build. This aligns with the hypothesis that we should see and lots lots of "personalized" or single purpose software if vibe coding works. This particular project is one example. Are there a ton more out there?
+1 here, with the latest Chrome v3 manifest shenanigans, the Pushbullet extension stopped working and the devs said they have no interest in pursuing that (understandable).
I always wanted a dedicated binary anyway, so 1 hour later I got: https://github.com/emilburzo/pushbulleter (10 minutes vibe coding with Claude, 50 minutes reviewing code/small changes, adding CI and so on). And that's just one where I put in the effort of making it open source, as others might benefit, nevermind the many small scripts/tools that I needed just for myself.
So I share the author's sentiments, before I would have considered the "startup cost" too high in an ever busy day to even attempt it. Now after 80% of what I wanted was done for me, the fine tuning didn't feel like much effort.