Something could be done at least in documentation in Amazon DevOps Guru. It could be better in that area. When I started maybe 20 years back, technologies and DevOps itself were new, and there were fewer services. Nowadays, if I remember correctly, in 2007-ish, AWS had only five services. Now there are maybe more than 300 or 400 services on AWS. One thing that could be challenging is based on the requirement, which tool to exactly choose if you are a newbie or a beginner. That could definitely be a challenging thing. Another thing is the documentation part. With more complex aspects nowadays, it is challenging to actually develop the architecture and document everything as things are changing.
Something could be done at least in documentation in Amazon DevOps Guru. It could be better in that area. When I started maybe 20 years back, technologies and DevOps itself were new, and there were fewer services. Nowadays, if I remember correctly, in 2007-ish, AWS had only five services. Now there are maybe more than 300 or 400 services on AWS. One thing that could be challenging is based on the requirement, which tool to exactly choose if you are a newbie or a beginner. That could definitely be a challenging thing. Another thing is the documentation part. With more complex aspects nowadays, it is challenging to actually develop the architecture and document everything as things are changing.