I did and it is amazing for someone with just mild 40s hearing issues. Took a bit of effort and updates to run the hearing test for AirPods Pro 3. Turns out I connected over Bluetooth when I should’ve paired them the Apple/iOS way.
The live listening mode is very good. I can hear my kid trying to quietly walk past 10pm :) There are a lot of features however you cannot selectively choose to lower / raise certain frequencies. I wish it had an equalizer I could use.
The ANC is fantastic, sometimes
I even forget fans around me are on. Only issue is that when I use live listen mode and everything is super clear, people still treat me like I’m using full noise cancellation.
I am curious why in your example you compare indigo to violet and purple since purple has a major red component while indigo and violet are on the complete opposite end of the visible color spectrum and are single wavelength colors.
I've been using a QNAP TBS-464 [1] for 4 years now with excellent results. I have 4x 4TB NVMe drives and get about 11TB usable after RAID. It gets slightly warm but I have it in my media cabinet with a UPS, Mikrotik router, PoE switches, and ton of other devices. Zero complaints about this setup.
The entire cabinet uses under 1kwh/day, costing me under $40/year here, compared to my previous Synology and home-made NAS which used 300-500w, costing $300+/year. Sure I paid about $1500 in total when I bought the QNAP and the NVMe drives but just the electricity savings made the expense worth it, let alone the performance, features etc.
Thanks, I’ll give it a look. I’m running a Synology right now. It only has 2 drives, so just swapping those out for SSDs would cost as much as a whole 4xNVMe setup, as I have 8TB HDDs in there now.
Augment Code (https://www.augmentcode.com/) extension in VSCode. The remote agent feature is fantastic and the local agent is worth buying credits for. I've tried almost every AI editor (Cursor, Windsurf, Roo/Cline etc.), tried CLI-based coders (Claude Code, Aider, Codex etc.), and have used them all with ton of useful MCPs and in the end, I've had the best results with Augment.
If the CLI tool does IO with the agentic CLI tool of choice over STDIO, then it's MCP by definition, with the only caveat being that it runs locally on each user's machine instead of a server. For dev-teams, CLI would work but for non-coders, web-apps or Slack-channel with LLM/MCP integration would be better.
TL;DR: Move your .git folders out of ~/Code into ~/Git/[reponame]. Use ln -s or plain text .git file[1].
I have my code folders in Dropbox on OSX but I believe my process should work for you. I work in node and have a number of monorepos with nested node_modules folders. I run my idempotent dev-files.command script [2] with or without "--nono" in any monorepo and it handles the entire git aliasing and dropbox folder ignore for node_modules process. I use --nono if I ever need to clear out all of the node_modules and do a fresh pnpm install.
Interesting, so it's as easy as putting `gitdir:{path}` in a .git file.
The downside is that git history is pretty useful, so it would suck to not sync it.
But you gave a real solution to the problem.
Edit: I remember now that one problem with iCloud was that doing something like switching Git branches or checking out commits causes a catastrophic sync cascade in the code folder itself.
Maybe Dropbox is better at dealing with that kind of thing in general. But that's pretty annoying for any syncing system to deal with, heh.
I guess the simplest solution is to just get into the habit of pushing every little project to github.
Same with Augment. Indexing makes a huge difference in a large monorepo and I can't imagine working in an editor that doesn't support an LLM with full indexing.
1. Would you sign BAA (for HIPAA) for the Pay As You Go plan? Can't find that anywhere on your site except for that Lite is HIPAA compliant (https://lite.xata.io/security).
2. FYI, couldn't request access via the BYOC form so I sent an email as per the error: There was an error, please try again or contact us at info@xata.io.
