This is too biased for me IMHO. I do agree with some points, documentation IS amazing, and you are very likely under-documenting things. But documentation is not cheap to create, and specially it's not cheap to maintain. I've worked in multiple companies where the problem was too much documentation, and of course everyone was afraid to update or ghasps remove any piece of old documentation in case it... - Source: Hacker News / about 1 year ago

Gcloud/command-line - Finally, for those more inclined to using the command-line, you can enable APIs with a single command in the Cloud Shell or locally on your computer if you installed the Cloud SDK (which includes the gcloud command-line tool [CLI]) and initialized its use. If this is you, issue the following command to enable all three APIs: gcloud services enable geocoding-backend.googleapis.com... - Source: dev.to / 19 days ago

While you might find that using the Google Cloud online console or Cloud Shell environment meets your occasional needs, for maximum developer efficiency you will want to install the Google Cloud CLI (gcloud) on your own system where you already have your favorite editor or IDE and git set up. - Source: dev.to / over 1 year ago

Here is the product https://cloud.google.com/shell It has a quick start guide and docs. - Source: Hacker News / over 1 year ago

If you are worried about creating other accounts etc - you can just use your gmail account with https://cloud.google.com/shell and that gives you a very small vm and a coding environment (replit or colab are way better than this though). Source: about 2 years ago

One workaround...launch a Google cloud shell from a personal google account and try the ssh toy from there. It's free. https://cloud.google.com/shell. - Source: Hacker News / over 2 years ago