3 ms·
“Hard to become an expert. Easy to be an expert.” I spent many years learning how to do cloud architecture. Now I can briefly look at AWS documentation for new
by Bucephalus355 8y ago
“Hard to become an expert. Easy to be an expert.”
I spent many years learning how to do cloud architecture. Now I can briefly look at AWS documentation for new services out of the corner of my eye and know all I need to for the next 6 months.
Yet the other day I opened a book on Java, which I haven’t studied since college, and literally had no idea what in the world I was reading.
- chosenbreed37 8y agoI guess that the side effect of focus
- Cthulhu_ 8y agoBack in the day (I'm not THAT old but still) I had the same with Javadoc, two chapters of the Java text book and the rest I could quickly google.
- p33p 8y agoDo you have any specific online resources you could point to in order to learn cloud architecture?
- sosodev 8y agoWhat are the benefits of knowing cloud architecture that deeply?
- saberience 8y agoI’m curious as to how/why you could have spent years learning cloud architecture, it’s not that complicated surely. My company is recently transitioning to GCP and I’m architecting big data solutions. I started doing this in November or so and well, it’s not rocket science, in fact, it’s considerably easier than building systems ten years ago was. I’d hazard a guess that you’re not learning particularly efficiently if it took you years to learn this. In my opinion, any smart engineer could learn cloud architecture in a month or two if they’re studying two/three hours per day in their own time.
- albertgoeswoof 8y agoThere are like 50+ services from AWS alone, I doubt you have deep experience across those from a few hours a week of study, let alone learning about Azure, GCP and all the other cross platform offerings out there. And that’s not even touching the custom architecture required when you hit real scale. Yes it’s easy to get going in the cloud, but becoming an expert, like anything, is hard and take time + experience.
- tekkk 8y agoYou must joking right? Sure you can learn how to graph down some services using draw.io or something, but to actually implement the architecture and have it working without hiccups is another matter entirely. There is a vast amount of different types of application architectures with different requirements that require completely different architecting compared to some "big data solutions". Maybe try architecting massive scale game servers next time? Or some other highly specialized solution with very strict performance requirements, it's not that easy. Sure you can again just graph down some vague lines and boxes with draw.io but the actual implementation with Terraform or whatnot is definitely not something you learn in a "month or two". Jezus what arrogance.
- saberience 8y agoI'm building Hadoop clusters in the cloud with massive streaming piplines using Kafka, then feeding stream processing jobs using Flink on Dataproc for driving machine learning models. We're doing this at a massive scale, bigger than most production games. So I don't know why you're talking about massive scale game servers, we are literally doing this at massive scale.
- pathseeker 8y ago>I spent many years learning how to do cloud architecture. What does that even mean? Serverless? Or just becoming an expert of AWS services?