|
Anyone know of a good book for learning Google API's? Something beginner level and up to date?
Thanks
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
I went out to Google APIs Explorer | Google Developers[^]
Ran this code on in the JS console on that page:
let allGapi = "";
let counter= 0;
document.querySelectorAll(".name-column").forEach(x => allGapi += `${++counter}. ${x.textContent}\n`);
console.log(allGapi);
Gave me this list of all the Google APIs. 
Which ones might you be interested in? 
1. Abusive Experience Report API
2. Accelerated Mobile Pages (AMP) URL API
3. Access Context Manager API
4. Ad Exchange Buyer API II
5. Ad Experience Report API
6. Admin SDK API 1
7. Admin SDK API 1
8. Admin SDK API 1
9. AdMob API
10. AdSense Host API
11. AdSense Management API
12. AI Platform Training & Prediction API
13. Analytics Core Reporting API v3
14. Google Analytics Data API
15. Analytics Hub API
16. Analytics Management API v3
17. Analytics Metadata API v3
18. Analytics Multi-Channel Funnels Reporting API v3
19. Analytics Provisioning API v3
20. Analytics Real Time Reporting API v3
21. Analytics Reporting API
22. Analytics User Deletion API v3
23. Android Device Provisioning Partner Customer API v1
24. Android Device Provisioning Partner Reseller API v1
25. Android Management API
26. API Discovery Service
27. API Gateway API
28. API Keys API
29. Apigee Registry API
30. App Engine Admin API
31. Apps Script API
32. Artifact Registry API
33. Assured Workloads API
34. Authorized Buyers Marketplace API
35. Backup for GKE API
36. Bare Metal Solution API
37. Batch API
38. BeyondCorp API
39. BigQuery API
40. BigQuery Connection API
41. BigQuery Data Transfer API
42. Binary Authorization API
43. Blogger API v2
44. Blogger API v3
45. Books API
46. Business Profile Performance API
47. Google Calendar API
48. Campaign Manager 360 API
49. Certificate Authority API
50. Certificate Manager API
51. Google Chat API
52. Chrome Management API
53. Chrome Policy API
54. Chrome UX Report API
55. Google Civic Information API
56. Google Classroom API
57. Cloud Asset API v1
58. Cloud Asset API v1p1beta1
59. Cloud Asset API v1p5beta1
60. Cloud Asset API v1p7beta1
61. Cloud Bigtable Admin API
62. Cloud Billing API
63. Cloud Billing Budget API
64. Cloud Build API
65. Cloud Channel API
66. Cloud Composer API
67. Google Cloud Data Catalog API
68. Cloud Data Fusion API
69. Cloud Data Loss Prevention (DLP) API
70. Cloud Dataplex API
71. Cloud Dataproc API
72. Cloud Datastore Admin API v1
73. Cloud Datastore API v1
74. Cloud Datastore API v1beta1
75. Cloud Datastore API v1beta3
76. Cloud Debugger API
77. Google Cloud Deploy API
78. Cloud Deployment Manager V2 API v2
79. Cloud Deployment Manager V2 API v2beta
80. Cloud DNS API v1
81. Cloud DNS API v1beta2
82. Cloud Document AI API
83. Cloud Domains API
84. Cloud Filestore API
85. Cloud Firestore API
86. Cloud Functions API
87. Cloud Healthcare API
88. Cloud Identity API
89. Cloud Identity-Aware Proxy API
90. Cloud IoT API
91. Cloud Key Management Service (KMS) API
92. Cloud Life Sciences API
93. Cloud Logging API
94. Cloud Memorystore for Memcached API
95. Google Cloud Memorystore for Redis API
96. Cloud Monitoring API
97. Cloud Natural Language API
98. Cloud OS Login API
99. Cloud Pub/Sub API
100. Cloud Resource Manager API
101. Cloud Run Admin API
102. Cloud Runtime Configuration API
103. Cloud Scheduler API
104. Cloud Search API
105. Cloud Shell API
106. Cloud Source Repositories API
107. Cloud Spanner API
108. Cloud Speech-to-Text API v1
109. Cloud SQL Admin API v1
110. Cloud SQL Admin API v1beta4
111. Cloud Storage API
112. Cloud Storage for Firebase API
113. Google Cloud Support API
114. Cloud Talent Solution API
115. Cloud Tasks API
116. Cloud Testing API
117. Cloud Text-to-Speech API
118. Cloud Tool Results API
119. Cloud TPU API
120. Cloud Trace API v1
121. Cloud Trace API v2
122. Cloud Translation API v2
123. Cloud Translation API v3
124. Cloud Translation API v3beta1
125. Cloud Video Intelligence API
126. Cloud Vision API
127. Compute Engine API beta
128. Compute Engine API v1
129. Connectors API
130. Contact Center AI Insights API
131. Container Analysis API v1
132. Container Analysis API v1beta1
133. Content API for Shopping
134. contentwarehouse API
135. Custom Search API
136. Data Labeling API
137. Data pipelines API
138. Database Migration API
139. Dataflow API
140. Dataproc Metastore API
141. Datastream API
142. Dialogflow API v2
143. Dialogflow API v2beta1
144. Digital Asset Links API
145. Discovery Engine API
146. Display & Video 360 API
147. Google Docs API
148. Domains RDAP API
149. DoubleClick Bid Manager API v1.1
150. DoubleClick Bid Manager API v2
151. Drive Activity API
152. Drive API v2
153. Drive API v3
154. Drive Labels API
155. Enterprise License Manager API
156. Error Reporting API
157. Eventarc API
158. Fact Check Tools API
159. Firebase App Check API
160. Firebase Cloud Messaging Data API
161. Firebase Dynamic Links API
162. Firebase Hosting API
163. Firebase Management API
164. Firebase Realtime Database API
165. Firebase Rules API
166. Fitness API
167. Google Forms API
168. Game Services API
169. GKE Hub API
170. Gmail API
171. Gmail Postmaster Tools API
172. Groups Migration API
173. Groups Settings API
174. HomeGraph API
175. IAM Service Account Credentials API
176. Identity and Access Management (IAM) API
177. Identity Toolkit API
178. Indexing API
179. Google Keep API
180. Knowledge Graph Search API
181. Kubernetes Engine API
182. Managed Service for Microsoft Active Directory API
183. Manufacturer Center API
184. Migrate to Virtual Machines API
185. My Business Business Calls API
186. My Business Business Information API
187. My Business Lodging API
188. My Business Notifications API
189. My Business Place Actions API
190. My Business Q&A API
191. My Business Verifications API
192. Network Connectivity API v1
193. Network Connectivity API v1alpha1
194. Network Management API
195. Notebooks API
196. Organization Policy API
197. OS Config API
198. PageSpeed Insights API
199. People API
200. Photos Library API
201. Google Play Android Developer API
202. Google Play Custom App Publishing API
203. Google Play EMM API
204. Google Play Game Management
205. Google Play Game Services
206. Google Play Game Services Publishing API
207. Policy Analyzer API
208. Policy Simulator API
209. Policy Troubleshooter API
210. Pub/Sub Lite API
211. Real-time Bidding API
212. reCAPTCHA Enterprise API
213. Recommendations AI (Beta)
214. Recommender API
215. Resource Settings API
216. Retail API
217. Safe Browsing API
218. SAS Portal API
219. Search Ads 360 API
220. Google Search Console API
221. Secret Manager API
222. Security Token Service API
223. Service Consumer Management API
224. Service Control API
225. Service Directory API
226. Service Management API
227. Service Networking API
228. Service Usage API
229. Google Sheets API
230. Site Verification API
231. Google Slides API
232. Smart Device Management API
233. speech v2beta1
234. Storage Transfer API
235. Street View Publish API
236. Tag Manager API v1
237. Tag Manager API v2
238. Tasks API
239. Transcoder API
240. Google Vault API
241. versionhistory.googleapis.com API
242. Web Fonts Developer API
243. Web Risk API
244. Web Security Scanner API
245. Workflow Executions API v1
246. Workflow Executions API v1beta
247. Workflows API
248. Google Workspace Alert Center API
249. Google Workspace Reseller API
250. YouTube Analytics API
251. YouTube Data API v3 v3
252. YouTube Live API v3
253. YouTube Reporting API
|
|
|
|
|
If you want to make your script even more 1337, you could get automatic indexing by using console.table[^] instead.
Jeremy Falcon
|
|
|
|
|
Jeremy Falcon wrote: make your script even more 1337,
You are actually really right on that. Big miss by me. 
I will learn from this and do better next time though. 
|
|
|
|
|
|
I asked because the Google API docs are pitifully lacking. For example, look at this:
https://developers.google.com/people/v1/contacts
There's 'peopleService' in the code, yet no mention of what is is. I searched all over and finally found this, which is the best top to bottom example I've found: Accessing the People API from C# / .NET
Their docs are typical. Show a few lines that mention the topic, but not enough to make sense of it.
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Kevin Marois wrote: I asked because the Google API docs are pitifully lacking.
Yeah, I understand & agree 100%. I wasn't trying to be a smart-*ss (altho herself says it comes naturally for me) was just not sure which API you'd be interested in.
I also couldn't believe how many there are -- even for Google.
Kevin Marois wrote: Their docs are typical. Show a few lines that mention the topic, but not enough to make sense of it.
That does seem to be the Dev-Way. 
Here's my fav meme (image) that shows devs' relation to docs[^].
|
|
|
|
|
Looks about right
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
raddevus wrote: I wasn't trying to be a smart-*ss
Are you sure of that?
raddevus wrote: (altho herself says it comes naturally for me)
women are always right... you know 
 
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
You should publish that script as the Google API API.
However you might want to fix it first. I'm currently a registered user of just 5 Google APIs, and not a single one of them appears in your list. According to my "Enabled APIs" page, I'm using:
* Geocoding API
* Maps Javascript API
* Directions API
* Distance Matrix API
* Maps Embed API
My guess is that if these aren't in your list, then probably dozens - if not hundreds of others - aren't either. 
|
|
|
|
|
DerekT-P wrote: probably dozens - if not hundreds of others - aren't either.
Uh, the list is from Google's API Explorer.
I cannot update the Google API explorer.
Please submit your request to the correct office. Thanks yous.
|
|
|
|
|
LOL - I wasn't having a go at your list. Just observing that the list you generated is the tip of an iceberg. Seems even Google's own API explorer has some major shortcomings - heaven help the rest of us! 
|
|
|
|
|
Google's products and APIs change so frequently, any book would be out of date and obsolete before the author had finished writing the introduction. 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
|
Now that some time has past ...
When I say use a browser and not an app, it's not because I'm against the "owner" of the app; it's their having direct access to my device, its sensor, GPS and its data.
Recent events and what are claimed to be new "features" (involving "your" data) should make this somewhat more clear.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
In the case of my iphone, I DON'T WANT all those 157 stinking, overly specialized, half the time flakey, way too often wanting to update, apps on my phone!
|
|
|
|
|
Yup. The older and (hopefully) wiser you get, you realize apps designed to steal your time and attention are very expensive in terms of your life... even if they were free to download.
Jeremy Falcon
|
|
|
|
|
Yeah, what Craig said.
I install very few "apps", I definitely prefer to use a browser when possible. But for me it's not about the data either; it more about experience and convenience. For example, when viewing Instagram I can use "open link in a new tab" (or whatever) and have multiple tabs open to the same site -- as far as I can tell, the "app" doesn't allow that.
|
|
|
|
|
So, I saw this infoworld blog pass by, discussing how full-stack is a fallacy in and of itself.
The take away being that a good team consists of specialized people, backend and frontend.
Not people that "pretend to know it all" and "take twice as long to do anything".
This notion has ruffled my feathers the wrong way, for a couple of major reasons.
- I run a very small team, about half the size of a typical team within our company.
- Every team member is full-stack, from junior to senior.
- Every year, for the past 3 years, we are attributed at least 50% of the entire value proposition created each year.
We are not specifically gifted, we don't pretend to know it all, and we regularly make mistakes.
Even still, our delivered quality is regarded as exemplary, and by far, we innovate, iterate and improve the most, relative to the other teams.
So, what's going on here?
Why do we succeed, while teams with dedicated backends and frontends seemingly require more time and coordination to succeed, in the same company?
Ironically, for exactly the same reasons as written in that blog post.
We work together and we specialize.
The key being, we don't specialize on arbitrary lines.
We specialize in our understanding of the code.
Because all of us can do the same tasks, we are regularly confronted with our strengths and weaknesses, and the entire team can give feedback and advice to each other, on everything.
Instead of artificially limiting the scope of tasks each developers gets assigned, we can and do collaborate on everything.
Instead of creating an artificial wall where ownerships gets handed over, each developer can complete a feature or bug from start to finish.
Instead of creating little islands of specialized knowledge, where only 1 or 2 people can ask critical questions, everyone within the team can ask critical question about anything they don't fully understand.
And we don't fully understand very often, and ask a lot of dumb questions.. which is very good when it comes to quality!
The end result is that all of our solutions are easy to understand, have a single owner, and are never over-engineered.
Yes, teamwork is essential. But having a team that actually works together is a prerequisite for that!
And as a side bonus:
- we caution each other to not take on to much work at once, because we can assess each others workloads
- we actually feel like a team of equals, regardless of personal experience
- the personal gratification we get when ownership is respected, and gets critical acclaim by clients, results in an astronomically high eNPS
|
|
|
|
|
Well written Kate-X257. It sounds like you are a member of a great team. That doesn't happen for everyone.
Congratulations and best wishes!
Craig Robbins
|
|
|
|
|
Ditto. Kate said it quite well.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Thank you, I made it myself. 
|
|
|
|
|
I'm with you on this. Used to manage three small teams until recently (now I'm a single warrior), of 3, 6 and 4 developers on three different continents. You have to use effectively all available resources, which is next to impossible with specialized developers like "backend", "frontend/presentation" and "DB developers". You grab the first available developer and work with him/her on an urgent task. I would prefer a specialization based on areas of work and/or business segments for long term projects, rather than specialization in technologies.
And this goes to all fields, not only .net fill-stack developers. Imagine embedded systems programmer with absent knowledge in computer architectures (or electronics). Not cool. Not cool at all.
There is only one Vera Farmiga and Salma Hayek is her prophet!
Advertise here – minimum three posts per day are guaranteed.
|
|
|
|
|
Once there were programmers.
Then there were analysts; to guide the programmers.
Then to simplify things, they added programmer-analysts.
When the software got too "techie", the programmers split into systems and application programmers ... who needed their own supervisors, directors, and VP's.
Then the system software got too "fat", so there came database analysts, programmers, and administrators.
Then the big machines got smaller and ...
It's all just a question of scale.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
Sure, after 40 years of developing, one can really learn backend and frontend well. But full-stack is a term that's abused and overused way too much. What it's come to mean colloquially is "I do some backend and well I've seen a few bits of JavaScript. What's CSS again?"
The idea a junior or even a mid can be full stack is an outdated notion. The frontend has evolved tremendously. Even outside of that, I can't even begin to tell you how many "full-stack" developers still don't know CSS even. They all swear they do because they've seen a div. But nope. They cannot beat a real expert that dedicates their time to it.
The problem is, a lot of developers have no respect for the frontend. And in their mind they think they can do it all. Nothing could be further from the truth.
Personally, I'd never hire someone who claim to knew it all. Even after 30 years of development and being able to hold my own on the backend, I still specialize in the frontend and don't know it all on the backend. I'm good, but I won't beat someone who dedicates all their time to it. Not to mention, you take two seconds to sneeze and even the frontend changes.
This isn't the 60s... the industry has evolved.
Jeremy Falcon
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
