Putting the pieces together

As of today, I am a Cloud Engineer working in Oracle. My main functions include helping customers design their cloud solutions. My main area of focus is cybersecurity, which involves mainly identity and access management, cloud security, governance and compliance. Since I joined the team, what I have been told is to master this field so that in case my workmates need help regarding the matter I will be able to help them. But that's all, we can say that some people dedicate themselves to master one field or subject (currently in my case, cloud security). Why am I writing about this? Isn't it supposed to be a blog about the article written by Pete Goodliffe about software architecture? Well, yes and no.

I would like to talk about architecture from my point of view. Having interacted with cloud architects, there are many things that amazed me about how they work. One of the many skills they have is that they are really good at putting the pieces together. They must have a really good understanding of how components interact with each other and how they can contribute in the pursuit of the organization's goals. They may not have the expertise of a specific component, product or software but understand what to ask to the ones who have the answers. Almost every time a customer is having interest in cloud transition, the first contact (besides the sales rep) is the cloud architect whose objective is to understand the customer's needs and requirements in order to design a complete solution.

Almost all of our courses throughout our major of computer science in Tecnológico de Monterrey are focused on specialization rather than seeing the whole picture. Maybe that is why the school has decided update their programs (for the good or the bad) in order to have multidisciplinary courses. From another course (ethics), according to the philosopher Edgar Mori, education is lacking several things, one of them is having the people to specialize in certain fields preventing an integral formation.I hope this course will be more about design and architecture of software rather than coding. 

Morin, E. (1999) Los Siete saberes necesarios para la educación del futuro. Santillana


Comentarios

Publicar un comentario

Entradas más populares de este blog

Microservices

Monolith applications is now a thing from the past. In order to build scalable and efficient applications, a new architectural style has come to try and solve the problems of deploying again and again the entire  code when a single change or modifications has been made to a single part of the project. I found logically correct to segment the application into units called services (each one with a specific purpose) and handle it like an independent application.  Web development and applications are growing, and considering that this will keep trending, HTTP is used as a communication method between services. How it is properly done? Through this incredible and standardized interfaces called APIs (Application Programming Interfaces). Since I learned Javascript,  when defining the routes I was already thinking in the required methods (GET, POST; PUT, DELETE, etc) and the scope for each one of them. Therefore, knowing about HTTP and APis will be (if it is not now) a necessary skill.  I was
Leer más

Is Design Dead

Thsi week's activity... software design... it is said that the more senior you become, the higher level you go through projects and, well... maybe there is a bit of reason of software builders losing respect to the ones designing. But to be able to design such software systems, you need to have experience and had the whole picture of how systems work. You do not need to be specialized in a product or service, you just need to know how they work and interact with other components (perhaps like a black box). Where I work, I interact daily with all types of people. There are software engineers, cloud engineers, architects, consultants and project managers. With my two years meeting different professionals and being in different areas, I would like to tell more about the place I work.  Currently, I am a Cloud Solution Engineer. The job is a mixture of both hard and soft skills, but most of the time I am interacting with customers designing solutions, troubleshooting issues, presenting
Leer más

Who needs an architect?

This week's article was a little short, but there are many ideas that can I can come up with. Basically, what the article was trying to do was to show the importance of architects, especially software architects. We have come a long way on our major of comptuer science, and it is time to start thinking big. Most of the projects we have worked in school are small projects which almost all of them consisted on a set of approximately seven classes, a database and a web server. Maybe for these projects you do not need a special person to check or validate the whole system.  But as the world progresses, organizations require bigger and more complex information systems and applications. Many of them involve the use of applications interacting with each other. Now, with that being said a special role or person is needed for a whole system to work. This includes knowing how a system interacts with a database, an application programming interface (APIs), with other classes, operating system
Leer más