DevOps está creciendo de forma explosiva — Transcript
Full transcript
- 0:00If you've clicked on this video, it's
- 0:02likely because you're thinking about
- 0:05learning DevOps, or perhaps you already
- 0:07work in tech and are considering
- 0:09specializing in this area. And honestly
- 0:12, this makes a lot of sense, because
- 0:14right now we are in a very interesting
- 0:17moment for DevOps profiles. More and
- 0:20more companies are migrating to the
- 0:22cloud, automating their deployments,
- 0:24working with containers, adopting
- 0:26Kubernetes, or even improving their
- 0:29security processes and looking for ways
- 0:31to deliver software faster and with
- 0:34fewer errors. And for all of this,
- 0:36DevOps profiles are required, but here
- 0:39is something important: this
- 0:41opportunity that exists now won't be
- 0:43around forever, it won't stay as open
- 0:45as it has been in other areas of
- 0:47technology. At the beginning, there is
- 0:50always high demand and few people
- 0:52prepared. Then, little by little, more
- 0:54people get trained and the market
- 0:56matures, companies raise their
- 0:58requirements, and getting in becomes
- 1:00much more difficult. That is why in
- 1:03this video I want to explain to you why
- 1:05DevOps continues to be one of the most
- 1:08interesting specializations for the
- 1:10coming years. First of all, my name is
- 1:12Jonall, I work in the cloud computing
- 1:14field as a cloud engineer and I am also
- 1:16an instructor in cloud computing and
- 1:18DevOps. And now, let's see what factors
- 1:21are driving the demand for DevOps and
- 1:24what you need to learn to enter this
- 1:26world. I will also mention here what
- 1:29mistakes you should avoid if you want
- 1:31to make the best use of your time.
- 1:33Let's get to it. There is something
- 1:35many people don't see, and that is that
- 1:37the DevOps sector is experiencing a
- 1:38situation similar to what software
- 1:40development lived through a few years
- 1:42ago. Some time ago, if you knew how to
- 1:45program, you didn't need to be an
- 1:46expert. I'm talking about programming a
- 1:49little, understanding the fundamentals
- 1:51and being able to build simple things,
- 1:53meant you already had plenty of options
- 1:56to find work as a programmer, as a
- 1:58developer. Companies required
- 2:00programmers with these profiles. There
- 2:02was high demand, more demand than
- 2:04supply, and many companies were willing
- 2:07to hire profiles with little experience
- 2:09to train them internally. Obviously,
- 2:12over time the market changed, it
- 2:14matured, more people learned to program
- 2:17, training programs and bootcamps
- 2:18appeared everywhere, even universities
- 2:21expanded their programs, and suddenly
- 2:23knowing the basics of programming was
- 2:25no longer enough. Today, to get a good
- 2:28job as a developer, you are usually
- 2:30asked for, or you need to differentiate
- 2:32yourself much more. You need better
- 2:34projects, a better technical foundation
- 2:36, a lot of judgment, and also more
- 2:38capacity to solve real problems. In
- 2:41other words, the level has risen; the
- 2:42bar has been raised significantly, and
- 2:44this is normal and always happens. It
- 2:47happens in any tech profession when
- 2:49many people want to start getting into
- 2:51it. With DevOps, we are still in a
- 2:54phase where demand remains very high
- 2:56and where there aren't that many truly
- 2:58prepared profiles, which creates a very
- 3:00interesting opportunity, but one that
- 3:02must be understood very well. It is not
- 3:05enough to know four Docker commands or
- 3:07to make a basic pipeline by following a
- 3:08tutorial. The truth is that that is not
- 3:11enough. What companies are looking for
- 3:13are people who understand how systems
- 3:16work, how deployments are automated,
- 3:18how to work with the cloud, how to
- 3:21monitor an application, and also how to
- 3:23solve problems in production. And that
- 3:26is where the real value lies. So, we
- 3:29are going to talk about all of this in
- 3:30detail. If you look at the market, you
- 3:33will see that many companies have
- 3:34difficulty finding very well-prepared
- 3:36DevOps profiles. And not because there
- 3:39aren't people interested, because there
- 3:40are; there are many people interested.
- 3:43The problem is that DevOps combines
- 3:45several areas at once, and you have to
- 3:48understand many things, such as:
- 3:50development, you have to understand
- 3:52systems, you have to understand the
- 3:54cloud computing side; you also have to
- 3:56master the entire automation side,
- 3:58master the security and cybersecurity
- 4:01side, and we also have to know how an
- 4:03application works when it is already in
- 4:05production. So that combination is not
- 4:09that easy to find. That is why many
- 4:12DevOps job offers take longer to fill
- 4:15than other tech roles. Companies are
- 4:18looking for people capable of moving
- 4:20between the realms of development,
- 4:22operations, infrastructure, and the
- 4:24cloud. And that is where the real
- 4:26opportunity appears. If you are
- 4:28thinking about learning DevOps, this is
- 4:30a very good time to start. Not because
- 4:33it is easy—we have to be completely
- 4:35honest here—it is not a simple area.
- 4:37Not because you are going to become an
- 4:39expert in two weeks, and if someone
- 4:41promises you that, it’s a lie, but
- 4:43because there is still a real need, a
- 4:45very, very solid need for prepared
- 4:47profiles, and if you build your
- 4:49foundation well, you can position
- 4:51yourself very well for the coming years
- 4:53. However, the demand for DevOps does
- 4:56not appear by chance; it appears for a
- 4:58reason. There are several factors that
- 5:00are pushing companies in this direction
- 5:03. So, let's look at the most important
- 5:05ones, the most important factors. Let's
- 5:08start with factor number one. The first
- 5:11factor is the adoption of the cloud, of
- 5:13cloud computing. More and more
- 5:16companies are leaving traditional
- 5:18infrastructures behind and moving their
- 5:20applications, data, and systems to
- 5:22platforms like Amazon Web Services,
- 5:24Azure, and Google Cloud. But migrating
- 5:28to the cloud is not just pressing a
- 5:30button; it is much more complex than
- 5:32that. You have to design architectures,
- 5:35automate the entire deployment process
- 5:38to the cloud, control costs—and this
- 5:40is important—protect environments,
- 5:42monitor what is happening at all times,
- 5:45and do it in a very orderly way. And
- 5:48that is where DevOps profiles have so
- 5:51much, so much value. Because it is not
- 5:53just about knowing cloud services,
- 5:55which is certainly important, but it is
- 5:57not just about that. It is about
- 6:00knowing how to use them to build
- 6:01reliable, automated systems that are
- 6:03prepared to grow. The second factor is
- 6:07the use of containers and Kubernetes. A
- 6:09few years ago, Docker and Kubernetes
- 6:11might have seemed like advanced
- 6:13technologies or even something niche.
- 6:15Today, they are part of the day-to-day
- 6:17operations of many technology companies
- 6:18. Containers allow applications to be
- 6:22packaged in a more consistent way, and
- 6:24then Kubernetes allows us to manage
- 6:26those applications at scale, but it
- 6:28also adds a lot of complexity, and you
- 6:30have to understand many other things
- 6:32like networking, storage, deployments,
- 6:35scaling, monitoring, security, and
- 6:37troubleshooting. So companies require
- 6:40profiles that not only know how to
- 6:42launch a container and that's it, but
- 6:44that also understand how to operate
- 6:46full production container platforms.
- 6:49And that is where DevOps is key once
- 6:51again. It is a key role for this case
- 6:53as well. The third factor is security.
- 6:56Today, it no longer makes sense to
- 6:57build an application first and think
- 6:59about security at the end. That is
- 7:01already too late. Companies require
- 7:04integrating security from the start
- 7:06into the code, into the pipelines, also
- 7:08into the infrastructure, into the
- 7:10permissions assigned, into the Docker
- 7:12containers we create, and also into
- 7:14cloud environments. The idea is very
- 7:18simple: security cannot be a separate
- 7:20phase at the end of the process; it
- 7:22must be integrated into the way we
- 7:24develop, the way we deploy, and the way
- 7:26we operate software. That is why DevOps
- 7:29profiles who also understand security,
- 7:32a role also known as DevSecOps, are
- 7:34increasingly valued. You don't need to
- 7:37be a cybersecurity expert from day one,
- 7:39but you do need to understand best
- 7:42practices, permission management,
- 7:44secrets, and we're also talking about
- 7:46vulnerability scanning, networking,
- 7:48encryption, and monitoring, which is
- 7:51quite a lot, but it is currently highly
- 7:53valued in the market. The fourth factor
- 7:56is infrastructure as code, and this is
- 7:58relevant because for years, many
- 8:00companies have configured servers,
- 8:02networks, and services manually. You
- 8:05would log into a console, click around,
- 8:07configure resources, and hope that
- 8:09everything remained well-documented.
- 8:11But there is a problem here, and the
- 8:13problem is that this doesn't scale well
- 8:15at all. It's very easy to make mistakes
- 8:17, and it's difficult to replicate
- 8:19environments once they are configured.
- 8:21So, as you can see, it's complicated to
- 8:23know exactly what changes between one
- 8:25infrastructure and another when we
- 8:27launch them several times. That is why
- 8:29tools like Terraform have become so, so
- 8:32important. Infrastructure as code
- 8:35allows you to define infrastructure in
- 8:38files, version it, review it, automate
- 8:41it, and deploy it in a repeatable way.
- 8:44This completely changes the way we work
- 8:46, and companies need people who know
- 8:48how to do it well, who know how to do
- 8:50it very well. Not just copying a
- 8:52Terraform example or a module they see
- 8:55online, but knowing how to design
- 8:57modules, organize environments, manage
- 8:59variables, control states, and apply
- 9:01best practices. The fifth factor is
- 9:03artificial intelligence. And there are
- 9:06two important ideas here. The first is
- 9:09that AI is changing the way we program.
- 9:12As you already know, today you can use
- 9:15tools like ChatGPT, Claude, or Copilot.
- 9:18Well, there are so many, and I think
- 9:20that over time there will be many more.
- 9:21There are assistants for writing code
- 9:24quickly, generating scripts, answering
- 9:26questions, or even automating simple
- 9:28tasks. You know that well. That makes
- 9:31some basic programming tasks much
- 9:33easier to execute, but there is
- 9:34something that AI does not solve on its
- 9:36own, at least not today. We don't know
- 9:39about the future. But what is this
- 9:41factor? It is judgment, technical
- 9:44judgment. Deciding how to design an
- 9:46architecture, knowing which tool to use
- 9:48in each case, understanding why a
- 9:50deployment fails or doesn't fail, or
- 9:52even diagnosing a network problem. We
- 9:55can also talk about designing a robust
- 9:57pipeline here; an AI can help us, but
- 9:59it is not everything. Or even thinking
- 10:01about security, scalability, costs, and
- 10:03maintenance. We can rely on an AI. But
- 10:06all of that requires experience,
- 10:08requires context, and that is the key.
- 10:11The data, the data within the project's
- 10:13business environment, that context and
- 10:15vision of the entire system that today
- 10:17—and I say today because things
- 10:19change fast—but today, one no longer
- 10:21has. And that is precisely where the
- 10:24DevOps part has a lot of value, since
- 10:27AI can help us work faster, we know
- 10:29that, but you need judgment: judgment
- 10:31to know what to ask for, what to review
- 10:33, what to accept, and what not to
- 10:35accept. The second important idea here
- 10:39is that AI projects themselves also
- 10:41need—when a model is used, when an AI
- 10:44project is used, all of that also has a
- 10:46DevOps profile behind it, since
- 10:49creating a model or an AI application
- 10:51is only part of the job. Then it must
- 10:54be deployed, it must be monitorable at
- 10:56all times. Also, these tools scale,
- 10:59they must be updated, we must protect
- 11:01them with the entire security scope.
- 11:03You also have to control costs and
- 11:05manage all the data aspects, as well as
- 11:08automate processes and keep everything
- 11:10running, which is no small feat. That
- 11:13is why very diverse areas appear, such
- 11:15as MLOps, which applies many practices
- 11:17from DevOps to the world of machine
- 11:19learning and the world of artificial
- 11:21intelligence. So AI does not eliminate
- 11:24the need for DevOps; in fact, in many
- 11:27cases, it increases it, because the
- 11:30more applications and systems are built
- 11:32, the more people are needed to deploy,
- 11:35operate, and maintain them well. One of
- 11:38the reasons why DevOps is so
- 11:40interesting is that it is not a
- 11:42single-skill profile. It is not just
- 11:45programming, it is not just coding, it
- 11:47is not just managing servers, it is not
- 11:49just knowing cloud—which is no small
- 11:51thing, eh? But it is not just that, it
- 11:53is not just using Docker, it is not
- 11:55just using Kubernetes, but rather it is
- 11:57the combination of many things; and
- 11:59that is what makes this profile so
- 12:01valuable, since many developers know
- 12:03how to write code, but do not fully
- 12:05understand the infrastructure where
- 12:06that code runs. Or we even see that
- 12:10many system administrators know servers
- 12:12, networks, and operating systems, but
- 12:14they don't always master more modern
- 12:16development practices. Everything
- 12:19related to CI/CD, automation, and
- 12:21DevOps is right in the middle; let's
- 12:24say it's at the center, since we need
- 12:26to understand how an application is
- 12:29built, how it is deployed, how the
- 12:31infrastructure is configured, and also
- 12:34how to automate, secure, monitor, and
- 12:36troubleshoot it when something fails in
- 12:39production. That complete vision is not
- 12:43achieved by watching random,
- 12:45unorganized tutorials, and it's not
- 12:47gained by just watching scattered
- 12:48videos without any order. It is
- 12:52achieved by building real projects and
- 12:54connecting tools to one another. And
- 12:56when you have that vision, your
- 12:58professional profile changes
- 12:59significantly. Why? Because you can
- 13:02speak with developers, talk to the
- 13:05systems teams, communicate with the
- 13:07security team, hold conversations with
- 13:10a Solutions Architect, and help
- 13:12everyone work better together. And that
- 13:16is the true value that makes the DevOps
- 13:18role unique, since it’s not just
- 13:20about knowing tools, it’s about
- 13:22improving how a company delivers
- 13:23software. Before continuing with this
- 13:27video, I remind you that, as always,
- 13:28I’ve attached completely free
- 13:30resources in the video description so
- 13:32you can continue learning about cloud
- 13:34computing and DevOps. So just go to the
- 13:37links and download them totally for
- 13:39free. I hope these resources provide
- 13:42you with more clarity regarding the
- 13:44professional world. And now, let’s
- 13:46look at a key part of this video. What
- 13:49exactly should you learn? That is
- 13:51usually a very good question. What do
- 13:53we learn if we want to dedicate
- 13:54ourselves to this? The good news is
- 13:55that you don't need to learn everything
- 13:58. And that’s important because I
- 13:59mention there are many things here, and
- 14:01the constant doubt is, "Hey, how do I
- 14:02master all of this?" In fact, I’ll
- 14:04tell you that trying to learn it all at
- 14:06once is one of the most common mistakes
- 14:08, since DevOps has many tools, but the
- 14:10important thing is to follow a logical
- 14:12order, because if we start with
- 14:13Kubernetes without understanding
- 14:15networks, containers, or deployments,
- 14:16we will get very frustrated. It is
- 14:18complex. If we start with Terraform
- 14:20without understanding the cloud side,
- 14:21we will be copying code without really
- 14:23knowing what we are creating. And if we
- 14:25start by learning CI/CD without
- 14:27understanding how an application is
- 14:29built and deployed, we will lack a lot
- 14:31of context. That is why the order
- 14:33matters so much when we are learning.
- 14:35You have to have a path, a logical path
- 14:37. And for me, the logical path would be
- 14:39this. First, learn the fundamentals of
- 14:42Linux and networking. You don't need to
- 14:45be a senior system administrator, but
- 14:47you do need to understand how an
- 14:48operating system works, how to navigate
- 14:51the terminal, and how to manage
- 14:52processes, permissions, services, ports
- 14:55, and connections. Second, learn Git
- 14:57and some basic Bash scripting. That
- 15:00will help you a lot. Git is essential
- 15:02for working on any technical team. If
- 15:05you join a company, they use Git,
- 15:07whether they use GitHub, GitLab,
- 15:09Bitbucket, or whatever else, but Git is
- 15:11what you need to master. And then Bash
- 15:14helps us automate tasks, understand
- 15:17scripts, and move better in real
- 15:19environments. Third, please learn
- 15:22Docker and containers. This is where
- 15:25you start to understand how to package
- 15:27applications and run them consistently
- 15:30across different environments. Fourth,
- 15:32learn about CI/CD. This is one of the
- 15:36pillars of DevOps. You can start with,
- 15:38for example, GitHub Actions, GitLab CI,
- 15:41Jenkins, or similar tools. Don't focus
- 15:43on the tool; focus on the concept. The
- 15:45important thing is to understand how to
- 15:47automate, how to run tests, how to
- 15:49perform builds, and how to do
- 15:50deployments. Fifth, learn a cloud
- 15:53platform. Learn one, start with one. It
- 15:56could be Amazon Web Services, Azure, or
- 15:57Google Cloud, and you don't have to
- 15:59master every service. There are
- 16:01hundreds, but please understand
- 16:03networking, virtual machines, storage,
- 16:06databases, identity, security, and also
- 16:09monitoring. And sixth, learn
- 16:11infrastructure as code using Terraform.
- 16:15I think Terraform is the most
- 16:16consistent or at least the most popular
- 16:18tool we currently have in the community
- 16:20. Here you start to define
- 16:22infrastructure in an automated,
- 16:25reusable, and versionable way. Seventh,
- 16:27learn Kubernetes, but do it only once
- 16:30you understand containers, networking,
- 16:32deployments, and the cloud. Kubernetes
- 16:35makes much more sense when you have a
- 16:37good foundation, because, to be honest,
- 16:39it’s not easy; it’s quite complex.
- 16:41And eighth, learn monitoring and
- 16:43observability, because deploying an
- 16:45application is not the end. You need to
- 16:47know what is happening at all times.
- 16:49You need metrics, logs, alerts, and the
- 16:52ability to investigate problems. Tools
- 16:55like Prometheus, Grafana, or even cloud
- 16:58monitoring solutions are very important
- 17:00for this part. However, learning tools
- 17:04isn't enough. The key is to connect
- 17:07them. Don't just learn Docker on its
- 17:09own, Terraform on its own, Kubernetes
- 17:11on its own, and CI/CD on its own. That
- 17:13gives you scattered knowledge, but it
- 17:15doesn't make you a well-rounded DevOps
- 17:16professional. What really makes you
- 17:19improve is building complete processes.
- 17:22For example, creating a simple
- 17:23application. First step, then you put
- 17:26it into a Docker container. You can
- 17:28upload the code to GitHub. You can
- 17:30create a CI/CD pipeline. You can also
- 17:33deploy it to a cloud provider like
- 17:34Amazon Web Services. You can automate
- 17:37the deployment with infrastructure
- 17:39using Terraform. You can even run it on
- 17:41Kubernetes later and monitor it with
- 17:43Grafana and Prometheus. Also, document
- 17:46the entire process. Projects like this
- 17:49are worth way more than 10 isolated
- 17:51courses, because it shows you
- 17:53understand how the pieces connect, and
- 17:55that is what a company requires and
- 17:57looks for. Now I want to talk to you
- 18:01about some very common mistakes I see
- 18:03in people who are learning DevOps. The
- 18:05first mistake we are going to discuss
- 18:07right here is one I have mentioned
- 18:09quite a bit, which is taking isolated
- 18:11courses without connecting the tools. A
- 18:14Docker course here, then one on
- 18:16Terraform, then one on Kubernetes, then
- 18:18we get an AWS certification, but you
- 18:20never build anything complete. The
- 18:22problem is that in a real job, tools
- 18:25don't live separately; everything is
- 18:27connected, the project is connected,
- 18:29everything: the code, the
- 18:31infrastructure, the deployments,
- 18:33security, monitoring, even production
- 18:35errors, all of this is connected. That
- 18:38is why you need to practice with
- 18:40projects that integrate various parts,
- 18:42all in one. The next mistake that needs
- 18:44to be mentioned here is the second
- 18:46error, which is learning in
- 18:47environments that are too prepared.
- 18:50Sometimes you follow a tutorial where
- 18:52everything is already set up, you just
- 18:54have to copy commands, everything works
- 18:55, everything is fine, and it gives you
- 18:57the feeling that you are progressing a
- 18:59lot, but then you try to do it from
- 19:01scratch and problems appear. Maybe you
- 19:04don't know how to configure credentials
- 19:06, or you don't know why the network is
- 19:08failing, the networking part, you don't
- 19:10know how to interpret an error or a
- 19:12problem, or you don't know how to
- 19:13deploy it in your own account, and
- 19:15that's when you realize you hadn't
- 19:17really understood it at all. That is
- 19:19why it is so important to build from
- 19:21scratch, even if it is harder, because
- 19:23if it costs more, it is more
- 19:25overwhelming, it is heavier, but well,
- 19:27it is what really makes us progress.
- 19:29The more uncomfortable, the better,
- 19:31because that is where we truly learn.
- 19:33And then we are going to discuss the
- 19:36third mistake, which is not valuing
- 19:38your time. Many people try to learn
- 19:41DevOps using only free courses or cheap
- 19:43courses. And mind you, there's nothing
- 19:45wrong with that, eh? I think there is a
- 19:47lot of free material and content of
- 19:49very, very high value. So, on one hand,
- 19:51that's fine, but the problem arises
- 19:53when you have no structure, when there
- 19:56is a lack of structure, because you can
- 19:58spend months, or even years, jumping
- 20:00from one video to another without
- 20:02knowing what the right path is. And
- 20:04that time also has a cost, because for
- 20:06every month you delay your entry into
- 20:08the sector, one month, another month,
- 20:10you could be gaining experience,
- 20:12improving your salary, and growing
- 20:14professionally as well. And it's not
- 20:16about spending money just because, hey,
- 20:18don't get me wrong here. It's about
- 20:20learning in an orderly way. It's about
- 20:22investing well in your professional
- 20:24career, whether it's with a master's
- 20:26degree, a university degree, a bootcamp
- 20:29, a roadmap, mentoring, or on your own,
- 20:31but please follow a clear path. The
- 20:34fourth mistake is learning in silence.
- 20:36Many people study, do projects, and get
- 20:38certifications, but they don't show it
- 20:40anywhere, and that limits you, it
- 20:42really limits your opportunities. You
- 20:44don't need to become an influencer or
- 20:47have a personal brand, but you should
- 20:49make this progress visible in some way.
- 20:53For example, complete your LinkedIn
- 20:54profile well, publish the projects you
- 20:56are building somewhere, explain what
- 20:58you have learned, upload the repository
- 20:59to GitHub, make it public if you want,
- 21:01document the practices, and show the
- 21:03certifications if you already have them
- 21:04. And this will help you a lot because
- 21:08recruiters, companies, and other
- 21:10professionals can see that you are
- 21:13active, and in a competitive market,
- 21:15being visible makes a difference. The
- 21:18good news is that all these mistakes
- 21:20can be avoided, and you don't need to
- 21:23do it perfectly, but you do need to
- 21:25move forward with intention. Learn the
- 21:28fundamentals, follow a logical order,
- 21:31and build real projects. Connect the
- 21:34tools you use to each other, document,
- 21:37document everything you do, and start
- 21:39showing your progress publicly. If you
- 21:41want to do it with guidance, I've
- 21:43included resources in the description
- 21:45of this video, which is a complete
- 21:47training program in the field of cloud
- 21:49computing and DevOps. But if you want
- 21:52to do it on your own, use free
- 21:54resources, which I also think is
- 21:55perfect. The important thing is that
- 21:58you don't just stay consuming content.
- 21:59Apply it. DevOps is learned by building
- 22:02practically, assembling things,
- 22:04breaking things, also making mistakes,
- 22:06fixing those mistakes, and
- 22:07understanding why each part of the
- 22:09system works. To finish, I want to
- 22:12leave you with one idea. Years ago,
- 22:14many people entered the world of
- 22:16software development early and took
- 22:18advantage of a period of massive growth
- 22:20. Today, many of those people hold
- 22:23senior roles, lead teams, or have built
- 22:26very solid careers. Something similar
- 22:28is happening with DevOps. That doesn't
- 22:30mean it's an easy path, I'm not saying
- 22:32that, right? It doesn't mean it's a
- 22:34path where everyone will get a job
- 22:36without effort, far from it. Either you
- 22:38put in the effort here, or it won't
- 22:39matter. But it does mean there is an
- 22:41opportunity, an opportunity I consider
- 22:44real for those who train well and build
- 22:46a solid foundation. And my
- 22:47recommendation is very clear. If you
- 22:49are interested in the world of DevOps,
- 22:51start now. Don't wait until you have
- 22:52everything figured out. Start with
- 22:55Linux, learn Git. Make your first
- 22:58scripts using Bash. Create your own
- 23:01containers. Your first containers. Set
- 23:03up your own pipelines. Don't wait until
- 23:06you have everything figured out. You
- 23:07can start right now by beginning with
- 23:09Linux and learning Git. You can create
- 23:13your first scripts, create your first
- 23:16containers, set up pipelines there too,
- 23:18build real projects, and little by
- 23:20little, start connecting all the pieces
- 23:23. A year from now, you could be much
- 23:27closer to working in this field, or you
- 23:29could also still be thinking about
- 23:30whether you should start. The
- 23:33difference lies in what you do now. I
- 23:35hope this video helps you understand
- 23:38why DevOps is such an interesting
- 23:40opportunity and how you can get started
- 23:42with more clarity. Remember that, as
- 23:44always, I have included resources for
- 23:46you in the description of this video.
About this transcript
This page contains the full transcript of DevOps está creciendo de forma explosiva by Joan Amengual, generated from the public captions YouTube serves with the video. The transcript has 4,023 words across 634 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.
What you can do with it
Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to choose a caption track available on the video.
Free YouTube transcript tool
YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, caption language selection, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.