Dasar-Dasar Google Cloud: Memulai App Engine Ulasan

Cedric L. · Diulas lebih dari 5 tahun lalu

Neetendra T. · Diulas lebih dari 5 tahun lalu

Michael S. · Diulas lebih dari 5 tahun lalu

Ernie John T. · Diulas lebih dari 5 tahun lalu

Dal P. · Diulas lebih dari 5 tahun lalu

Shivam K. · Diulas lebih dari 5 tahun lalu

good

Lingala D. · Diulas lebih dari 5 tahun lalu

Abhijeet K. · Diulas lebih dari 5 tahun lalu

Damir G. · Diulas lebih dari 5 tahun lalu

Nacho L. · Diulas lebih dari 5 tahun lalu

Oliver B. · Diulas lebih dari 5 tahun lalu

Andrei T. · Diulas lebih dari 5 tahun lalu

Tadeusz W. · Diulas lebih dari 5 tahun lalu

D.Isuru P. · Diulas lebih dari 5 tahun lalu

Suraj K. · Diulas lebih dari 5 tahun lalu

isaac S. · Diulas lebih dari 5 tahun lalu

Ibrahim R. · Diulas lebih dari 5 tahun lalu

Nageshwar M. · Diulas lebih dari 5 tahun lalu

Anissa H. · Diulas lebih dari 5 tahun lalu

This isn't really a complaint but I felt the time was barely enough to complete the lab (had a minute remaining on completion), if something wouldn't have worked it's possible the time would've ran out. For instance, my git update failed the first time, which didn't really take too much time but if one or two other things would've failed... maybe a few more minutes wouldn't be a bad idea. Now complaints: 1. When the instructions told to check the App Engine Dashboard and to "notice there are no resources", I went to the dashboard and instead of an empty list of some sort, a tutorial was there waiting for me, so I couldn't "notice there are no resources". This was entirely confusing. Although, I later found out that if you DO have an app running, the tutorial is no longer there and it shows your app information properly. 2. In the final Task, when you're supposed to disable the application by typing in your App ID, I got confused because I had no idea what my App ID was supposed to be. Turns out, it was this obnoxious string of a million characters (of course everything is a long string because these are training resources but that makes it even more important to help the user find these). Thankfully, it was on the popup but it should definitely be mentioned when you're creating the app, what your App ID is and where it can be found. It is printed on the console upon creation so it would be nice if the instructions referenced this in some way. 3. Many of the steps were confusing and lacked information. Some of them say to do 2-3 things but only give you a command for the last one. For example, before doing the pip command to install the packages, the instructions said to "navigate to the project folder" but only gave you the pip command. Usually, in these labs, when you're asked to navigate to a folder, you are given a straight up cd command or at least some sort of indication of where the folder is. Not this time. So I deduced that the "hello_world" folder was the project folder. Everything went fine, but later I was told to navigate back to the hello_world folder (this time I was given a cd command) so apparently it wasn't the project folder (or maybe it was?). All this takes time in what is already a tightly timed lab. What makes this even more of a problem, is that it's possible to get your account blocked if you do these labs incorrectly (e.g. deploy something in the wrong place or start a wrong number of things). So confusing or inconsistent instructions are Otherwise, the lab was okay. However, considering how short and simple it is, there were far too many things wrong to give this anything more than 2/5

Reino N. · Diulas lebih dari 5 tahun lalu

Evgeniia A. · Diulas lebih dari 5 tahun lalu

Alicja S. · Diulas lebih dari 5 tahun lalu

Eduardas J. · Diulas lebih dari 5 tahun lalu

Adriel D. · Diulas lebih dari 5 tahun lalu

Maciej D. · Diulas lebih dari 5 tahun lalu