Things I wish I knew before being a Junior Dev: Learning

From my first post where I was sharing things I wish I knew before beginning my internship, I had expressed the 6 most important things a junior must know and use to scale their profile and grow their skill set as a developer.

Here we will discuss how to get around learning a tool or language while using the documentation or using a textbook.

Learning how to learn:

With this I want to start by saying it's important to check out the four styles of learning and also do self-introspection to see which one works best for you. So how about you look at your past learning achievements and see which process of learning you have done before that gave you the best result or even how you can improve it.

• Create a flexible pattern of learning that you will use for grasping concepts and understanding material effective and efficiently but base it on your preferred learning style.

• Make a habit of setting miles stones for your learning code. Look at the different subjects relating to that tool or language, the different uses & try to learn them individually, and write a summary of your understanding.

• Another achieve your milestones is to make small programs with what you have learned or code along with your tutorial video or the documentation you looking at and we will discuss that later also.

• If you don’t manage to finish a course or finish a tool tutorial, make a note to put bookmark where you left off and come back to finish it off later, it's a good habit to start and finish things.

Have a reason to learn that tool:

Whatever tool you working on let it have value at the beginning of your learning, because learning it without a purpose you will burn out of boredom or you will waste your time gaining a skill you won't be happy working with.

• Look at what your employer needs, or look at the projects you intend to build or the company you want to work for and learn skills and technologies so that your target market sees value in you.

• A good example is, if I intend to work for Designative, I need to look at their LinkedIn and see what types of skills they need, then I will start learning those and staying up to date with who else needs those skills. Then when I start I know my goals are to master this tool enough to maintain the type of software Designative uses.

Which resource do I use to learn?

A huge part of learning is mostly you trusting the validity of whatever tool or method you use, So here I am just showing examples of the content which is available out there and I hope you can go out and search for the material that works for you or a content creator that resonates with you.

Books 'my fave!!' - PDFDrive

Online courses for programming like Udemy & Sololearn

Coding games - Codewars & codearena

You tube videos - WebDevSimplify

Blogs - Dev.to & Github Blog

• These are just examples of good blogs, video creators and also games that will help you learn and grow. Challenges - Geek4Geeks

  How do you learn code:

• So what's important when learning a library, framework or a programming language is to be able to use it and also understand the fundamentals of how it works and how you can use it on a high level.

• So you want to be able to be efficient with your learning process and also effective with your information consumption. This means you have to learn to understand the tool and within that same go, you aim at being able to use it effectively after your learning process.

• You also want to practice the different design patterns and tools available there to see how it behaves and the bugs that are possible with your logic and consumption.

• You also want to have something to satisfy yourself after learning, and so if you create something while you learn you will have something to be happy you achieved, something more or less tangible.

Example of using documentation:

We have a very good example in the video I explain using the python documentation to learn how to use the tkinter library

• So in this video I show how following the instruction in the documentation and also see how you will get stuck and start debugging. Link the video

• When using the docs to learn something you want to first install it properly and set up your environment.

• Sometimes you have to download the tool or library like bootstrap and you will use it on your machine.

But then if you don’t intend to use it locally you can also used the CDN like the following image, So you copy that link to the CSS online and paste it into your project or your HTML.

This image shows the download for the node installer.

• For situations where you have a package manager line node js already installed, you would have to use the npm install command to install things, for example installing a tailwind library: In this following image, we see the installation of the tailwind CSS CLI,

In this instance we see how to install using postcss

In this instance we can see how to install bootstrap instead of downloading it.

In the following image we can see what's possible, we can see more guidance on how to config your environment for using the tool and also how to start out, and so you can see the docs will help you get started.

• So the docs are out there for you to use, go get it friend!!

How to stay at the top of your game:

• Creating code alone or just for your own pleasure can get uninspiring and boring, I suggest you involve other developers in your growth. Try learning the tool together, do some buddy programming, or even build the same thing using different logic.

• Talk to your seniors and hear what they think about what you have done thus far and how you could improve your work or your code.

• This way you can also have a code review to see how much you understand and how you can apply some standards to your projects.

• Also describe the bugs you facing and ask for possible fixes for the problem you face, this can greatly expose you to different problem-solving methods.

• Ask for a chance to work on projects that relate to what you have learned so your skills can be tested and can grow.

• Don’t be satisfied by building a hello world program with each tool you learn then forget about it, go deeper, understand all the fundamentals, check how they are applied in different instances, and solve problems for other people on that tool. You Have To Be Pro-Active.

Example of using documentation:

We have a very good example in the video I explain using the python documentation to learn how to use the Tkinter library

• So in this video, I show how to follow the instruction in the documentation and also see how you will get stuck and start debugging.

  Check out how python Documentation

The Goal of learning:

• Its smart to practice iterative learning, learning to reach a small goal, then set a bigger or much in-depth one then do it again, then keep iterating till your goal becomes mastering.

• Firstly its always important to be clear that you learning to understand and be effective when using a tool, to be able to read someone’s code or create a beginning project that works.

• Second you want to learn to use best practices and understand higher-level concepts or patterns above the fundamentals and practice those on your beginning project.

• Third you want to build learn some of the concepts of design patterns used for different scenarios with that tool and understand those and their bugs.

• I know you have an app idea lol, I suggest you take this time to build that project and apply those fundamentals and their high-level counterparts.

• We can also use other channels of learning like this react docs video where you have a collection of videos with good quality information which is like a translation of the documentation as a video.

Let me hear your ideas on how we can improve this process for better learning. I am ready to learn more.