The Ultimate Self-Taught Developer Curriculum

Summary

This video script outlines a comprehensive 12-month curriculum for self-taught developers aiming to become software engineers. It suggests starting with determining one's programming interests, then progressing through language fundamentals, object-oriented programming, and problem-solving exercises. As learners advance, the curriculum covers advanced programming concepts, good coding practices, and tools like Git and GitHub. Later stages introduce data structures, algorithms, and potentially a second programming language for a broader perspective. The final months focus on applying knowledge to projects, exploring system design, and continuous practice to refine skills.

Takeaways

• 📅 The video outlines a 12-month curriculum for self-taught developers to become proficient software engineers.
• 🕒 It's recommended to spend 15-20 hours per week learning, with a focus on mastering a list of topics in a specific order.
• 💡 The curriculum begins with determining the type of programming you're interested in, which will guide your choice of programming language.
• 🔑 Fundamental programming concepts such as control flow, data types, and input/output operations are emphasized as the starting point.
• 🧩 After grasping the basics, object-oriented programming (OOP) principles like classes, inheritance, and polymorphism are introduced.
• 📚 The importance of practicing coding through exercises and problem-solving is stressed to reinforce learning.
• 💻 Advanced programming concepts like memory management, asynchronous programming, and system design are covered in later months.
• 🔗 Learning Git and GitHub is recommended to familiarize with version control and collaboration tools used in software development.
• 🌐 Gaining exposure to different programming languages and their paradigms is suggested to broaden the developer's perspective.
• 📈 The curriculum concludes with studying data structures, algorithms, and potentially system design to prepare for technical interviews and real-world applications.
• 🔗 The sponsor, Scalar, is highlighted for offering mentorship and interview career support to help developers crack tech interviews at top companies.

Q & A

What is the main focus of the video?

The main focus of the video is to share an ultimate self-taught developer curriculum, outlining a list of topics to master and the order in which to learn them to become a software engineer.

How is the curriculum structured in terms of time?

The curriculum is structured as a 12-month schedule, with recommendations on what to learn each month, assuming the learner has 15 to 20 hours per week to dedicate to learning.

What is the first step recommended in the curriculum for a self-taught developer?

The first step is to determine what type of programming the learner wants to do, which involves researching different areas within programming to find what interests them.

Why is it important to learn the fundamentals of programming before moving on to more complex topics?

Learning the fundamentals of programming is crucial as it provides a solid foundation. It ensures that the learner understands basic concepts before tackling more complex topics, which can be discouraging if not grounded in the basics.

What does the video suggest about the importance of object-oriented programming (OOP) in the learning process?

The video suggests that after mastering the basics of a programming language, the next topic to focus on is object-oriented programming. It is considered a fundamental concept that involves learning about classes, objects, inheritance, and other related topics.

How does the curriculum address the need for practice in programming?

The curriculum emphasizes the need for practice by recommending that learners work on exercises, problems, and assessments to reinforce the concepts learned and to improve their coding skills.

What role does the sponsor Scalar play in the video, and what do they offer?

Scalar, the sponsor of the video, is a tech school founded by industry veterans that offers mentorship and dedicated interview career support. They help prepare individuals for technical coding interviews at top companies.

What are some advanced programming concepts recommended to be learned in the curriculum?

Some advanced programming concepts include decorators, code modularity, command line operations, iterators, generators, asynchronous programming, threading, multiprocessing, and memory management.

Why is it suggested to learn another programming language after becoming comfortable with the first one?

Learning another programming language provides a broader perspective on programming paradigms and the strengths and weaknesses of different languages, which is valuable for a well-rounded software engineer.

How does the curriculum prepare learners for technical interviews?

The curriculum prepares learners for technical interviews by covering essential topics like data structures, algorithms, time complexity, and system design, which are commonly assessed in such interviews.

What is the significance of understanding operating system level concepts and computer architecture in the curriculum?

Understanding operating system level concepts and computer architecture provides a deeper insight into how programs execute and how a computer works, which is beneficial for a software engineer to optimize and understand system-level interactions.

Outlines

00:00

📚 Introduction to the Self-Taught Developer Curriculum

The speaker introduces a comprehensive curriculum designed for individuals who are teaching themselves to become software engineers. They outline a list of topics to master, recommend an order of learning, and provide an approximate timeline for each topic based on a 15-20 hour per week study schedule spread over 12 months. The speaker's experience in teaching programming for six years and their own programming experience for ten years add credibility to the curriculum. They also mention their own programming course available at programmingexpert.io and suggest that viewers who are already familiar with coding to check out the video's sponsor, Scalar, which offers a tech school curriculum and interview preparation for top tech companies.

05:00

👨‍💻 Month-by-Month Curriculum and Early Programming Fundamentals

The speaker breaks down the curriculum into a month-by-month schedule, starting with determining the type of programming one wants to pursue and selecting a programming language. They emphasize the importance of learning programming fundamentals such as data types, control flow, and basic syntax before moving on to object-oriented programming (OOP) concepts like classes, objects, inheritance, and interfaces. The speaker suggests spending the first month or two focusing on these fundamentals and gaining comfort with writing basic code and setting up a development environment.

10:02

🔄 Advanced Programming Concepts and Problem-Solving

After establishing a strong foundation in programming basics and OOP, the speaker advises moving on to advanced programming concepts in month four. This includes topics like decorators, code modularity, command-line operations, and understanding of iterators, generators, asynchronous programming, threading, and memory management. They also recommend learning about computer and operating system-level concepts to deepen the understanding of how programs execute and how computers work. The speaker suggests dedicating months four to six to these advanced topics and starting to work on more complex programming problems.

15:02

📈 Refining Programming Skills and Exploring Specializations

In the later months of the curriculum, the speaker suggests focusing on writing clean and efficient code, understanding good programming habits, and learning from others' code on platforms like GitHub and StackOverflow. They recommend learning version control with Git and getting comfortable with command-line operations. The speaker also advises learning a new programming language to gain perspective on different paradigms and tools. Towards the end of the curriculum, they suggest delving into data structures, algorithms, and computer science theory, and considering exploring areas like system design, design patterns, and specialized fields such as artificial intelligence or data science.

Keywords

💡Self-taught developer curriculum

A self-taught developer curriculum refers to a structured learning path designed for individuals to acquire programming and software development skills independently, without formal education. In the video, the speaker outlines a comprehensive 12-month plan covering various topics, from basic programming concepts to advanced computer science theories. This curriculum is intended to guide viewers on what to learn and in what order, assuming a commitment of 15 to 20 hours per week.

💡Programming fundamentals

Programming fundamentals are the basic concepts and principles that form the foundation of programming, such as variables, loops, conditionals, and data types. The video emphasizes starting with these fundamentals as the first step in the curriculum, suggesting that understanding these basics is crucial before moving on to more complex topics.

💡Object-oriented programming (OOP)

Object-oriented programming is a programming paradigm that uses objects and classes to design applications and improve code reusability and scalability. In the script, OOP is introduced as a topic to focus on during the second month of the curriculum, highlighting the importance of learning about classes, objects, inheritance, and other related concepts.

💡Development environment

A development environment refers to the setting, tools, and resources used by developers to write, test, and debug code. The video mentions setting up a development environment as part of the initial learning phase, which is essential for getting comfortable with writing basic code and using essential tools for programming.

💡Data structures and algorithms

Data structures and algorithms are fundamental to computer science and software engineering. They involve organizing and manipulating data efficiently and solving problems using step-by-step processes. The video script suggests that after gaining a solid foundation in programming, learners should delve into these topics, which are critical for technical interviews and advanced programming.

💡Software engineering tools

Software engineering tools encompass a range of applications and utilities that aid in the software development process, such as version control systems, integrated development environments (IDEs), and debugging tools. The speaker recommends learning these tools as part of the curriculum to enhance productivity and code management skills.

💡Git and GitHub

Git is a version control system used for tracking changes in source code during software development, while GitHub is a web-based platform built on Git for version control and collaboration. The video encourages learning Git and GitHub to practice code versioning, collaboration, and to become familiar with the command line.

💡Advanced programming concepts

Advanced programming concepts include more complex topics such as decorators, asynchronous programming, memory management, and operating system-level interactions. The video script places these topics in the fourth month of the curriculum, indicating that a solid grasp of these concepts is necessary for deeper understanding and proficiency in programming.

💡Problem-solving skills

Problem-solving skills in the context of programming refer to the ability to analyze, reason, and develop solutions to programming challenges. The video emphasizes the importance of these skills, suggesting that practice and experience are key to becoming a great programmer and successfully tackling technical interview questions.

💡Technical interview preparation

Technical interview preparation involves learning and practicing the skills and knowledge required to perform well in job interviews for software engineering roles. The video script mentions that mastering data structures, algorithms, and having a strong foundation in programming concepts are essential for cracking tech interviews at top companies.

💡System design

System design in the context of the video refers to the process of planning and constructing systems, particularly software systems, to meet desired needs and specifications. It is mentioned as a topic to explore towards the end of the curriculum, suggesting that understanding system design principles is beneficial for more advanced or senior software engineering roles.

Highlights

The video provides a 12-month curriculum for self-taught developers to become software engineers.

The curriculum is designed for learners with 15 to 20 hours per week to dedicate to learning.

The presenter has six years of teaching and ten years of programming experience.

The curriculum includes a focus on problem-solving skills, practice, and guidance.

Scalar, the sponsor, offers a solution to enhance programming skills and prepare for tech interviews.

The first step in month one is to determine the type of programming the learner is interested in.

Learners are advised to start with the fundamentals of programming before building complex applications.

Month two focuses on learning object-oriented programming concepts.

By month three, learners should be comfortable with the basics and start working on projects.

Month four introduces advanced programming concepts such as decorators and memory management.

Learners are encouraged to explore operating system level concepts and how a computer works.

Month seven is about building good programming habits and understanding clean code.

Git and GitHub basics are recommended to be learned in month eight.

Learning a second programming language is suggested in month nine to gain perspective on different paradigms.

Data structures and algorithms are the focus in month ten, preparing learners for technical interviews.

The final months are dedicated to exploring fun projects, system design, and potentially specializing in a niche area.

The video concludes with a reminder that consistent practice is key to improving programming skills.

Transcripts

So in this video, I'm going to share with you

the ultimate self-taught developer curriculum, which will be a long

list of topics that you need to master to become a software engineer.

Now, not only will I give you this list,

I will tell you the order in which you should learn these topics

and approximately how much time I would spend on each

assuming you had between 15 to 20 hours per week to learn this stuff.

So what I've kind of done is broken this into a 12 month schedule,

saying in month one learn this, month two learn this

etc. etc..

Again, assuming that you have between 15 to 20 hours per week.

Obviously this will widely vary depending on your skill level,

how naturally this comes to you, if you have more time, less time.

I just figured it'd be nice to kind of

put it in a one year schedule and give you, you know,

where I would hope to be by each month with 15 to 20 hours per week.

So just to add a bit of credibility here,

I've been teaching programing for about six years.

I've been programing myself for about ten.

A very good understanding of what it takes

to get good at programing and the order in which you should learn specific topics.

In fact, I have a programing course programingexpert.io,

you can check it out from the link in the description

that teaches this exact curriculum pretty much.

And lastly, if you already know how to code,

you already know a lot of the topics on this list, then what I would recommend

you do is check out the sponsor of this video.

So what makes a great programmer?

Now, you may have thought about

this often, but there really is no definitive answer.

Now, if you ask me, I'd say good problem solving skills,

lots of practice and likely some other guidance.

Now, fortunately for us, Scalar, the sponsor of today's video

has a solution that can make you a great programmer

and help you crack pretty much any tech interview that you can think of.

And yes, by that I mean at companies like Microsoft Media and Google.

Now, Skyler's a tech school

that was founded by industry veterans that worked at top tier tech companies

one of them actually worked

directly with Mark Zuckerberg in the early days of Facebook

and helped to build the Messenger app and other parts of the Facebook platform.

Skyler's curriculum is built keeping in mind

the needs of tech companies vetted by those who work there currently.

And with Scalar, you get mentorship as well as dedicated interview career

support to help you along your journey Last year, they helped 2000

plus engineers get into top product based companies.

Now, mastering

problem solving data structures and system design is now only one step away.

Give scaler.

Try it by clicking the link in the description

and enrolling in a free master class

where you can learn how to master technical coding rounds at main companies.

Thanks to scalar for sponsoring this video.

So with all that said, let's dove into the beginning of the curriculum here.

We'll start at kind of month one.

So on month one,

the very first thing you need to do is determine what type of programing

you actually want to do.

And this may be hard if you've never program before,

you need to spend at least a day or two researching kind of different areas

within programing and figuring out what interests you and what you want to build.

You can always change later on

if you find that you're really bored with what you originally chose,

but you need a starting point

in a programing language that you're going to be learning.

So you need to pick, you know, do

I want to do I, do I want to do research, do and do data science?

Why am I learning to code, first of all? What interests me?

What do I want to build?

Once you know

those things, it's very easy to find languages in the specific domain.

For example, if you wanted to be a front end web

developer, you'd probably want to learn JavaScript.

You want to do more backend stuff, maybe Python, maybe go, maybe Java C++, right?

There's a bunch of different options.

So that's kind of what you need to figure out first.

Now, once you find a programing language that you want to learn,

you need to immediately go right to the fundamentals.

No building stuff, no creating complex applications.

You need to understand what is an F statement, what is A for, what is a value?

How do I add numbers together? What are different data types?

How do I print something? How do I collect console input?

All of the fundamental programing concepts.

If you want a full list, you can check out the curriculum.

I'm programing expert it's free.

You don't have to pay to view the curriculum you can go through in view

kind of what I would teach in terms of programing fundamentals.

Moving on from there, I would imagine that learning

just the fundamental tools of programing, setting up your development environment,

kind of getting comfortable writing basic code would take you about a month.

If you're putting in 15, 20 hours per week to really get good at it,

to really understand what's going on.

That's how long I think it would take the average person.

Again, some people may be much faster than that.

So once you've done that,

what I would recommend is trying to do some type of exercises,

trying to do some type of problems,

going through assessments, going through practice questions,

whatever is going to help you practice and actually be writing code

and learning this skill.

You need to do that because it's not enough to just watch the video.

You have to really understand the fundamentals

before you can go any further.

So after you nail down the fundamentals here, the next topic, which is still kind

of considered fundamentals in my book, would be object oriented programing.

So you're kind of starting month two here.

The next thing I would focus on learning is object oriented programing.

Now, this is definitely more complicated than the fundamentals,

and it may not even be necessarily offered in the programing language

that you're working in,

but you still need to learn kind of the paradigms of that

and all the different topics within for example,

you need to learn about classes and objects,

you need to learn about attributes, need to learn about methods.

You're going to have to learn about inheritance, about abstract classes,

interfaces, based classes, you know, all these different things.

Right?

There's a lot of topics within object oriented programing.

Again, if you want a full list, you can go to something

like programing expert and you can see kind of the curriculum Again,

that's for you don't have to pay to see that.

It's not what I would do in kind of month to learn object oriented programing

and then really start working on maybe some larger projects.

And I say large, nothing massive.

But where you're writing a few classes, you're having classes and objects interact

with each other.

You need to practice all of this stuff and do it in some type of format

where you're actually writing a program.

You know, you're doing stuff on your own,

maybe you're referencing solutions or StackOverflow, that's fine.

But you still need to be trying to create a majority of this program by yourself.

And kind of struggling before you just dove in to the answer book.

So that is what I would do in kind of a month.

And moving on to month three here, at this point in time,

you should be very comfortable with program.

You should know how to solve basic problems.

You should have the fundamentals down,

and hopefully you've memorized a lot of the basic syntax.

Like you don't need to refer to maybe some base code

or something like that all the time to actually get anything done.

At this point, I would really, really start working on some type of project,

some type of exercises and just continuing to practice these skills.

These are things that it doesn't matter what programing language you work in,

you're going to have to know and you're going to have to be very, very good.

So personally, I would commit probably a month

to just going through different exercises going through different problems

and really testing myself and making sure I understood

all of the concepts very, very well before going any further.

Because if you try to jump further without knowing it

it's going to be very discouraging because stuff gets even more complicated, right?

In kind of the next month that I'm going to go through.

So it's kind of month one, two, three.

Make sure you learn the basics, the fundamentals,

of a programing language,

object oriented programing, and then you do a ton of exercises

and a ton of practice.

Then you can move on to month four.

All right.

So moving on to month four here again, at this point,

you should have a very solid understanding of the basic programing.

Concepts should be comfortable

writing code and ready to kind of move on to a new topic and learn something new.

Now, this is where I'm going to recommend that you start diving into advanced

programing concepts.

Some people may disagree with me here, but I think it's a good idea

to really nail everything programing before you dove into stuff like software

engineering tools and more kind of, you know, add ons to programing.

That's what I'll call them.

So in month four, I would start looking at advanced programing concepts.

Now, some of those concepts would be things like decorators splitting your code

into different modules and different packages, learning how to run your code

from the command line, how to compile code manually, stuff like that is important.

Next, I would learn stuff like iterator generators, understand

some kind of underlying concepts in the programing language

that maybe you've been taking advantage of,

but you didn't really understand how they worked.

I would learn about asynchronous programing.

I would learn about threading and multiprocessing.

I would start looking into

memory management, understanding stuff like pointers versus references.

You may have learned that earlier.

Hopefully you did, but if you've not already at this point,

then I would try to learn topics like that,

especially if you're in a dynamically typed programing language.

You probably want to start looking at some constructs,

maybe a little bit outside of that

and just kind of exploring, you know, how do other programing languages work?

Not just the main language that I meant continuing here.

I would learn about some operating system

level concepts, which is kind of what I was discussing.

Like, how does a CPU actually work?

What is a CPU?

What's a core versus what is a thread?

What does it actually mean to run my program?

What's happening on the computer?

How what is binary?

Right, stuff like that you don't need to be a master at,

but I think you should have some perspective

on as a programmer or someone who wants to become a software engineer.

So that's what I would do in kind of month for probably month five

and six, as well as just get comfortable with these more advanced topics.

Try to dig into how a computer works, how do programs actually work,

how are they being executed?

What is a file, what is source code, what is bytecode?

Those are things you want to understand next.

Once you've done that in this kind of,

I guess, four to six month period here, your month for two months, six.

What I would do is work on harder programing problems, right?

Maybe at this point you go to

something like leak code or algal expert, you start just trying

maybe some of the easy and medium problems and seeing, okay, how do I deal with,

you know, problems I've never seen before?

Stuff that's completely new.

What is my problem solving skill?

Like, not just pure kind of coding and I guess regurgitating stuff

that you've already learned.

How do I look at a unique problem and use code to solve it?

That's a skill set that's always going to be important

and that at this point I think you start diving into.

So that's kind of what I have from month four to six.

Learn advanced programing concepts, learn operating system level concepts,

learn threading multiprocessing,

how a computer works, what is a CPU, what is a thread, what is a core?

And then work on some more

advanced problems and more difficult ones and then move on to month seven.

All right.

So at this point here, you've been programing

for about half a year approximately, if you're following the schedule, right?

And you should have learned a lot of stuff, right?

You have a lot of knowledge in your head.

It's a lot of new stuff.

Hopefully you've been applying it along the way and you've done

a lot of practice problems and you're getting good at that.

Now is where I I think you need to start looking into what is good program.

What does it mean to write a good program?

What are good programing, habits? What is clean code?

How do I not just solve the problem, but how do I solved in a more optimal way?

How do I make my code easier for other people

to read, easier for other people to add to, etc.?

This is when I think you start getting into building good programing habits

and also reading a lot of other people's code,

going to GitHub, going to StackOverflow, and just maybe spending an hour or so

whenever you want to do this, looking through some production level code,

understanding how code bases are kind of laid out, how do they organize code?

What happens when I have, you know, 10,000 code files?

How do those kind of get laid out?

Where do I put those? Again, you're not going to be a master at this.

Need to probably learn this on a job, but this is something that I would start

trying to learn good programing habits, learn

what is clean code, what is good code, how do I write this in a more optimal way?

There's a lot of patterns you can learn that are like that.

And again, reading and kind of reviewing a lot of other people's code.

Now continuing here,

another thing I would do is I would start learning Git and GitHub,

just the basics, nothing crazy, but I would start practicing committing

everything that I read in terms of code to my GitHub repository.

I would start seeing, Okay, you know what happens if I have a conflict?

What is a branch?

I'll start learning these basic GitHub kind of terms

and getting comfortable using the command line.

How do I copy a file? How do I move a file?

Maybe you don't always have to touch your mouse.

Now you can do a lot of stuff with commands that you know,

like Bash commands, Windows commands, you know, Mac commands, terminal commands,

whatever you want to learn.

But I would get, you know, familiar with some of those commands and understand

some of these software engineering tools, which is what I call them.

All right, so now we're moving on to month eight.

At this point, you should be good at programing.

You should know the basics of getting GitHub.

Maybe you have some bash commands under your belt.

You're starting to understand

what is clean code, what is good code, how do I write better code?

How do I not just solve the problem?

How do I solve the problem?

Well, now this is the point where I think you need to jump into

another programing language.

You don't need to become a master. You don't need to be an absolute pro.

But I think you should study and look at another language

and ideally one that is different than the programing language

then you currently know.

What I mean by that is pick something that is fairly different.

Maybe you go from a dynamically typed language to a statically typed language.

You go from something

that's a very high level language and maybe a lower level language.

Maybe you try learning something like C++ or C, something that's considered harder

than maybe a Python or a JavaScript.

This is going to give you a really good perspective

for different kind of programing paradigms,

the way that different programing languages work, and the fact

that there's always the best tool for the job right?

When you have two different programing languages,

one is not better than the other, but one is better at something than the other.

One is just like the other.

One has its pros and has its cons or places

where you would use it in places where you wouldn't use it.

And that's an important perspective to build and learning another

programing language is always something very, very valuable,

especially because a lot of the stuff you already know is going to carry over.

Then you're going to learn about a little nuances, tweaks, and,

you know, maybe this one's faster or slower. You're going to just discover

a lot of things by jumping into another language.

So that's what I would do here. No need to be master.

So that's what I would focus on. Another programing language.

All right, so now we're nearing kind of the end of the journey here.

You've been programing for a long time.

Hopefully you're getting good hopefully the basics are now kind of nailed down.

You know, everything.

That's totally fine.

You feel comfortable solving most problems

in the programing language that you originally chose.

You've just learned another one.

You know, you've got some basics and not now.

Unfortunately, it's time to learn

some of the hard stuff that everyone hates learning now is the reason I left this

till the end, because this is a fairly discouraging section for a lot of people.

But this is what I would start

looking into the dreaded data structures and algorithms.

I would also start potentially looking at mathematics related to programing,

maybe just getting some perspective of what

like a proof looks like for an algorithm,

looking at something like discrete mathematics or linear algebra.

You don't have to do that.

I'm just saying maybe that's something you want to just take a look at.

Have an appreciation for how complex some computer science proofs

and topics can really be.

I would also maybe start considering looking into computer architecture

that's, you know, what is it?

Transistor, what are different gates?

What's an end gate or gate nor gate?

How is, you know, a CPU design, stuff like that?

Again, you don't need to do this, but that's something

that I would have learned at my computer science degree

and that I'm very thankful that I did learn.

So I'm kind of just recommending it here.

But overall, you're going to be wanting

to look at a lot more theory related to computer science.

So data structures and algorithms,

time complex, the big O notation, big theta, big Omega,

how you determine the running time of an algorithm how you write

specific algorithms,

sorting algorithms, searching algorithms, what is a heap, what is a binary tree?

What is a big tree?

There's a lot of stuff like that that will come up in an interview scenario.

So if you're trying to prepare for a technical interview,

this is something you're going

to have to kind of already know before going into that.

So I would spend two months probably on this type of stuff, right?

A month, nine to ten, I guess.

And then I would move on to next up.

All right, so let's say an hour on month 11 or 12.

I can't really keep track of exactly what I've said at this point.

Let's say you're near the end of your journey.

All right. You did the data structures and algorithms.

You have the foundation in that.

Maybe you dabbled in a little bit of math.

You looked at some computer architecture.

Now is the point where I would start looking at maybe some more fun stuff.

Maybe you would look at some modules

and packages, like maybe if you're working in Python,

you start creating a website with Python,

or you start kind of applying your knowledge into building something

that's fun, that's cool, a project that you want to work on

and that you could maybe continue over a month or two months

and then maybe you're going to add your resume or something like that, right?

So dabbling into that kind of stuff.

So external packages, external modules, stuff

that's been built for you to build with others in that.

I would also start potentially looking at something like system design.

Now, this is something that you would

really not do until you're like a senior software engineer,

but it's never a bad idea to get, again, a very minimal perspective of all of these

different topics, just so that if you ever were asked about something like this,

you'd at least have some idea what the what the question was.

Right?

So when I say system design,

maybe you start thinking about, hey, you know, I know how to code now

how the heck did they make something like Netflix?

What is involved in that in terms of like a dev ops thing?

How many servers do they have how optimized is their delivery mechanism

have to be? How are they serving content that quickly?

Maybe that's something

you just want to look into for a few days and kind of research a little bit

other than that, you can start learning about some design patterns so you know,

common ways to kind of structure programs and start looking into

maybe some specific things within your programing.

Niche that you're into.

Maybe you're really into

artificial intelligence, maybe you're really into data science stuff.

Maybe you start learning some specific tools within that area

and kind of getting a bit of a specialty, if that makes sense.

That's what I would do here.

And then of course, always be practicing.

That's really how you're going to get better.

So I think with that said, it's going to wrap up this video again.

All of this pretty much with the exception of a few topics,

especially like in the later sections is taught.

I'm programing expert.

I don't want this to just come across as a huge add for that product.

But I designed that with pretty much all of what I just described in

mind for you to be the best possible place to learn how to code.

So if you're interested, check it out from the LinkedIn description.

Use discount code. Tim, I hope you enjoyed the video.

If you did leave it like good luck in your programing journey.

I'll see you in the next one.