I hope sharing my experience and tips on this topic was useful for you 😊 How do you keep up with technology developments and what are some of your tips on that? 🙋🏽♂️ ▬▬▬▬▬▬ ⬇ Resources to learn DevOps ⬇ ▬▬▬▬▬▬ 💙 Subscribe to me on TH-cam :) 👉🏼 bit.ly/2z5rvTV 💛 High-Quality and Hands-On Courses 👉🏼 bit.ly/3q7QTTO 💚 Become a DevOps Engineer - full educational program 👉🏼 bit.ly/3OA3Orz Sign up to get notified about new upcoming courses ► www.techworld-with-nana.com/course-roadmap ▬▬▬▬▬▬ T I M E S T A M P S ⏰ ▬▬▬▬▬▬ 0:00 - Intro - Why it's overwhelming 01:24 - DevOps ecosystem - Separate Concepts and Tools 03:32 - How to actually learn? 04:01 - Use Cases - What problems the DevOps tool solves? 05:31 - How does the tool work? 06:10 - Hands-On Practice with a realistic use case 09:20 - Patience while learning 10:20 - Embrace lifelong learning 10:58 - How to stay up to date?
I enjoy most of your videos relevant to "on ground" operation. DevOps indeed a challenge to all levels not just happily setup alone as well troubleshoot and bug fixes on every single software..Gosh what happen it breaks ..oops !!.. Devops aka middleware i.e understand infra and application to gel all in one. awesome sharing ..
As always a fantastic point of view, totally agree...especially in "how to learn", because it focus the time and learning process in what really matter, that is solve a problem.
Nana this is not only for DevOps, what you just synthesized in these 12 minutes can be applied in all the IT branches from operations to code development and research, a very good video and I totally agree with these techniques .
I’m a junior devops, I often watch your video, they are sooooooo helpful for me at work. I love the way you explain technology from big picture to practical demos with awesome visualization through the entire process. That’s really human mind friendly. Also, your peaceful tone can always comfort my busy mind in the beginning of learning process. Thank you soooo much! Please keep up with this great work! 👍👍👍
1. Concepts and processes before tools: challenges, steps, pros, cons, why, what is the purposes 2. Learn tools, use cases fit tools in the big picture, what problem does it solves? 3. How does the tool work? 4. how is it compared to other tools? 5. hands on-practice, simple case 6. Expand the use case 7. References - documentation, tutorials 8. Patience - good foundation, makes click 9. Continous learning -community, blogs...keep update
working for a company/manager that doesn't expect you to be 12 people in one with 20 years of experience with react hooks, data warehousing, proficiency in 30 middle tier languages, knowledge of gitlab, github actions, jenkins, jenkin x, ansible, all the linux distros, all the bsds, windows, embedded programming, VR device manufacturing, materials science, native German, Spanish, Chinese, Japanese, Korean, Russian and other human natural languages (they always put "etc" in the job description), and also can clean toilets all for 9$/hr is another thing.
I like the emphasis on figuring out why you should learn a given tool and understanding what problem it solves. It’s easy to try to learn a tool because you know it’s what people use, but understanding why and the underlying concepts first helps frame it in your mind when learning. I spend a lot of time learning new web dev frameworks and npm libraries. And when I jump right in without really taking time before hand what problems it’s mainly addressing and the goals behind it, it’s a much worse learning experience all around or really appreciate the tool for what it solves.
Senior developers find it hard to learn new things cause they fail to adapt to change due to feelings of cognitive dissonance . The greatest barrier to this change is the belief that ‘they are smart’. While learning new stuff you experience feeling dumb. Once you learn to identify this stage of cognitive dissonance - and learn to push through it you end up being a life long student. Great video. Keep up the good wirk
As someone who transitioned from the nuclear industry (where technology hardly budged over the course of a decade), and literally fell into a MLOps role (where shiny new features and tools are released every minute), I must say that this video made me feel way better. Thanks so much!
I just started my journey on the DevOps career path. I had no idea how many tools were available, and used together. I will keep this advice in mind as I move through the process of learning all of them. Thanks for sharing!
Nana, I am a Sr. Business Analyst but I love watching your videos to help me understand complex subjects. They are just the right length for me. You should teach at a college or for those that are trying to learn these concepts.
This video could not have been recommended to me at a better time! I just made a career switch to DevOps and I feel overwhelmed with all the information out there. Thanks Nana for the advice - will definitely try them!
7c's of DevOps Continuous (Planning, Development, Integration, Deployment, Testing, Delivery & Monitoring, and Feedback), then 8th C "Continuous Learning" added
It's really rare to be person having much of knowledge and being excellent at teaching. Thank you very much Nana, I was soaking every word you said in the video.
The other point I want to add to the patience category is a lack of progress, especially when you are new to a tool or concept. This frustrates many people and makes them give up on learning stuff when things simply don't work. Understand that every single developer you admire or look up to was exactly in that stage not too long ago. Breathe, go for a quick walk, reset and start again.
Thank you Nana for wonderful video. You really broken entire DevOps into simpler steps and make me understand the real picture. Really, I was overwhelmed when I was first learning the GIt Lab, Liquibase, and Docker and trying to learn entire tools and features through their company documentation. Which made me go crazy and not sure how to follow and keep up with project timelines. You are genius and thank you once again for helping folks like me.
I appreciate it, Nana; this is the best video I've ever watched. I currently work as a cloud engineer using an outdated approach of distributing software, but I'm feeling strongly motivated to switch to a career as a DevOps engineer. Actually, I'm getting ready for that. Your channel is quite useful in that regard. Thank you for making such wonderful contents.
I think good paitence also stems from keeping good motivation to what you're learning. If you hit similar concepts you've already learnt, that can become boring, and demotivating, even though those concepts are foundational to what you're learning.
This was super helpful. Thank you. As a junior full stack engineer I’ve found it hard juggling both learning and understanding technologies that I need to know for my job. I’d never heard of terraform before and didn’t know what docker did fully or how it all integrated in aws etc so to be hit all at once was overwhelming. One thing Ive found that helped me was creating diagrams as I’m quite a visual learner. Also then explaining the tech I’m trying to learn to my husband (who is now thoroughly bored I’m sure, but endures it for me) to help solidify my understanding.
Great to hear! It will get easier, once you have a good foundation. And the good thing is that you will get rewarded for your efforts as it's a very demanded job nowadays :)
@@TechWorldwithNana Rightly said Nana, its been chaotic learning so far because of the timelines. I will re-structure my learning process. This video surely helped!! Thanks a lot!
Thanks for the excellent video.. Any tool I learn about, if it is not used in our real life projects, it disappears from our mind quickly.. that's the challenge!... confidence grows only when u use in real life projects.
You are always good with the contents. Keep helping the community. If you can add something on devops security in detail it would be great help. Thanks for all.
Hi Ankush, thanks for your feedback. We will create a complete DevSecOps course probably this year - you can add your email to the waitlist so you will get notified: www.techworld-with-nana.com/course-roadmap
Thank you Nana! I’m web developer so I don’t actively learn CI/CD but the techniques you’ve described here are generic enough and very good to apply in any domain! Thanks again for your work!
Nana , Patience is the key I started to learn DevOps Technologies since my 2nd yr in college and eod I landed into the production as a DevOps engineer I agree its always overwhelming with lot of tools personally I also felt the same so to overcome it , be patience learn one by one and get hands dirty
Summary CI/CD = continuous integration & development IaC = infrastructure as Code 1. Why? Understand the purpose before learning. What problems does it solve? 2. How? Does terraform do it (declarative, state, etc) 3. Hands-on Simple use case (for motivation) ex: take simple project and dockerify it Tips - Use official documentation on a specific topic - Online courses - Patience - Don't rush: good foundational knowledge (take time) - Continous learning - Stay up to date (Follow communities, social media, letters, channels)
Thank you so much for sharing this content. It's so easy to get overwhelmed but loved what you said about separating "concepts" vs "tools" because this allows you to build different roadmaps of learning to eventually allow them to meet.
OMG!! 🤯!! Much needed. Was an ArcSight SIEM admin then SPLUNK ES with little accessibility and now onto Elasticsearch. All in a little over 3 years and being introduced to DevOps as it now a requirement for Cyber Security Administration/Specialist.Started with Bitbucket without the WHY lol and now...so many tools
Easily a landmark video to share for anyone looking to get into this wonderful world of DevOps or even someone in the field for some time to consider how to best get up to speed with the ever moving targets that is our DevOps tools :) Thanks Nana!
@@TechWorldwithNana nah thank you for all of the amazing content that you share on this channel! I first heard about GitOps and ArgoCD through your channel when I browsed around after looking for videos to understand Kubernetes stateful sets. Glad that the TH-cam / Google algorithms worked out to find the amazing content here, keep it up :)
Thank you for this video. I was from a full-stack developer bootcamp and somehow I was in an apprenticeship as a SecDevOps. This certainly breakdown the Golden Circle on Dev Ops.
I subscribed to your channel when you had around 500 subscribers. Now you are at more than 500,000 subscribers. Hoping to see a million subscribers soon.
Nana, this is obviously for me..I am having a career shift into Devops from Data centre management .Sincerely, it looks scary to me sometimes but there is an inner force that tells me I can do it.Thanks for these wonderful tips.And should you have a way of helping me acheive my goal of becoming a Devop Engineer beyond these tips,I will be extremely glad.
Very good advice. I will add the following: Write down details, study notes. It activate parts of your brain that help you to remember better. Later when/if you do want to relearn and/or add new use cases, you can update the notes and get up to speed fast. Also in my labs over time I have kept some virtual machines that I could take out a year, 2 years, 10 years later on, update and work with the latest products.
Nana, I just wanted to thank you so much. One year ago I watched one of the first videos of your channel, I landed a devops engineer role 4 months ago. Thank you so much Nana
Network engineer here ( the older dinosaur genre to be specific); Nana you are quite the shinny white angel in the IT tipping edge of things, I am and have been mostly an Infra person, but somehow what you have iterated here compels nd beckons for improvement how I would view network core tasks, amazing stuff. Thanks Nana
I'd like to add another tip that works very well to me. Having a markdown project to write down important information related to what you are learning. One could say "but the documentation is already written out there... why am I going to write down duplicate things?" Well, actually is not just writing, it's about how you organize your notes, you have to think about where should I put this information? on what abstract level? The way I see it is that answering that questions actually helps keeping the information in your head.
Thanks for the video you touched on a good point about not rushing and 1 step at the time. The challenge i am having is getting an interview not sur if my resume is poorly written or i should just wait.
i've recently become the tech lead for one of my employer's most used platforms, and one of the challenges i'm facing now is learning all of the surrounding tools and processes around it. Kubernetes was one of those tools so i thought OK, time to learn it. I'm so glad i watched this because you outline the importance of understanding why a tool is needed first, which makes learning the tool itself much easier. Practicing this holistically is great advice. Thank you!
Thanks for the tips. I often miss on creating a simple usecase before learning new tool which makes me forget the concepts. This video is very helpful.
One more thing to add is when learning a new technology that solves a problem, and if you know other technology that solves the same problem then just try to identify the blocks which do the same operation in both technologies
Nana is freaking awesome! I just discovered the channel a few days ago, and have found it a very valuable resource. When learning something new I will now be checking this channel first to see if there's a video on the subject!
Im a senior developer and have such a huge backlog on technologies im currently learning, it can be extremely overwhelming. It used to be just learn java, spring framework and the occasional framework here and there or architecture. Now tho its very overwhelming, but also Exciting. Ive been actually doing the transition to Cloud Architect, and had to learn DevOps, architectural knowledge on microservices, event-driven, etc. But the backlog is there, im actually doing right now my AWS Solution Architect Certification, then i have queued, Apache Kafka, Kubernetes, Linux (finally want to take it to a more professional level instead of just the basics), many things from Spring that i need to reupdate myself with, and then AWS Solution Architect Professional and Networking Specialty. The only way i can achieve this is focusing one at a time, and be patient. Im doing AWS Solution Architect and Kafka between now and the summer, then for the remainder of the year ill probably have my hands full with job, kubernetes and spring. Ill start the next year strong with Linux. And afterwards i can focus exclusively on the harder AWS Certifications. As you see its a long and painful road. But very exciting. I also had to cut down on many things i want to see, for example i want to visit at some point node.js, not so much for the front end aspect but as an architectural deep dive of sorts. Then if i include all the other DevOps stuff like Ansible, the testing, etc. Yes its overwhelming, but prioritize, narrow down a little bit, then go ahead.
As a DevOps professional, you have to enjoy or have a passion for different disciplines: hardware, software, infrastructure, then those areas can be sub-divided into smaller chunks (ex: infrastructure into Networking, Certificates, encryption), and then all the Integration points. Now you can finally know the use-cases and the tools to fill in those use-cases. You can't do everything so be an expert in one or few areas and then grow from there. Start small and simple, and then add knowledge on top of that.
Thanks for your coment Mr Richard Nunez , I am now a software engineer student in my last year and I want to build a career in devops engineering but there are a lot of opportunities in Web dev and full-stack dev I don't know is it relevant to build a career on full-stack dev and after with experience move on to DevOps, or in another word what is the optimal path to be a good DevOps enginner?
@@abdellahelgourami7609 DevOps people come from two backgrounds: programmers or sysadmins. I was a programmer and did lots of different stuff (web, desktop, VB, VBA, C#, Java, C, C++, bat, bash, PowerShell, etc). Working with all sorts of stuff helped me to create CI/CD pipelines. And my journey into DevOps took off from there. Knowing how those programs worked and operated on infrastructure, and then getting the infrastructure working helped me to become a DevOps pro.
Thank you for this Nana, I am on my upskilling journey right now, starting from AWS SAA and moving on to my DevOps destination. My past experience has been in tech support so hopefully this will be a natural progression..
Thank you! This should be the introduction of all DevOps class or training. I love it! You actually showed me how to be a DevOps in 15 minutes. This is fantastic! Thank you!
Spot on, all of your remarks are of importance! I'm enjoying your video's. You obviously are putting a lot of time preparing and presenting. They are clear and concise. Thanks
Hi Nana, really love your tutorials. And this one rock's it as well. I have 2 questions for personal reference reasons: 1) Can you please share some average stats on the (NETT & BRUTTO) time it takes someone (...like you => so with experience) to get from the WHY Stage to the COVERED stage assessing something new detailed to: a) New Tech. Concept, b) New Tool/Framework/Platform/Solution. 2) What proved as efficient personal strategy to record your learnings in a way that you can get back to them one year later. And I mean besides running this channel ;o) Let me share first my averages as kind of a template and invitation to everybody to share: But first some scoping: - Energy-Level: there is a difference between Personal Free Time mode and Professional Business mode, in terms of the energy level you run. I'm sharing my Personal Free Time Mode stats here (where I allow myself to flow at what ever energy level I have. At work I'm burning with my max-energy and can cover significant more ground in shorter time). - Experience Level: As you mentioned, the more you know the easier it is to connect the dots. You are definitely faster in digesting new stuff, compared to someone who just started, has less real life experience and has to lookup (exaggerating) every keyword as a new concept ;o). I'm quite a couple of years in the field (>20), and can confirm that my journey lead me to pretty much the principles you describe. - Brutto/Netto: BRUTTO: Time spent including breaks and distractions. How many Hours/Days/Weeks was it a Topic for you till you could close the case as COVERED. NETTO: Concrete Time spent on the TOPIC itself, excluding breaks or other non related activities. - Targeted Know-How Level: Management Level: - got the gist of the concept. - top(1-3) players (Tools / Service Providers, ..) - top Pro's & Con's Architect/Principal/Consultant: same as Management + Architecture understanding, Tech. dependencies and at least a HandsOn Tutorial executed. DevOps Practitioner: same as above + read the docs and tested it in a (small) real life project. So here come my "Free Time mode" stats [BRUTTO/NETTO]: a) New Concept: @Management : 2d / 4h @Architect/co. : 1w / 2d @DevOps pract. : 2w / 1w b) New Tool: @Management : 2h / 2h @Architect/co. : 0.5d / 1d @DevOps pract. : 3d / 2d b) New Platform/Framework: @Management : 1d / 4h @Architect/co. : 3d / 2d @DevOps pract. : 1w / 3d Looking fwd. & Thanks for sharing :o)
It is not just about IT or DevOps. These principles are applicable for all human activities. i learned them and followed from primary school when learned math. Very surprised that people with Uni degree do not understand or do not follow them.
Wow! This video comes in just when I need it. I'm in the same boat as many of them here, just started getting into DevOps and already started feeling overwhelmed with the number of concepts and tools I had to learn. I took a course and learning everyday. They teach a variety of DevOps tools / skills needed like Python, Linux, Shell scripting (Docker, AWS, Kubernetes, Ansible are yet to come), and all of them are new to me, I just have a very basic understanding of what they do but not how. So my goal is to learn them deeply. Your techniques are very helpful and I will keep applying them as I go through the learning process, but I think this DevOps journey is going to take a few years to become better with DevOps. But I'm also afraid of changing tools and technologies very fast these days. Thank you so much for this valuable content! You've earned a new subscriber :) Please continue the awesome work.
Awesome video Nana! You hit on some great learning strategies and learning points. The foundational knowledge point is vital. It makes picking up newer concepts much easier. Also, building a home lab helps with practice.
A career in technology means that it is a lifelong pursuit of learning. A technology professional should strive to put in one hour per day dedicated to that. How does one find the time? Well, if you have time to watch TH-cam videos or go on eBay during your work day, you certainly can find the time to learn. So make use of your downtime as much as possible in that regard. Turn that downtime into avenues of pure net profit as you invest in your career.
Because you're brilliant and above human! 😂 I have followed you for a year and recently you were the topic of discussion in my group of developers. You make us feel lazy 😂
Thats Exactly what I do , I play with a small user situation on a new technology. At the moment im just learning Jenkins . But Did Terraform and Puppet before it . Since im not a DevOp Engineer this is really new to me. Im old school Linux engineer brought up with TIN
1 year later, I am still here. All the best to everyone who's working so hard to put all these videos together. When I first started, I was a beginner. Now, after one AWS Solution Architect certification later, I am ready to dig deeper into Kubernetes and Terraform. I am grateful for this channel. Cheers. You guys keep uploading, we'll keep learning :)
Thank you so much for this video, I am an IT Administrator trying to enter to the DevOps field and it is hard for me to understand what to learn because there is too much tools, now I will follow your advice.
Hello Nana, hi community. First I say thank you for this and your other videos about how to become a DevOps Engineer. You made my day, by explaining that concepts first is the way to go. I started learning to code and how to do software development and deployment earlier this year and first became a victim of the so called Tutorial Hell. I will sure follow your suggestions on how to learn the things. For me, the most annoying and difficult obstacle to get it going is, that I need the Cloud Providers. As an IT Systems Engineer I could learn much stuff by using some old hardware and get my hands dirty on it. While all major Cloud Providers offer free tiers and services, you gotta have a university degree to dig their offer and price structure. My first step now is to find the right platform to start with. Self hosting a cloud seems not to be so easy. Thanks again, and I'm for sure subscribed and liked and I am looking forward to see more of your videos. Have a good time you all and happy automating.
I started my IT career 16 years ago. In the beginning of career, if I knew the industry would evolve into what it is today where we need to have knowledge on so many tools and technologies, I would have given up on IT and switched to another industry to avoid the stress of having to learn so many things ceaselessly. Now I feel like I am just a technology SLAVE. This industry is absolutely terrible. I don't know what will happen in another 10 years. Maybe the tools and technologies that we have spent so much time and effort to learn today will all be wiped out AGAIN in 10 years. The pain will never end.
Wow, great information. Hello, I am currently taking a very costly AWS for jobs course which has some DevOps features. After two nights a week of video lectures. I find my way back to your channel where I am learning more about DevOps. What is unfortunate for me is I found your site after I paid for my current course, (Yellowtail tech). Now, I am really regretting it. I also want to thank you for this video, I have been overwhelmed with trying to learn and understand the introduction to DevOps, and your video really helps gain some understanding of what I what to achieve. Thanks again.
Thank you for sharing, devops tech move very Quickly sometimes Im worry i will always feel stressed just to keep up with it. I need a good system that i can follow to constantly keep up without feeling overwhelm.
Hi Nana, it was really amazing video and lot of us were and are facing this issue of staying updated with every new tools coming up every now and then. You broke down every tip perfectly , many of us follow the same way for learning new things , it may not be in this type of proper managed way sometimes due to job or sometimes due to not finding the right content. Your videos always help in one or other way. Looking forward to watching your videos which helps in overall development along with tool/topic specific on devops. Thanks and Regards.
As always Miss Nana a wonderful video and excellent topic to focus on. Thanks for creating these videos! I can say as a individual from the collective group of the tech world, we all appreciate the effort and content provided from this channel!
Thanks for another great video! Like you said, I know various concepts and some tools, but now I know how to resolve the confusions and stay relevant! Thanks!
Howdy Nana, very authoritative content and angle of approaching subject of learning on the shifting sands of the DevOps-verse, I find it very masterful : Always start with concentp > decide tools > then get comcept of Tool But the business powers that may be - deadlines and delivery - how do you overcome the steep learning curves on a tight time frame : How do you become efficient -quickly enough to learn and to deliver ?
Thank you for sharing the tips. One of the challenge , I often face is how to evaluate which tool is optimal for the given usecase , as there are many overlapping functionalities provided by different tools (i have been in this field for around 3 months). Any suggestions on this is much appreciated.
Hey, Nana (and everyone else who wants to join the conversation)! What’s your opinion on reading books? I personally do not have enough patience to read a whole 600-something pages book on a single subject. However, I see them often on the market, especially on dev tools. Do you read books? Is that an efficient way for you to learn? This is mainly the question for cases when you are already familiar with the subject and want to proceed to a more senior level. P.S. I'm a backend engineer, but I'm sure the DevOps field has pretty much the same literature market.
You have been doing really great things pumping people for consistent learning and how to stay upto date by embracing a change in HABIT of LEARNING continously . Thanks a lot for all ur Devops videos it really helps a lot . !
I hope sharing my experience and tips on this topic was useful for you 😊 How do you keep up with technology developments and what are some of your tips on that? 🙋🏽♂️
▬▬▬▬▬▬ ⬇ Resources to learn DevOps ⬇ ▬▬▬▬▬▬
💙 Subscribe to me on TH-cam :) 👉🏼 bit.ly/2z5rvTV
💛 High-Quality and Hands-On Courses 👉🏼 bit.ly/3q7QTTO
💚 Become a DevOps Engineer - full educational program 👉🏼 bit.ly/3OA3Orz
Sign up to get notified about new upcoming courses ► www.techworld-with-nana.com/course-roadmap
▬▬▬▬▬▬ T I M E S T A M P S ⏰ ▬▬▬▬▬▬
0:00 - Intro - Why it's overwhelming
01:24 - DevOps ecosystem - Separate Concepts and Tools
03:32 - How to actually learn?
04:01 - Use Cases - What problems the DevOps tool solves?
05:31 - How does the tool work?
06:10 - Hands-On Practice with a realistic use case
09:20 - Patience while learning
10:20 - Embrace lifelong learning
10:58 - How to stay up to date?
I enjoy most of your videos relevant to "on ground" operation. DevOps indeed a challenge to all levels not just happily setup alone as well troubleshoot and bug fixes on every single software..Gosh what happen it breaks ..oops !!.. Devops aka middleware i.e understand infra and application to gel all in one. awesome sharing ..
Fantastic lectures!!
Thanks a lot Nana, for your job, your time !
Does you have any devops course on udent
As always a fantastic point of view, totally agree...especially in "how to learn", because it focus the time and learning process in what really matter, that is solve a problem.
Nana this is not only for DevOps, what you just synthesized in these 12 minutes can be applied in all the IT branches from operations to code development and research, a very good video and I totally agree with these techniques .
Thank you for this great feedback Don!
@@TechWorldwithNana You are really brilliant Nana. In English to boot!
Nana is very smart lady . I love her clarity
I’m a junior devops, I often watch your video, they are sooooooo helpful for me at work. I love the way you explain technology from big picture to practical demos with awesome visualization through the entire process. That’s really human mind friendly. Also, your peaceful tone can always comfort my busy mind in the beginning of learning process. Thank you soooo much! Please keep up with this great work! 👍👍👍
Wow thank you Nicole for this amazing feedback, that makes me happy :)
@@TechWorldwithNana Glad to know 😆😆
Hello I'm training to be a devops engineer, can I connect with you please?
1. Concepts and processes before tools: challenges, steps, pros, cons, why, what is the purposes
2. Learn tools, use cases fit tools in the big picture, what problem does it solves?
3. How does the tool work?
4. how is it compared to other tools?
5. hands on-practice, simple case
6. Expand the use case
7. References - documentation, tutorials
8. Patience - good foundation, makes click
9. Continous learning -community, blogs...keep update
Thanks
Learning is one part, retention is whole new game 😊
Totally agree
And that i think can be supplemented by practicing on real use cases . At least, that's what works for me.
working for a company/manager that doesn't expect you to be 12 people in one with 20 years of experience with react hooks, data warehousing, proficiency in 30 middle tier languages, knowledge of gitlab, github actions, jenkins, jenkin x, ansible, all the linux distros, all the bsds, windows, embedded programming, VR device manufacturing, materials science, native German, Spanish, Chinese, Japanese, Korean, Russian and other human natural languages (they always put "etc" in the job description), and also can clean toilets all for 9$/hr is another thing.
Replication is the hardest! LOL. Imagine do a proof of concept on the fly! Oh man documentation is a real challenge as an engineer!
@@Mrslykid1992 oh yes , there is not enough time in the world for the documentation 😀
I like the emphasis on figuring out why you should learn a given tool and understanding what problem it solves. It’s easy to try to learn a tool because you know it’s what people use, but understanding why and the underlying concepts first helps frame it in your mind when learning.
I spend a lot of time learning new web dev frameworks and npm libraries. And when I jump right in without really taking time before hand what problems it’s mainly addressing and the goals behind it, it’s a much worse learning experience all around or really appreciate the tool for what it solves.
Senior developers find it hard to learn new things cause they fail to adapt to change due to feelings of cognitive dissonance . The greatest barrier to this change is the belief that ‘they are smart’. While learning new stuff you experience feeling dumb. Once you learn to identify this stage of cognitive dissonance - and learn to push through it you end up being a life long student. Great video. Keep up the good wirk
As someone who transitioned from the nuclear industry (where technology hardly budged over the course of a decade), and literally fell into a MLOps role (where shiny new features and tools are released every minute), I must say that this video made me feel way better. Thanks so much!
Not particularly interested in DevOps, but still found these tips helpful. This is can be applied to anything else tech related.
I just started my journey on the DevOps career path. I had no idea how many tools were available, and used together. I will keep this advice in mind as I move through the process of learning all of them. Thanks for sharing!
Nana, I am a Sr. Business Analyst but I love watching your videos to help me understand complex subjects. They are just the right length for me. You should teach at a college or for those that are trying to learn these concepts.
This video could not have been recommended to me at a better time! I just made a career switch to DevOps and I feel overwhelmed with all the information out there. Thanks Nana for the advice - will definitely try them!
Precious, precious advice for learning literally anything. Problem-oriented learning is the way to go!
@Radical Ed yeah def. Tools come and go. Problems stay.
Really love your series on Kubernetes and Service Mesh, I save those videos in a playlist and watch them to refresh my memory. Thanks!
That's cool, thanks for this great feedback! :)
7c's of DevOps Continuous (Planning, Development, Integration, Deployment, Testing, Delivery & Monitoring, and Feedback), then 8th C "Continuous Learning" added
Concepts > Tools > Understand the problems the tools solve > Breakdown each step > Apply to your existing project. Thanks alot 😊👍
It's really rare to be person having much of knowledge and being excellent at teaching. Thank you very much Nana, I was soaking every word you said in the video.
The other point I want to add to the patience category is a lack of progress, especially when you are new to a tool or concept.
This frustrates many people and makes them give up on learning stuff when things simply don't work.
Understand that every single developer you admire or look up to was exactly in that stage not too long ago.
Breathe, go for a quick walk, reset and start again.
Thank you Nana for wonderful video. You really broken entire DevOps into simpler steps and make me understand the real picture. Really, I was overwhelmed when I was first learning the GIt Lab, Liquibase, and Docker and trying to learn entire tools and features through their company documentation. Which made me go crazy and not sure how to follow and keep up with project timelines. You are genius and thank you once again for helping folks like me.
I appreciate it, Nana; this is the best video I've ever watched. I currently work as a cloud engineer using an outdated approach of distributing software, but I'm feeling strongly motivated to switch to a career as a DevOps engineer. Actually, I'm getting ready for that. Your channel is quite useful in that regard. Thank you for making such wonderful contents.
This video is a wisdom. Just exactly when I was overwhelmed with the new end to end role. Great work + great timing👏👏
Thank you, happy it's useful for you :)
I think good paitence also stems from keeping good motivation to what you're learning. If you hit similar concepts you've already learnt, that can become boring, and demotivating, even though those concepts are foundational to what you're learning.
This was super helpful. Thank you. As a junior full stack engineer I’ve found it hard juggling both learning and understanding technologies that I need to know for my job. I’d never heard of terraform before and didn’t know what docker did fully or how it all integrated in aws etc so to be hit all at once was overwhelming.
One thing Ive found that helped me was creating diagrams as I’m quite a visual learner. Also then explaining the tech I’m trying to learn to my husband (who is now thoroughly bored I’m sure, but endures it for me) to help solidify my understanding.
what resources (which youtube channels, tutorials, documentations) did you refer
Much needed video! Recently started with DevOps and it is indeed overwhelming!
Great to hear! It will get easier, once you have a good foundation. And the good thing is that you will get rewarded for your efforts as it's a very demanded job nowadays :)
@@TechWorldwithNana Rightly said Nana, its been chaotic learning so far because of the timelines. I will re-structure my learning process. This video surely helped!! Thanks a lot!
Don't be afraid. nana has prepared everything you need
Thanks for the excellent video.. Any tool I learn about, if it is not used in our real life projects, it disappears from our mind quickly.. that's the challenge!... confidence grows only when u use in real life projects.
You are always good with the contents. Keep helping the community. If you can add something on devops security in detail it would be great help.
Thanks for all.
Hi Ankush, thanks for your feedback. We will create a complete DevSecOps course probably this year - you can add your email to the waitlist so you will get notified: www.techworld-with-nana.com/course-roadmap
Thank you Nana! I’m web developer so I don’t actively learn CI/CD but the techniques you’ve described here are generic enough and very good to apply in any domain! Thanks again for your work!
Hi Andrei, glad it was helpful for you as well! And yes I'm sure it's applicable for other IT fields as well :)
Nana , Patience is the key I started to learn DevOps Technologies since my 2nd yr in college and eod I landed into the production as a DevOps engineer I agree its always overwhelming with lot of tools personally I also felt the same so to overcome it , be patience learn one by one and get hands dirty
Summary
CI/CD = continuous integration & development
IaC = infrastructure as Code
1. Why?
Understand the purpose before learning.
What problems does it solve?
2. How?
Does terraform do it (declarative, state, etc)
3. Hands-on
Simple use case (for motivation)
ex: take simple project and dockerify it
Tips
- Use official documentation on a specific topic
- Online courses
- Patience
- Don't rush: good foundational knowledge (take time)
- Continous learning
- Stay up to date (Follow communities, social media, letters, channels)
I Like: learning the concept and need first to understand any tool (tools are just used to solve a specific/multiple problems).
Thank you so much for sharing this content. It's so easy to get overwhelmed but loved what you said about separating "concepts" vs "tools" because this allows you to build different roadmaps of learning to eventually allow them to meet.
Agree as a newbie I am facing…
Much awaited video. Thank you Nana for making this video. You put a smile on every one who is overwhelmed and Stressed out or burned out.
I absolutely love your videos. I admire how well-structured your thought process is and your beginner to advanced approach. Kudos 👏
OMG!! 🤯!! Much needed. Was an ArcSight SIEM admin then SPLUNK ES with little accessibility and now onto Elasticsearch. All in a little over 3 years and being introduced to DevOps as it now a requirement for Cyber Security Administration/Specialist.Started with Bitbucket without the WHY lol and now...so many tools
Easily a landmark video to share for anyone looking to get into this wonderful world of DevOps or even someone in the field for some time to consider how to best get up to speed with the ever moving targets that is our DevOps tools :)
Thanks Nana!
Wow thanks Daniel for this great feedback! :)
@@TechWorldwithNana nah thank you for all of the amazing content that you share on this channel! I first heard about GitOps and ArgoCD through your channel when I browsed around after looking for videos to understand Kubernetes stateful sets. Glad that the TH-cam / Google algorithms worked out to find the amazing content here, keep it up :)
Thank you for this video. I was from a full-stack developer bootcamp and somehow I was in an apprenticeship as a SecDevOps. This certainly breakdown the Golden Circle on Dev Ops.
I subscribed to your channel when you had around 500 subscribers. Now you are at more than 500,000 subscribers.
Hoping to see a million subscribers soon.
Nana, this is obviously for me..I am having a career shift into Devops from Data centre management .Sincerely, it looks scary to me sometimes but there is an inner force that tells me I can do it.Thanks for these wonderful tips.And should you have a way of helping me acheive my goal of becoming a Devop Engineer beyond these tips,I will be extremely glad.
Very good advice. I will add the following: Write down details, study notes. It activate parts of your brain that help you to remember better. Later when/if you do want to relearn and/or add new use cases, you can update the notes and get up to speed fast. Also in my labs over time I have kept some virtual machines that I could take out a year, 2 years, 10 years later on, update and work with the latest products.
Thanks for sharing Bent!
Notes means writing with pen on paper or typing on word doc?
My passion is DevOps and for me it's the future. Awesome breakdown! I want to be like you when I grow up 😉
Nana, I just wanted to thank you so much. One year ago I watched one of the first videos of your channel, I landed a devops engineer role 4 months ago. Thank you so much Nana
That's so great, thank you for sharing and all the best with your DevOps engineer job :)
@@TechWorldwithNana Thanks a lot Nana 🤗
This was very helpful. What helped the most was the reminder of learning the concepts 1st, then the tools. That opened the way for me.
Really glad the video was helpful Robert!
Learning with a use case is spot on. Learning without a use case is like frosting without the cake.
You are the revolution DevOps engineers needed in the current world. Thank you mam.
How about train with shubham? 😂😂😜😜😜.
@@hardikgangani4369 ghanta chu****p....waise tutors Mukherjee Nagar mein book khol ke nai bataa paate
Network engineer here ( the older dinosaur genre to be specific);
Nana you are quite the shinny white angel in the IT tipping edge of things,
I am and have been mostly an Infra person, but somehow what you have iterated here compels nd beckons for improvement how I would view network core tasks,
amazing stuff. Thanks Nana
I'd like to add another tip that works very well to me. Having a markdown project to write down important information related to what you are learning. One could say "but the documentation is already written out there... why am I going to write down duplicate things?" Well, actually is not just writing, it's about how you organize your notes, you have to think about where should I put this information? on what abstract level? The way I see it is that answering that questions actually helps keeping the information in your head.
Learn why of the tool before the actual tool and hands-on with a real use case example are the gold suggestion I found in this videos
Thanks for the video you touched on a good point about not rushing and 1 step at the time. The challenge i am having is getting an interview not sur if my resume is poorly written or i should just wait.
I see you had put full effort on your teaching video. You are standing out from other people. Good luck.
i've recently become the tech lead for one of my employer's most used platforms, and one of the challenges i'm facing now is learning all of the surrounding tools and processes around it. Kubernetes was one of those tools so i thought OK, time to learn it. I'm so glad i watched this because you outline the importance of understanding why a tool is needed first, which makes learning the tool itself much easier. Practicing this holistically is great advice. Thank you!
Thanks for the tips. I often miss on creating a simple usecase before learning new tool which makes me forget the concepts. This video is very helpful.
One more thing to add is when learning a new technology that solves a problem, and if you know other technology that solves the same problem then just try to identify the blocks which do the same operation in both technologies
Nana is freaking awesome! I just discovered the channel a few days ago, and have found it a very valuable resource. When learning something new I will now be checking this channel first to see if there's a video on the subject!
As a QA, I can feel the concepts in this channel is quit challengeable. But I enjoy, I learn
Im a senior developer and have such a huge backlog on technologies im currently learning, it can be extremely overwhelming. It used to be just learn java, spring framework and the occasional framework here and there or architecture.
Now tho its very overwhelming, but also Exciting. Ive been actually doing the transition to Cloud Architect, and had to learn DevOps, architectural knowledge on microservices, event-driven, etc.
But the backlog is there, im actually doing right now my AWS Solution Architect Certification, then i have queued, Apache Kafka, Kubernetes, Linux (finally want to take it to a more professional level instead of just the basics), many things from Spring that i need to reupdate myself with, and then AWS Solution Architect Professional and Networking Specialty.
The only way i can achieve this is focusing one at a time, and be patient.
Im doing AWS Solution Architect and Kafka between now and the summer, then for the remainder of the year ill probably have my hands full with job, kubernetes and spring.
Ill start the next year strong with Linux.
And afterwards i can focus exclusively on the harder AWS Certifications.
As you see its a long and painful road. But very exciting. I also had to cut down on many things i want to see, for example i want to visit at some point node.js, not so much for the front end aspect but as an architectural deep dive of sorts.
Then if i include all the other DevOps stuff like Ansible, the testing, etc. Yes its overwhelming, but prioritize, narrow down a little bit, then go ahead.
Thanks so much Nana..this is really going to help me as i embark on my DevOps journey... i will be starting this Feb. 2023.
As a DevOps professional, you have to enjoy or have a passion for different disciplines: hardware, software, infrastructure, then those areas can be sub-divided into smaller chunks (ex: infrastructure into Networking, Certificates, encryption), and then all the Integration points. Now you can finally know the use-cases and the tools to fill in those use-cases. You can't do everything so be an expert in one or few areas and then grow from there. Start small and simple, and then add knowledge on top of that.
Thanks for your coment Mr Richard Nunez , I am now a software engineer student in my last year and I want to build a career in devops engineering but there are a lot of opportunities in Web dev and full-stack dev I don't know is it relevant to build a career on full-stack dev and after with experience move on to DevOps, or in another word what is the optimal path to be a good DevOps enginner?
@@abdellahelgourami7609 DevOps people come from two backgrounds: programmers or sysadmins. I was a programmer and did lots of different stuff (web, desktop, VB, VBA, C#, Java, C, C++, bat, bash, PowerShell, etc). Working with all sorts of stuff helped me to create CI/CD pipelines. And my journey into DevOps took off from there. Knowing how those programs worked and operated on infrastructure, and then getting the infrastructure working helped me to become a DevOps pro.
THANK YOU @@Antebios for your reply, and about the average time to have the necessary experience in dev before jump into DevOps ?
Thank you for this Nana, I am on my upskilling journey right now, starting from AWS SAA and moving on to my DevOps destination. My past experience has been in tech support so hopefully this will be a natural progression..
Thank you! This should be the introduction of all DevOps class or training. I love it! You actually showed me how to be a DevOps in 15 minutes. This is fantastic! Thank you!
Thank you Nana. You’re a super hero and thanks for all you do. This video has gone a long way to help.
Spot on, all of your remarks are of importance! I'm enjoying your video's. You obviously are putting a lot of time preparing and presenting. They are clear and concise. Thanks
I love this Nana, I've been having periods of Learning and then being overwhelmed 🙃then anxiety
For me a great instructor is important in order not to be overwhelmed. If I want to learn golang, your video was easy to start with.
im starting to watch your playlist i have time to learn i will be a devops :)) Thanks for your Content
Hi Nana, really love your tutorials. And this one rock's it as well. I have 2 questions for personal reference reasons:
1) Can you please share some average stats on the (NETT & BRUTTO) time it takes someone (...like you => so with experience) to get from the WHY Stage to the COVERED stage assessing something new detailed to:
a) New Tech. Concept,
b) New Tool/Framework/Platform/Solution.
2) What proved as efficient personal strategy to record your learnings in a way that you can get back to them one year later. And I mean besides running this channel ;o)
Let me share first my averages as kind of a template and invitation to everybody to share:
But first some scoping:
- Energy-Level: there is a difference between Personal Free Time mode and Professional Business mode, in terms of the energy level you run.
I'm sharing my Personal Free Time Mode stats here (where I allow myself to flow at what ever energy level I have. At work I'm burning with my max-energy and can cover significant more ground in shorter time).
- Experience Level: As you mentioned, the more you know the easier it is to connect the dots. You are definitely faster in digesting new stuff, compared to someone who just started, has less real life experience and has to lookup (exaggerating) every keyword as a new concept ;o).
I'm quite a couple of years in the field (>20), and can confirm that my journey lead me to pretty much the principles you describe.
- Brutto/Netto:
BRUTTO: Time spent including breaks and distractions. How many Hours/Days/Weeks was it a Topic for you till you could close the case as COVERED.
NETTO: Concrete Time spent on the TOPIC itself, excluding breaks or other non related activities.
- Targeted Know-How Level:
Management Level:
- got the gist of the concept.
- top(1-3) players (Tools / Service Providers, ..)
- top Pro's & Con's
Architect/Principal/Consultant: same as Management + Architecture understanding, Tech. dependencies and at least a HandsOn Tutorial executed.
DevOps Practitioner: same as above + read the docs and tested it in a (small) real life project.
So here come my "Free Time mode" stats [BRUTTO/NETTO]:
a) New Concept:
@Management : 2d / 4h
@Architect/co. : 1w / 2d
@DevOps pract. : 2w / 1w
b) New Tool:
@Management : 2h / 2h
@Architect/co. : 0.5d / 1d
@DevOps pract. : 3d / 2d
b) New Platform/Framework:
@Management : 1d / 4h
@Architect/co. : 3d / 2d
@DevOps pract. : 1w / 3d
Looking fwd. & Thanks for sharing :o)
11:42 the golden line if you feel interesting you will find your own way to do it.
It is not just about IT or DevOps. These principles are applicable for all human activities. i learned them and followed from primary school when learned math. Very surprised that people with Uni degree do not understand or do not follow them.
Wow! This video comes in just when I need it. I'm in the same boat as many of them here, just started getting into DevOps and already started feeling overwhelmed with the number of concepts and tools I had to learn. I took a course and learning everyday. They teach a variety of DevOps tools / skills needed like Python, Linux, Shell scripting (Docker, AWS, Kubernetes, Ansible are yet to come), and all of them are new to me, I just have a very basic understanding of what they do but not how. So my goal is to learn them deeply.
Your techniques are very helpful and I will keep applying them as I go through the learning process, but I think this DevOps journey is going to take a few years to become better with DevOps. But I'm also afraid of changing tools and technologies very fast these days.
Thank you so much for this valuable content! You've earned a new subscriber :) Please continue the awesome work.
Wow... what a great video nana AGAIN👌🔥We really needed this video... Thanks dear nana🙏🌱💯
Thank you Nana, I definitely needed it, I’m trying hard 🎉
I'm going to start a new job as a devops engineer soon and this guide will help me in adapting to the devops setup in my new company. Thank you
Awesome video Nana! You hit on some great learning strategies and learning points. The foundational knowledge point is vital. It makes picking up newer concepts much easier. Also, building a home lab helps with practice.
A career in technology means that it is a lifelong pursuit of learning. A technology professional should strive to put in one hour per day dedicated to that. How does one find the time? Well, if you have time to watch TH-cam videos or go on eBay during your work day, you certainly can find the time to learn.
So make use of your downtime as much as possible in that regard. Turn that downtime into avenues of pure net profit as you invest in your career.
Because you're brilliant and above human! 😂 I have followed you for a year and recently you were the topic of discussion in my group of developers. You make us feel lazy 😂
Subscribed, I've seen many of your vids in the past. Your explanations are always on point. Really appreciate you!
Thanks so much Josh!
Thats Exactly what I do , I play with a small user situation on a new technology. At the moment im just learning Jenkins . But Did Terraform and Puppet before it . Since im not a DevOp Engineer this is really new to me. Im old school Linux engineer brought up with TIN
Thanks for sharing :)
1 year later, I am still here.
All the best to everyone who's working so hard to put all these videos together.
When I first started, I was a beginner. Now, after one AWS Solution Architect certification later, I am ready to dig deeper into Kubernetes and Terraform.
I am grateful for this channel.
Cheers. You guys keep uploading, we'll keep learning :)
wow.. i am still struggle to learn because of slow thinker
@@gijoe6529 Let me know If I can help in any way. Happy to have a chat with you about it :)
Thank you so much for this video, I am an IT Administrator trying to enter to the DevOps field and it is hard for me to understand what to learn because there is too much tools, now I will follow your advice.
Hello Nana, hi community. First I say thank you for this and your other videos about how to become a DevOps Engineer. You made my day, by explaining that concepts first is the way to go. I started learning to code and how to do software development and deployment earlier this year and first became a victim of the so called Tutorial Hell. I will sure follow your suggestions on how to learn the things. For me, the most annoying and difficult obstacle to get it going is, that I need the Cloud Providers. As an IT Systems Engineer I could learn much stuff by using some old hardware and get my hands dirty on it. While all major Cloud Providers offer free tiers and services, you gotta have a university degree to dig their offer and price structure. My first step now is to find the right platform to start with. Self hosting a cloud seems not to be so easy. Thanks again, and I'm for sure subscribed and liked and I am looking forward to see more of your videos. Have a good time you all and happy automating.
Amazing video as always !!. I am already your fan. A perfect guide and and a clear path laid out to people who wants to start with Devops. Thanks 👍
I started my IT career 16 years ago. In the beginning of career, if I knew the industry would evolve into what it is today where we need to have knowledge on so many tools and technologies, I would have given up on IT and switched to another industry to avoid the stress of having to learn so many things ceaselessly. Now I feel like I am just a technology SLAVE. This industry is absolutely terrible. I don't know what will happen in another 10 years. Maybe the tools and technologies that we have spent so much time and effort to learn today will all be wiped out AGAIN in 10 years. The pain will never end.
Wow, great information. Hello, I am currently taking a very costly AWS for jobs course which has some DevOps features. After two nights a week of video lectures. I find my way back to your channel where I am learning more about DevOps. What is unfortunate for me is I found your site after I paid for my current course, (Yellowtail tech). Now, I am really regretting it. I also want to thank you for this video, I have been overwhelmed with trying to learn and understand the introduction to DevOps, and your video really helps gain some understanding of what I what to achieve. Thanks again.
I generally understand the concept playing with the tools, but anyway once you get the concept, it becomes easier to implement with other tools
Thank you for sharing, devops tech move very Quickly sometimes Im worry i will always feel stressed just to keep up with it.
I need a good system that i can follow to constantly keep up without feeling overwhelm.
Hi Nana, it was really amazing video and lot of us were and are facing this issue of staying updated with every new tools coming up every now and then. You broke down every tip perfectly , many of us follow the same way for learning new things , it may not be in this type of proper managed way sometimes due to job or sometimes due to not finding the right content. Your videos always help in one or other way. Looking forward to watching your videos which helps in overall development along with tool/topic specific on devops. Thanks and Regards.
As always Miss Nana a wonderful video and excellent topic to focus on. Thanks for creating these videos! I can say as a individual from the collective group of the tech world, we all appreciate the effort and content provided from this channel!
One of the best IT channel on YT
I always wondered where people find out about new devops tools. Great video, as always!
Thanks for another great video!
Like you said, I know various concepts and some tools, but now I know how to resolve the confusions and stay relevant!
Thanks!
This is the best video on DevOps overview. Excellent!
First video from new office... As usual a great and informative video...I wish you reach 1 Million followers soon..
Howdy Nana, very authoritative content and angle of approaching subject of learning on the shifting sands of the DevOps-verse,
I find it very masterful : Always start with concentp > decide tools > then get comcept of Tool
But the business powers that may be - deadlines and delivery - how do you overcome the steep learning curves on a tight time frame :
How do you become efficient -quickly enough to learn and to deliver ?
Thank you for sharing the tips. One of the challenge , I often face is how to evaluate which tool is optimal for the given usecase , as there are many overlapping functionalities provided by different tools (i have been in this field for around 3 months). Any suggestions on this is much appreciated.
I wish i had this piece of advice when starting the IT field, very practical and highly useful
Hey, Nana (and everyone else who wants to join the conversation)! What’s your opinion on reading books? I personally do not have enough patience to read a whole 600-something pages book on a single subject. However, I see them often on the market, especially on dev tools. Do you read books? Is that an efficient way for you to learn? This is mainly the question for cases when you are already familiar with the subject and want to proceed to a more senior level.
P.S. I'm a backend engineer, but I'm sure the DevOps field has pretty much the same literature market.
Thanks so much. It's been easier doing my studies in DevOps since after watching your videos. You help make it so much easier.
შესანიშნავი რჩევები, ძალიან დასაფასებელია, ნანა! სასიცოცხლოდ მნიშვნელოვანია სწავლისადმი მიდგომა, ვიდრე დიდი დრო გაატაროთ მცირე მოგებით.
You have been doing really great things pumping people for consistent learning and how to stay upto date by embracing a change in HABIT of LEARNING continously . Thanks a lot for all ur Devops videos it really helps a lot . !
This is the IT field in general. You have to have basic knowledge in JIRA, Slack, Teams, SharePoint, Excel etc.. just to get your work done.
Your videos are always motivating and make for awesome guidelines ! Thanks Nana.