When asking for change, there are the choices you know about and the ones you don't. I've gotten in the habit of describing some of the current state as well as my desired state, and using that to focus the LLM on the areas I'd like to have a stronger voice in.
Of course, I definitely appreciate when it makes choices that I don't know I need to make, and it chooses reasonable defaults.
I mean, I could say "make the visualization three columns", but there's a lot of ambiguity in that kind of thing, and the LLM is going to make a lot of choices about my intent.
Instead, "each team/quarter currently has a vertically stacked list of people assigned to that team, with two columns (staying on team, leaving team). change that to being three columns (entering team, staying on team, leaving team)."
As a bonus, it's much, much clearer to somebody reading the history later what the intent was.
1 - Not deprecate the api that allowed people to run incremental backups. They took positive action to intentionally break this. If they feel the need to break the api for ginned-up security excuses, provide a working solution for incremental backup.
2 - Fix takeout not to be entirely broken and hostile to users on 2 axes: usability and reliability. Usability: emit photos once only with a separate json specifying group memberships. Like, you know, competent engineers. Because that's how they store it internally.
2a - Either (i) fix whatever brokenness in their system regularly causes zip downloads to fail; or (ii) figure out or build a reliable alternate solution. Forcing users to wait hours to a day or two to access zips that they can't download is nothing more than a symptom of total disdain for their users while checking a compliance checkbox.
> What privacy feature are you looking for that Pixels don't supply?
Opt-in cross app tracking instead of opt-out, but if Google can get all apps on board with their new privacy sandbox thing that'll be less relevant.
More importantly, an equivalent to Apple's advanced data protection for all Google services & backups. I want full E2EE for photos, notes, backups, passwords, bookmarks, etc. I want built-in hide my email to gmail, I want to be able to turn off network access for any app I want in the permission settings. I want Google to treat Android as something completely separate from their advertising business instead of an extension of it as a source of data collection.
At scale, the larger companies end up needing to be able to make policy decisions (read: authn/authz, most of the time) across a large number of "policies" in an efficient way. Everybody starts with simple representations that can go fast but have limited expression, then moves to various forms of extensions/templating/substitution/rules/etc.
OPA and Rego use a datalog variant to bring order to that bespoke mess. Think IAM policy, but you DRY because it's a real programming language with a library full of nice-to-have built-ins.
"I commute 400 miles each way to work, every day, towing my 5000 pound boat, fully equipped outdoor kitchen trailer/classroom, my home-schooled family of 6, 6 dogs, a portable sawmill, solar-powered game freezer + ammunition, and an extra trailer because I might have to go to home depot."
I have power, yes; however, I can't even run the toaster oven and A/C, for example, at the same time. There's likely no way I could charge an EV w/o having everything trip the breaker. And there's no way to go beyond what we have unless the electric company upgrades our service.
More advanced EVSEs are capable of adjusting the power delivered based on the power available. It does require a sensor on the supply cables to determine how much power is being used, but it's technically capable without a service upgrade. Also, electric companies will frequently upgrade an old 50/100 amp service to 200 amp for low or no cost (because they figure you'll pay off the cost of doing so through more power usage). The panel side of the service upgrade will cost you, but then you'll be able use the toaster oven at the same time as the A/C.
Of course, I definitely appreciate when it makes choices that I don't know I need to make, and it chooses reasonable defaults.
I mean, I could say "make the visualization three columns", but there's a lot of ambiguity in that kind of thing, and the LLM is going to make a lot of choices about my intent.
Instead, "each team/quarter currently has a vertically stacked list of people assigned to that team, with two columns (staying on team, leaving team). change that to being three columns (entering team, staying on team, leaving team)."
As a bonus, it's much, much clearer to somebody reading the history later what the intent was.
reply