1,500 karma · joined September 1, 2011
https://www.amazon.com/gp/privacycentral/dsar/preview.html
Scroll down on that page to “request all data”
I live in central nyc, been only a few times to a Costco, and had no idea they even do any shipping! I assumed that part of all those good prices is the smaller selection, large minimum quantities, and that you have to get yourself there with a car to get it in person.
* I often used it as a way to make reviews significantly easier for the reviewer. If I split something more complex into smaller units where the small change seems obviously correct, it's much more likely i'll get a faster accept than with a very large change.
* Critically, once a unit of the stack has been approved, the approval will still stay with rebases of the whole stack.
* You can keep building up a stacs and once you think you have enough for whatever you are doing, ship the whole stack.
* Suppose you have a 'hole' in the reviews and you're missing a review for a middle part of the stack. You can still merge the bottom part up to where all are reviewed.
* Let's assume you're the reviewer: smaller changes is much easier to review. Also, each part of the stack builds incrementally on the previous one. With your example, suppose you're reviewing 'api changes' part of the stack, but it has failing tests because something is broken with the lower 'db schema changes' change - but otherwise, the 'api changes' diff looks fine - you can then accept it and this part of the stack is already reviewed. The author can now whenever fix their bottom-most change (db schema change) to have tests passing, and get someone to review that (perhaps someone completely different more familiar with db), and then rebase the 'api changes' diff, and _it will not_ require review because you haven't changed anything, just updated the diff underneath it. In this way you parallelized your approvals. Right now at work, using github, I have to serialize my PRs and can't effectively get things reviewed until the previous PR is approved.
And I ask for details because I have attempted something similar but wasn’t getting the best results. I was using ‘3d scanner app’ (which was good but was sold and is not recommended now), and that created pretty decent models, but like, they were still I think based on lidar and not super precise. I also wasn’t sure how to reconcile my actual floor plan with that 3d model the right way - like if the 3d model got some error built-up, the wall which I know to be 100 inches has to be that, and not 101 or 99, since for furniture planing an inch definitely matters. So I kind of got stuck here on how to actually generate some useful and as correct dimensionally as possible 3d model, into which I can later put furniture 3d models into. Thanks for any info!
I do such more careful planning and AI handholding at work where it’s important the thing doesn’t break in prod, or doesn’t forget about some important use case.
But this was just purely for “fun” / homelab style type of vibe coding where I don’t want it to feel like work and write intricate specs and handhold the agent - point being the current SotA models still currently do need a bunch of guidance to not devolve into a code spaghetti, and it does end up feeling like ‘work’.
Recently I asked an agent for a feature where the screen will get dimmer after some time, and eventually after a day the screen will turn off and then turn back on if I tap, which should be pretty easy in esphome.
But: some past agent decided what it wanted wasn’t in esphome, so it made its own custom module in c++ for the display, spelunking in pdf datasheets; then the weeds were so deep the new agent decided to add on to that, and to read the power controller and display controller spec sheets and somehow implement my dimming feature by writing raw values to some nondescript registers.
The contraption worked until it didn’t and once every so often my esp32 would just completely hang with black screen and no connnectivity and needed a power cycle, presumably because whatever low level register writing the agent implemented eventually breaks something. I told the agent to get rid of all custom stuff and wherever possible just use default esphome yaml, now it’s been working fine. I don’t really have a point with the anecdote, just that I’m also getting tired of such scenarios like the OP.
It also has a status page! https://eruv.nyc/
> Apple has transitioned its hardware products to the AArch64 processor architecture and is phasing out support for x64. Oracle engineers will thus stop maintaining the macOS/x64 port as of JDK 27.
On my work laptop though (M3 Pro, 1TB), I’m at ~70% health. Iirc the lifetime writes are at >700TB. I do develop on it, but a lot of it is due to the various endpoint security software that’s always there logging every single possible thing but I can’t do much about it. I expect the ssd to die first in this laptop at this rate, so best I can do is ensure everything always synced/backed up from my local work laptop.
I wonder what the exact language was. If it included something like “5 star review” on that card, then the guy deserves getting kicked out from Amazon and getting his business shut down (it’s federally illegal to do that per ftc regulation). If it was just very neutral language asking for reviews, then that sucks, and hope he can get it resolved with Amazon eventually.