GCP's documentation has an aesthetic quality but is lacking practicality. Take for example a fundamental usecase: working with a blob storage service through a

GCP's documentation has an aesthetic quality but is lacking practicality. Take for example a fundamental usecase: working with a blob storage service through a client library. Googling "gcp cloud storage java example" and "s3 java example" returns these as top results: https://cloud.google.com/java/getting-started/using-cloud-storage https://cloud.google.com/java/getting-started/using-cloud-st... https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/examples-s3.html https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/... The AWS doc is clear and gives me exactly what I want: Java code snippets for doing common actions with buckets. The GCP doc is about a sample bookshelf application? And it starts off by creating a bucket through a terminal command followed by a couple of massive code snippets specific to the example app? Changing the search terms a bit reveals this: https://cloud.google.com/storage/docs/creating-buckets#storage-create-bucket-java https://cloud.google.com/storage/docs/creating-buckets#stora... That's a bit better, but seeing options for the various arguments requires me to copy and paste a non-clickable link from the code snippet, which brings me to another attractive but minimally helpful page. Another example: renaming a bucket. I find the link easily enough.. https://cloud.google.com/storage/docs/moving-buckets#storage-create-bucket-code_samples https://cloud.google.com/storage/docs/moving-buckets#storage... But only the first code snippet has code samples of any kind. The remaining steps only have instructions for the console and terminal (and the JSON API if you want to curl against that..) To me, GCP's documentation just doesn't surface information in a way that's conducive to getting work done quickly.