YouTube2Text

DevOps está creciendo de forma explosiva — Transcript

by Joan Amengual · 4,023 words · 634 segments · language en · Watch on YouTube

Full transcript

  1. 0:00If you've clicked on this video, it's
  2. 0:02likely because you're thinking about
  3. 0:05learning DevOps, or perhaps you already
  4. 0:07work in tech and are considering
  5. 0:09specializing in this area. And honestly
  6. 0:12, this makes a lot of sense, because
  7. 0:14right now we are in a very interesting
  8. 0:17moment for DevOps profiles. More and
  9. 0:20more companies are migrating to the
  10. 0:22cloud, automating their deployments,
  11. 0:24working with containers, adopting
  12. 0:26Kubernetes, or even improving their
  13. 0:29security processes and looking for ways
  14. 0:31to deliver software faster and with
  15. 0:34fewer errors. And for all of this,
  16. 0:36DevOps profiles are required, but here
  17. 0:39is something important: this
  18. 0:41opportunity that exists now won't be
  19. 0:43around forever, it won't stay as open
  20. 0:45as it has been in other areas of
  21. 0:47technology. At the beginning, there is
  22. 0:50always high demand and few people
  23. 0:52prepared. Then, little by little, more
  24. 0:54people get trained and the market
  25. 0:56matures, companies raise their
  26. 0:58requirements, and getting in becomes
  27. 1:00much more difficult. That is why in
  28. 1:03this video I want to explain to you why
  29. 1:05DevOps continues to be one of the most
  30. 1:08interesting specializations for the
  31. 1:10coming years. First of all, my name is
  32. 1:12Jonall, I work in the cloud computing
  33. 1:14field as a cloud engineer and I am also
  34. 1:16an instructor in cloud computing and
  35. 1:18DevOps. And now, let's see what factors
  36. 1:21are driving the demand for DevOps and
  37. 1:24what you need to learn to enter this
  38. 1:26world. I will also mention here what
  39. 1:29mistakes you should avoid if you want
  40. 1:31to make the best use of your time.
  41. 1:33Let's get to it. There is something
  42. 1:35many people don't see, and that is that
  43. 1:37the DevOps sector is experiencing a
  44. 1:38situation similar to what software
  45. 1:40development lived through a few years
  46. 1:42ago. Some time ago, if you knew how to
  47. 1:45program, you didn't need to be an
  48. 1:46expert. I'm talking about programming a
  49. 1:49little, understanding the fundamentals
  50. 1:51and being able to build simple things,
  51. 1:53meant you already had plenty of options
  52. 1:56to find work as a programmer, as a
  53. 1:58developer. Companies required
  54. 2:00programmers with these profiles. There
  55. 2:02was high demand, more demand than
  56. 2:04supply, and many companies were willing
  57. 2:07to hire profiles with little experience
  58. 2:09to train them internally. Obviously,
  59. 2:12over time the market changed, it
  60. 2:14matured, more people learned to program
  61. 2:17, training programs and bootcamps
  62. 2:18appeared everywhere, even universities
  63. 2:21expanded their programs, and suddenly
  64. 2:23knowing the basics of programming was
  65. 2:25no longer enough. Today, to get a good
  66. 2:28job as a developer, you are usually
  67. 2:30asked for, or you need to differentiate
  68. 2:32yourself much more. You need better
  69. 2:34projects, a better technical foundation
  70. 2:36, a lot of judgment, and also more
  71. 2:38capacity to solve real problems. In
  72. 2:41other words, the level has risen; the
  73. 2:42bar has been raised significantly, and
  74. 2:44this is normal and always happens. It
  75. 2:47happens in any tech profession when
  76. 2:49many people want to start getting into
  77. 2:51it. With DevOps, we are still in a
  78. 2:54phase where demand remains very high
  79. 2:56and where there aren't that many truly
  80. 2:58prepared profiles, which creates a very
  81. 3:00interesting opportunity, but one that
  82. 3:02must be understood very well. It is not
  83. 3:05enough to know four Docker commands or
  84. 3:07to make a basic pipeline by following a
  85. 3:08tutorial. The truth is that that is not
  86. 3:11enough. What companies are looking for
  87. 3:13are people who understand how systems
  88. 3:16work, how deployments are automated,
  89. 3:18how to work with the cloud, how to
  90. 3:21monitor an application, and also how to
  91. 3:23solve problems in production. And that
  92. 3:26is where the real value lies. So, we
  93. 3:29are going to talk about all of this in
  94. 3:30detail. If you look at the market, you
  95. 3:33will see that many companies have
  96. 3:34difficulty finding very well-prepared
  97. 3:36DevOps profiles. And not because there
  98. 3:39aren't people interested, because there
  99. 3:40are; there are many people interested.
  100. 3:43The problem is that DevOps combines
  101. 3:45several areas at once, and you have to
  102. 3:48understand many things, such as:
  103. 3:50development, you have to understand
  104. 3:52systems, you have to understand the
  105. 3:54cloud computing side; you also have to
  106. 3:56master the entire automation side,
  107. 3:58master the security and cybersecurity
  108. 4:01side, and we also have to know how an
  109. 4:03application works when it is already in
  110. 4:05production. So that combination is not
  111. 4:09that easy to find. That is why many
  112. 4:12DevOps job offers take longer to fill
  113. 4:15than other tech roles. Companies are
  114. 4:18looking for people capable of moving
  115. 4:20between the realms of development,
  116. 4:22operations, infrastructure, and the
  117. 4:24cloud. And that is where the real
  118. 4:26opportunity appears. If you are
  119. 4:28thinking about learning DevOps, this is
  120. 4:30a very good time to start. Not because
  121. 4:33it is easy—we have to be completely
  122. 4:35honest here—it is not a simple area.
  123. 4:37Not because you are going to become an
  124. 4:39expert in two weeks, and if someone
  125. 4:41promises you that, it’s a lie, but
  126. 4:43because there is still a real need, a
  127. 4:45very, very solid need for prepared
  128. 4:47profiles, and if you build your
  129. 4:49foundation well, you can position
  130. 4:51yourself very well for the coming years
  131. 4:53. However, the demand for DevOps does
  132. 4:56not appear by chance; it appears for a
  133. 4:58reason. There are several factors that
  134. 5:00are pushing companies in this direction
  135. 5:03. So, let's look at the most important
  136. 5:05ones, the most important factors. Let's
  137. 5:08start with factor number one. The first
  138. 5:11factor is the adoption of the cloud, of
  139. 5:13cloud computing. More and more
  140. 5:16companies are leaving traditional
  141. 5:18infrastructures behind and moving their
  142. 5:20applications, data, and systems to
  143. 5:22platforms like Amazon Web Services,
  144. 5:24Azure, and Google Cloud. But migrating
  145. 5:28to the cloud is not just pressing a
  146. 5:30button; it is much more complex than
  147. 5:32that. You have to design architectures,
  148. 5:35automate the entire deployment process
  149. 5:38to the cloud, control costs—and this
  150. 5:40is important—protect environments,
  151. 5:42monitor what is happening at all times,
  152. 5:45and do it in a very orderly way. And
  153. 5:48that is where DevOps profiles have so
  154. 5:51much, so much value. Because it is not
  155. 5:53just about knowing cloud services,
  156. 5:55which is certainly important, but it is
  157. 5:57not just about that. It is about
  158. 6:00knowing how to use them to build
  159. 6:01reliable, automated systems that are
  160. 6:03prepared to grow. The second factor is
  161. 6:07the use of containers and Kubernetes. A
  162. 6:09few years ago, Docker and Kubernetes
  163. 6:11might have seemed like advanced
  164. 6:13technologies or even something niche.
  165. 6:15Today, they are part of the day-to-day
  166. 6:17operations of many technology companies
  167. 6:18. Containers allow applications to be
  168. 6:22packaged in a more consistent way, and
  169. 6:24then Kubernetes allows us to manage
  170. 6:26those applications at scale, but it
  171. 6:28also adds a lot of complexity, and you
  172. 6:30have to understand many other things
  173. 6:32like networking, storage, deployments,
  174. 6:35scaling, monitoring, security, and
  175. 6:37troubleshooting. So companies require
  176. 6:40profiles that not only know how to
  177. 6:42launch a container and that's it, but
  178. 6:44that also understand how to operate
  179. 6:46full production container platforms.
  180. 6:49And that is where DevOps is key once
  181. 6:51again. It is a key role for this case
  182. 6:53as well. The third factor is security.
  183. 6:56Today, it no longer makes sense to
  184. 6:57build an application first and think
  185. 6:59about security at the end. That is
  186. 7:01already too late. Companies require
  187. 7:04integrating security from the start
  188. 7:06into the code, into the pipelines, also
  189. 7:08into the infrastructure, into the
  190. 7:10permissions assigned, into the Docker
  191. 7:12containers we create, and also into
  192. 7:14cloud environments. The idea is very
  193. 7:18simple: security cannot be a separate
  194. 7:20phase at the end of the process; it
  195. 7:22must be integrated into the way we
  196. 7:24develop, the way we deploy, and the way
  197. 7:26we operate software. That is why DevOps
  198. 7:29profiles who also understand security,
  199. 7:32a role also known as DevSecOps, are
  200. 7:34increasingly valued. You don't need to
  201. 7:37be a cybersecurity expert from day one,
  202. 7:39but you do need to understand best
  203. 7:42practices, permission management,
  204. 7:44secrets, and we're also talking about
  205. 7:46vulnerability scanning, networking,
  206. 7:48encryption, and monitoring, which is
  207. 7:51quite a lot, but it is currently highly
  208. 7:53valued in the market. The fourth factor
  209. 7:56is infrastructure as code, and this is
  210. 7:58relevant because for years, many
  211. 8:00companies have configured servers,
  212. 8:02networks, and services manually. You
  213. 8:05would log into a console, click around,
  214. 8:07configure resources, and hope that
  215. 8:09everything remained well-documented.
  216. 8:11But there is a problem here, and the
  217. 8:13problem is that this doesn't scale well
  218. 8:15at all. It's very easy to make mistakes
  219. 8:17, and it's difficult to replicate
  220. 8:19environments once they are configured.
  221. 8:21So, as you can see, it's complicated to
  222. 8:23know exactly what changes between one
  223. 8:25infrastructure and another when we
  224. 8:27launch them several times. That is why
  225. 8:29tools like Terraform have become so, so
  226. 8:32important. Infrastructure as code
  227. 8:35allows you to define infrastructure in
  228. 8:38files, version it, review it, automate
  229. 8:41it, and deploy it in a repeatable way.
  230. 8:44This completely changes the way we work
  231. 8:46, and companies need people who know
  232. 8:48how to do it well, who know how to do
  233. 8:50it very well. Not just copying a
  234. 8:52Terraform example or a module they see
  235. 8:55online, but knowing how to design
  236. 8:57modules, organize environments, manage
  237. 8:59variables, control states, and apply
  238. 9:01best practices. The fifth factor is
  239. 9:03artificial intelligence. And there are
  240. 9:06two important ideas here. The first is
  241. 9:09that AI is changing the way we program.
  242. 9:12As you already know, today you can use
  243. 9:15tools like ChatGPT, Claude, or Copilot.
  244. 9:18Well, there are so many, and I think
  245. 9:20that over time there will be many more.
  246. 9:21There are assistants for writing code
  247. 9:24quickly, generating scripts, answering
  248. 9:26questions, or even automating simple
  249. 9:28tasks. You know that well. That makes
  250. 9:31some basic programming tasks much
  251. 9:33easier to execute, but there is
  252. 9:34something that AI does not solve on its
  253. 9:36own, at least not today. We don't know
  254. 9:39about the future. But what is this
  255. 9:41factor? It is judgment, technical
  256. 9:44judgment. Deciding how to design an
  257. 9:46architecture, knowing which tool to use
  258. 9:48in each case, understanding why a
  259. 9:50deployment fails or doesn't fail, or
  260. 9:52even diagnosing a network problem. We
  261. 9:55can also talk about designing a robust
  262. 9:57pipeline here; an AI can help us, but
  263. 9:59it is not everything. Or even thinking
  264. 10:01about security, scalability, costs, and
  265. 10:03maintenance. We can rely on an AI. But
  266. 10:06all of that requires experience,
  267. 10:08requires context, and that is the key.
  268. 10:11The data, the data within the project's
  269. 10:13business environment, that context and
  270. 10:15vision of the entire system that today
  271. 10:17—and I say today because things
  272. 10:19change fast—but today, one no longer
  273. 10:21has. And that is precisely where the
  274. 10:24DevOps part has a lot of value, since
  275. 10:27AI can help us work faster, we know
  276. 10:29that, but you need judgment: judgment
  277. 10:31to know what to ask for, what to review
  278. 10:33, what to accept, and what not to
  279. 10:35accept. The second important idea here
  280. 10:39is that AI projects themselves also
  281. 10:41need—when a model is used, when an AI
  282. 10:44project is used, all of that also has a
  283. 10:46DevOps profile behind it, since
  284. 10:49creating a model or an AI application
  285. 10:51is only part of the job. Then it must
  286. 10:54be deployed, it must be monitorable at
  287. 10:56all times. Also, these tools scale,
  288. 10:59they must be updated, we must protect
  289. 11:01them with the entire security scope.
  290. 11:03You also have to control costs and
  291. 11:05manage all the data aspects, as well as
  292. 11:08automate processes and keep everything
  293. 11:10running, which is no small feat. That
  294. 11:13is why very diverse areas appear, such
  295. 11:15as MLOps, which applies many practices
  296. 11:17from DevOps to the world of machine
  297. 11:19learning and the world of artificial
  298. 11:21intelligence. So AI does not eliminate
  299. 11:24the need for DevOps; in fact, in many
  300. 11:27cases, it increases it, because the
  301. 11:30more applications and systems are built
  302. 11:32, the more people are needed to deploy,
  303. 11:35operate, and maintain them well. One of
  304. 11:38the reasons why DevOps is so
  305. 11:40interesting is that it is not a
  306. 11:42single-skill profile. It is not just
  307. 11:45programming, it is not just coding, it
  308. 11:47is not just managing servers, it is not
  309. 11:49just knowing cloud—which is no small
  310. 11:51thing, eh? But it is not just that, it
  311. 11:53is not just using Docker, it is not
  312. 11:55just using Kubernetes, but rather it is
  313. 11:57the combination of many things; and
  314. 11:59that is what makes this profile so
  315. 12:01valuable, since many developers know
  316. 12:03how to write code, but do not fully
  317. 12:05understand the infrastructure where
  318. 12:06that code runs. Or we even see that
  319. 12:10many system administrators know servers
  320. 12:12, networks, and operating systems, but
  321. 12:14they don't always master more modern
  322. 12:16development practices. Everything
  323. 12:19related to CI/CD, automation, and
  324. 12:21DevOps is right in the middle; let's
  325. 12:24say it's at the center, since we need
  326. 12:26to understand how an application is
  327. 12:29built, how it is deployed, how the
  328. 12:31infrastructure is configured, and also
  329. 12:34how to automate, secure, monitor, and
  330. 12:36troubleshoot it when something fails in
  331. 12:39production. That complete vision is not
  332. 12:43achieved by watching random,
  333. 12:45unorganized tutorials, and it's not
  334. 12:47gained by just watching scattered
  335. 12:48videos without any order. It is
  336. 12:52achieved by building real projects and
  337. 12:54connecting tools to one another. And
  338. 12:56when you have that vision, your
  339. 12:58professional profile changes
  340. 12:59significantly. Why? Because you can
  341. 13:02speak with developers, talk to the
  342. 13:05systems teams, communicate with the
  343. 13:07security team, hold conversations with
  344. 13:10a Solutions Architect, and help
  345. 13:12everyone work better together. And that
  346. 13:16is the true value that makes the DevOps
  347. 13:18role unique, since it’s not just
  348. 13:20about knowing tools, it’s about
  349. 13:22improving how a company delivers
  350. 13:23software. Before continuing with this
  351. 13:27video, I remind you that, as always,
  352. 13:28I’ve attached completely free
  353. 13:30resources in the video description so
  354. 13:32you can continue learning about cloud
  355. 13:34computing and DevOps. So just go to the
  356. 13:37links and download them totally for
  357. 13:39free. I hope these resources provide
  358. 13:42you with more clarity regarding the
  359. 13:44professional world. And now, let’s
  360. 13:46look at a key part of this video. What
  361. 13:49exactly should you learn? That is
  362. 13:51usually a very good question. What do
  363. 13:53we learn if we want to dedicate
  364. 13:54ourselves to this? The good news is
  365. 13:55that you don't need to learn everything
  366. 13:58. And that’s important because I
  367. 13:59mention there are many things here, and
  368. 14:01the constant doubt is, "Hey, how do I
  369. 14:02master all of this?" In fact, I’ll
  370. 14:04tell you that trying to learn it all at
  371. 14:06once is one of the most common mistakes
  372. 14:08, since DevOps has many tools, but the
  373. 14:10important thing is to follow a logical
  374. 14:12order, because if we start with
  375. 14:13Kubernetes without understanding
  376. 14:15networks, containers, or deployments,
  377. 14:16we will get very frustrated. It is
  378. 14:18complex. If we start with Terraform
  379. 14:20without understanding the cloud side,
  380. 14:21we will be copying code without really
  381. 14:23knowing what we are creating. And if we
  382. 14:25start by learning CI/CD without
  383. 14:27understanding how an application is
  384. 14:29built and deployed, we will lack a lot
  385. 14:31of context. That is why the order
  386. 14:33matters so much when we are learning.
  387. 14:35You have to have a path, a logical path
  388. 14:37. And for me, the logical path would be
  389. 14:39this. First, learn the fundamentals of
  390. 14:42Linux and networking. You don't need to
  391. 14:45be a senior system administrator, but
  392. 14:47you do need to understand how an
  393. 14:48operating system works, how to navigate
  394. 14:51the terminal, and how to manage
  395. 14:52processes, permissions, services, ports
  396. 14:55, and connections. Second, learn Git
  397. 14:57and some basic Bash scripting. That
  398. 15:00will help you a lot. Git is essential
  399. 15:02for working on any technical team. If
  400. 15:05you join a company, they use Git,
  401. 15:07whether they use GitHub, GitLab,
  402. 15:09Bitbucket, or whatever else, but Git is
  403. 15:11what you need to master. And then Bash
  404. 15:14helps us automate tasks, understand
  405. 15:17scripts, and move better in real
  406. 15:19environments. Third, please learn
  407. 15:22Docker and containers. This is where
  408. 15:25you start to understand how to package
  409. 15:27applications and run them consistently
  410. 15:30across different environments. Fourth,
  411. 15:32learn about CI/CD. This is one of the
  412. 15:36pillars of DevOps. You can start with,
  413. 15:38for example, GitHub Actions, GitLab CI,
  414. 15:41Jenkins, or similar tools. Don't focus
  415. 15:43on the tool; focus on the concept. The
  416. 15:45important thing is to understand how to
  417. 15:47automate, how to run tests, how to
  418. 15:49perform builds, and how to do
  419. 15:50deployments. Fifth, learn a cloud
  420. 15:53platform. Learn one, start with one. It
  421. 15:56could be Amazon Web Services, Azure, or
  422. 15:57Google Cloud, and you don't have to
  423. 15:59master every service. There are
  424. 16:01hundreds, but please understand
  425. 16:03networking, virtual machines, storage,
  426. 16:06databases, identity, security, and also
  427. 16:09monitoring. And sixth, learn
  428. 16:11infrastructure as code using Terraform.
  429. 16:15I think Terraform is the most
  430. 16:16consistent or at least the most popular
  431. 16:18tool we currently have in the community
  432. 16:20. Here you start to define
  433. 16:22infrastructure in an automated,
  434. 16:25reusable, and versionable way. Seventh,
  435. 16:27learn Kubernetes, but do it only once
  436. 16:30you understand containers, networking,
  437. 16:32deployments, and the cloud. Kubernetes
  438. 16:35makes much more sense when you have a
  439. 16:37good foundation, because, to be honest,
  440. 16:39it’s not easy; it’s quite complex.
  441. 16:41And eighth, learn monitoring and
  442. 16:43observability, because deploying an
  443. 16:45application is not the end. You need to
  444. 16:47know what is happening at all times.
  445. 16:49You need metrics, logs, alerts, and the
  446. 16:52ability to investigate problems. Tools
  447. 16:55like Prometheus, Grafana, or even cloud
  448. 16:58monitoring solutions are very important
  449. 17:00for this part. However, learning tools
  450. 17:04isn't enough. The key is to connect
  451. 17:07them. Don't just learn Docker on its
  452. 17:09own, Terraform on its own, Kubernetes
  453. 17:11on its own, and CI/CD on its own. That
  454. 17:13gives you scattered knowledge, but it
  455. 17:15doesn't make you a well-rounded DevOps
  456. 17:16professional. What really makes you
  457. 17:19improve is building complete processes.
  458. 17:22For example, creating a simple
  459. 17:23application. First step, then you put
  460. 17:26it into a Docker container. You can
  461. 17:28upload the code to GitHub. You can
  462. 17:30create a CI/CD pipeline. You can also
  463. 17:33deploy it to a cloud provider like
  464. 17:34Amazon Web Services. You can automate
  465. 17:37the deployment with infrastructure
  466. 17:39using Terraform. You can even run it on
  467. 17:41Kubernetes later and monitor it with
  468. 17:43Grafana and Prometheus. Also, document
  469. 17:46the entire process. Projects like this
  470. 17:49are worth way more than 10 isolated
  471. 17:51courses, because it shows you
  472. 17:53understand how the pieces connect, and
  473. 17:55that is what a company requires and
  474. 17:57looks for. Now I want to talk to you
  475. 18:01about some very common mistakes I see
  476. 18:03in people who are learning DevOps. The
  477. 18:05first mistake we are going to discuss
  478. 18:07right here is one I have mentioned
  479. 18:09quite a bit, which is taking isolated
  480. 18:11courses without connecting the tools. A
  481. 18:14Docker course here, then one on
  482. 18:16Terraform, then one on Kubernetes, then
  483. 18:18we get an AWS certification, but you
  484. 18:20never build anything complete. The
  485. 18:22problem is that in a real job, tools
  486. 18:25don't live separately; everything is
  487. 18:27connected, the project is connected,
  488. 18:29everything: the code, the
  489. 18:31infrastructure, the deployments,
  490. 18:33security, monitoring, even production
  491. 18:35errors, all of this is connected. That
  492. 18:38is why you need to practice with
  493. 18:40projects that integrate various parts,
  494. 18:42all in one. The next mistake that needs
  495. 18:44to be mentioned here is the second
  496. 18:46error, which is learning in
  497. 18:47environments that are too prepared.
  498. 18:50Sometimes you follow a tutorial where
  499. 18:52everything is already set up, you just
  500. 18:54have to copy commands, everything works
  501. 18:55, everything is fine, and it gives you
  502. 18:57the feeling that you are progressing a
  503. 18:59lot, but then you try to do it from
  504. 19:01scratch and problems appear. Maybe you
  505. 19:04don't know how to configure credentials
  506. 19:06, or you don't know why the network is
  507. 19:08failing, the networking part, you don't
  508. 19:10know how to interpret an error or a
  509. 19:12problem, or you don't know how to
  510. 19:13deploy it in your own account, and
  511. 19:15that's when you realize you hadn't
  512. 19:17really understood it at all. That is
  513. 19:19why it is so important to build from
  514. 19:21scratch, even if it is harder, because
  515. 19:23if it costs more, it is more
  516. 19:25overwhelming, it is heavier, but well,
  517. 19:27it is what really makes us progress.
  518. 19:29The more uncomfortable, the better,
  519. 19:31because that is where we truly learn.
  520. 19:33And then we are going to discuss the
  521. 19:36third mistake, which is not valuing
  522. 19:38your time. Many people try to learn
  523. 19:41DevOps using only free courses or cheap
  524. 19:43courses. And mind you, there's nothing
  525. 19:45wrong with that, eh? I think there is a
  526. 19:47lot of free material and content of
  527. 19:49very, very high value. So, on one hand,
  528. 19:51that's fine, but the problem arises
  529. 19:53when you have no structure, when there
  530. 19:56is a lack of structure, because you can
  531. 19:58spend months, or even years, jumping
  532. 20:00from one video to another without
  533. 20:02knowing what the right path is. And
  534. 20:04that time also has a cost, because for
  535. 20:06every month you delay your entry into
  536. 20:08the sector, one month, another month,
  537. 20:10you could be gaining experience,
  538. 20:12improving your salary, and growing
  539. 20:14professionally as well. And it's not
  540. 20:16about spending money just because, hey,
  541. 20:18don't get me wrong here. It's about
  542. 20:20learning in an orderly way. It's about
  543. 20:22investing well in your professional
  544. 20:24career, whether it's with a master's
  545. 20:26degree, a university degree, a bootcamp
  546. 20:29, a roadmap, mentoring, or on your own,
  547. 20:31but please follow a clear path. The
  548. 20:34fourth mistake is learning in silence.
  549. 20:36Many people study, do projects, and get
  550. 20:38certifications, but they don't show it
  551. 20:40anywhere, and that limits you, it
  552. 20:42really limits your opportunities. You
  553. 20:44don't need to become an influencer or
  554. 20:47have a personal brand, but you should
  555. 20:49make this progress visible in some way.
  556. 20:53For example, complete your LinkedIn
  557. 20:54profile well, publish the projects you
  558. 20:56are building somewhere, explain what
  559. 20:58you have learned, upload the repository
  560. 20:59to GitHub, make it public if you want,
  561. 21:01document the practices, and show the
  562. 21:03certifications if you already have them
  563. 21:04. And this will help you a lot because
  564. 21:08recruiters, companies, and other
  565. 21:10professionals can see that you are
  566. 21:13active, and in a competitive market,
  567. 21:15being visible makes a difference. The
  568. 21:18good news is that all these mistakes
  569. 21:20can be avoided, and you don't need to
  570. 21:23do it perfectly, but you do need to
  571. 21:25move forward with intention. Learn the
  572. 21:28fundamentals, follow a logical order,
  573. 21:31and build real projects. Connect the
  574. 21:34tools you use to each other, document,
  575. 21:37document everything you do, and start
  576. 21:39showing your progress publicly. If you
  577. 21:41want to do it with guidance, I've
  578. 21:43included resources in the description
  579. 21:45of this video, which is a complete
  580. 21:47training program in the field of cloud
  581. 21:49computing and DevOps. But if you want
  582. 21:52to do it on your own, use free
  583. 21:54resources, which I also think is
  584. 21:55perfect. The important thing is that
  585. 21:58you don't just stay consuming content.
  586. 21:59Apply it. DevOps is learned by building
  587. 22:02practically, assembling things,
  588. 22:04breaking things, also making mistakes,
  589. 22:06fixing those mistakes, and
  590. 22:07understanding why each part of the
  591. 22:09system works. To finish, I want to
  592. 22:12leave you with one idea. Years ago,
  593. 22:14many people entered the world of
  594. 22:16software development early and took
  595. 22:18advantage of a period of massive growth
  596. 22:20. Today, many of those people hold
  597. 22:23senior roles, lead teams, or have built
  598. 22:26very solid careers. Something similar
  599. 22:28is happening with DevOps. That doesn't
  600. 22:30mean it's an easy path, I'm not saying
  601. 22:32that, right? It doesn't mean it's a
  602. 22:34path where everyone will get a job
  603. 22:36without effort, far from it. Either you
  604. 22:38put in the effort here, or it won't
  605. 22:39matter. But it does mean there is an
  606. 22:41opportunity, an opportunity I consider
  607. 22:44real for those who train well and build
  608. 22:46a solid foundation. And my
  609. 22:47recommendation is very clear. If you
  610. 22:49are interested in the world of DevOps,
  611. 22:51start now. Don't wait until you have
  612. 22:52everything figured out. Start with
  613. 22:55Linux, learn Git. Make your first
  614. 22:58scripts using Bash. Create your own
  615. 23:01containers. Your first containers. Set
  616. 23:03up your own pipelines. Don't wait until
  617. 23:06you have everything figured out. You
  618. 23:07can start right now by beginning with
  619. 23:09Linux and learning Git. You can create
  620. 23:13your first scripts, create your first
  621. 23:16containers, set up pipelines there too,
  622. 23:18build real projects, and little by
  623. 23:20little, start connecting all the pieces
  624. 23:23. A year from now, you could be much
  625. 23:27closer to working in this field, or you
  626. 23:29could also still be thinking about
  627. 23:30whether you should start. The
  628. 23:33difference lies in what you do now. I
  629. 23:35hope this video helps you understand
  630. 23:38why DevOps is such an interesting
  631. 23:40opportunity and how you can get started
  632. 23:42with more clarity. Remember that, as
  633. 23:44always, I have included resources for
  634. 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.