My local models interact with Sheets exclusively over the API with Python scripts I been curating for years

Given how well the API works, that we are discussing Googlers, my guess is that's how they dog food their services. Programmers don't get hired by Google for mouse skills.

The GUI is for spot checking results, final presentation.

If you're sitting there point-n-clicking everything into place perhaps consider you are doing it wrong.

▲

beepdyboop 3 hours ago | parent | next [-]

That sounds like an extremely narrow use case, compared to what the vast majority of Sheets users will be comfortable with

	▲	mbreese 3 hours ago \| parent \| next [-]
		At the same time, it makes some sense... the programmers for a system aren't always the best users of a system. So if you're expecting them to dogfood their own system (Google Sheets), you might find that they test/interact with the system primarily through the API and not the GUI. I have no idea if they do or not, but it's a plausible explanation...
	▲	yabutlivnWoods 3 hours ago \| parent \| prev [-]
		Use case feels like the wrong term. Do you mean restricted workflow? Googles APIs are pretty much 1:1 to the GUI And using Python makes it trivial to copy-paste out of files and other APIs with one run of Python Versus all the fiddling in browser tabs with a mouse, it actually affords an incredibly wide set of options to quickly collate and format data

▲

intended 3 hours ago | parent | prev [-]

How? This argument would make sense if sheets wasn’t targeted at a general audience.