Google Spreadsheets and Python
111–120 of 143 posts
Re: Google Spreadsheets and Python
#112Earlier quoted context omitted.
Cofounder of Airtable here, I hear you and that's on the roadmap :).
Could you spend a couple of minutes to describe the advantages of Airtable over Fieldbook or Ragic? I've been gripped by indecision regarding which tool to use, and hence use none of them.
Re: Google Spreadsheets and Python
#113Re: Google Spreadsheets and Python
#114Earlier quoted context omitted.
Why are the row limits so tight?! 1200 rows for the free tier, and only 5000 rows for the first paid tier! That's crazy low, given that Google Sheets gives you 200,000 cells, or 10,000 20-column rows, for free. EDIT: That was from 2009. The current limit is 2,000,000 cells per sheet: https://support.google.com/drive/answer/37603?hl=en
Probably because they are in business to make money? Customers whose first priority is cost usually aren't good customers.
If that saying meant anything meaningful, Walmart, Safeway, Ford, etc would not exist. I think what you meant to say was, "don't target customers not willing to pay enough for a profit margin." Much less catchy, but at least it's not bullshit.
Re: Google Spreadsheets and Python
#115Re: Google Spreadsheets and Python
#116I love Google Sheets. It is so much more powerful than 99.9% of the users appreciate. Here is how I use it at my day job as head of PM at New Relic: - Fetch deals closed and lost hourly from Salesforce - Fetch for each of our 14k+ paid accounts usage metrics using our Insights product - Pull both items into a nice color-coded business dashboard that is near realtime - Send said dashboard out as a PDF to a bunch of st…
I get all the good things Google Apps do. It's wonderful. Yet, until Google has a "contract with our users" that includes a level of customer service and human conflict resolution I would not touch them with a ten foot pole. Why? Because they could take it all away --and I do mean ALL-- overnight. Email, apps, etc. I've seen many people run into the Google ban for reasons not more complicated than not being experts a…
Re: Google Spreadsheets and Python
#117https://gspread.readthedocs.io/en/latest/ is great, but it's limited in what kinds of things it can set (formatting, notes, etc.). One other option is to create an endpoint on script.google.com which can access a much richer SpreadsheetApp API: https://developers.google.com/apps-script/reference/spreadsh... . You can POST to it using an auth token from the same service account oauth creds (though you need to add driv…
Re: Google Spreadsheets and Python
#118I love Google Sheets. It is so much more powerful than 99.9% of the users appreciate. Here is how I use it at my day job as head of PM at New Relic: - Fetch deals closed and lost hourly from Salesforce - Fetch for each of our 14k+ paid accounts usage metrics using our Insights product - Pull both items into a nice color-coded business dashboard that is near realtime - Send said dashboard out as a PDF to a bunch of st…
I get all the good things Google Apps do. It's wonderful. Yet, until Google has a "contract with our users" that includes a level of customer service and human conflict resolution I would not touch them with a ten foot pole. Why? Because they could take it all away --and I do mean ALL-- overnight. Email, apps, etc. I've seen many people run into the Google ban for reasons not more complicated than not being experts a…
In my experience Google provides amazing service for tools that you are paying for. If you're using Google Suite/Apps to access your sheets, you should be just fine.
> I want stuff I can rely on because my businesses depend on it.
Well we're talking about using Google spreadsheets as a backend for an app. It should go without saying that this wouldn't be a mission-critical use.
Re: Google Spreadsheets and Python
#119Re: Google Spreadsheets and Python
#120Huh. I bet that in the Docs SRE team at Google there's a senior SRE who's having a "I felt a great disturbance in the Force moment." Google Sheets is awesome, people at Google are smart, but they are not capable of magic. In the case of Sheets, the most reasonable sharding scheme for the database backing it would be based on some collection of spreadsheets (in the extreme case it would be just one spreadsheet, but th…
One of the good things to come out of Google Wave was a better understanding of how to scale using (eg) operational transform. Even without that, scaling a mostly read only spreadsheet backend isn't as hard as you are making out.