Forem: Precious adeyinka

How To Become A Serial Programmer In 6 Easy Steps

Precious adeyinka — Sat, 28 Aug 2021 19:31:55 +0000

Wait What, Serial Who?

Yeah, I know right, not the best decision for an article title, but it was the only thing that inspired me to write so, I hope it will make more sense to you eventually, than focusing on how crappy the title might sound.

But whichever way, I haven't really heard this word before or even researched if it existed, but the idea is that you can learn any programming language you want to learn as long as you have a deep understanding of the fundamental concepts from your first language.

So, for a proper definition if you care, I say a serial programmer in my opinion is a programmer that sort of have a good proficiency level in several programming languages like; Ruby, Python, Javascript, Java et cetera.

If you fancy quotes, here is one:

"Knowledge is transferable"

Who said that? I don't know.

Alright, with that out of the way let's dive in!

Step 1

Decide the programming language you want to learn

Well, this as you might have guessed is where you have the desire to expand your knowledge and attempt learning a new language. Maybe you are a JavaScript guy, and you want to vibe with python also, well this is for you, keep reading.

Step 2

Focus on a problem (maybe from personal or external experiences)

When, you have decided upon a new language or tech stack, then you have to find a problem, you have a lot of them I know, make a choice from all your problems, say you always have to manually check duplications in a data entry job you are doing somewhere for passive income, decide to automate the boring task by learning python and implementing that knowledge.

Step 3

Develop a solution to this problem (brainstorming)

Oh you're doing great, almost there! Now you have a language and a problem, it is time to think of a way out of that hell you're in. So, what do you think could have been done better, what can be done now, if you have that answer, and you know it is very possible and achievable, then you can make a couple of solutions and choose which one works best for your own case, and maybe that is why you have to choose a subtle problem, like I said, could be a productivity app or music player or whatever.

Step 4

Build out the product or service

Congratulations you are now an LPS(Language-Problem-Solution) expert. So, you have a language you want to learn, you have a problem or challenge, and you have a solution, and somehow it should be implemented.

Pause, this is the tricky part, a lot of people go in head start to the docs and get immersed and bury themselves in the docs for days, even months. Now, that has it's benefits, but the world is not waiting for you or something, so you got to fast track right, and watching hours of YouTube will not ordinarily help a lot, or maybe just reading hundreds of articles. What you can do is instead of learning so many concepts about the new language in isolation, I suggest that since you have a problem at hand, you should direct your attention to learning the particular concepts from the language that can help to implement a solution for the problem. Doing it this way, has proven to be very effective, because you will learn a lot from the process of researching and implementing, and at the end of your learning journey you have a product to show off, how cool?

Step 5

Launch the product or service and write about it

This is the part where you make the solution public, and see if others have similar problems and find your product or service useful, and then talk about what you have done and what you have learnt also. This is a good way to retain information and also document your experiences, and trust me when you need it again, you can get back to it however you want to consume the information.

So you are not only writing, but you are also taking a responsibility of teaching others by merely sharing your experiences, that's massive.

Step 6

Repeat Step 1 to 6 for a different problem or for a different language

Ok...ay, I hope you have been following to till this point, this wraps up the serial thingy, and umm yeah just repeat it again and again and again, you will be a badass in no time.

Thank you for reading, and I will talk to you in my next article.

Cheers!

Memoization Demystified in 6 minutes

Precious adeyinka — Fri, 06 Aug 2021 13:06:16 +0000

Background

Do you remember how we used to play Nintendo games as kids, and did you ever played Need for speed video games. Boy! I don't know what you played if you didn't played that game, and can you remember how you try to boost your racing speed by the push of a button to apply some nitro super powers? Yeahhh, I know you are having memories already, good old days huh!

Anyways, it is pretty much the same concepts applied in programming, but just in a different context, and in this article I aim to explain the relationship between nitrospeeding concept from the video game and memoization for your computer programs.

When we write code and build applications, we often write functions that tend to perform some sort of computations, and those computations could be very expensive, in terms of space (as in the amount of memory needed by your program to execute) and time (as in the duration it takes for your program to execute) complexity.

This can affect the performance of your application, and as such, you might loose your customers, some money, as a result or even worse. So, what if there is a way to make those slow performing processes that makes your application lack some Nitro Speed faster and better?

Let's do this thing!

What is Memoization?

That is when MEMOIZATION gains the spotlight, because it essentially aims to solve the issues with performance for the most. When your application slows down, it might be because of a particular process running that causes the delay to affect the entire app, and when we build software's we tend to use functions, because they make our programs reusable and modular. So, maybe you have a function that performs some kind of API calls or complex calculations that requires a lot of space and time to execute, then what you can do to prevent such function from affecting your application is to memoize the function, and that basically means that since the function will be receiving some inputs, and producing some results, then why not sort of remember the values of each input, so that whenever you need to perform a future action that depends on the values from the previous computations with already know inputs, then your function could just remember them and use them again easily rather than have to recalculate them all over again, and doing so will tremendously improve the speed and efficiency of your programs.

Essentially, think of memoization as a type of caching (where caching generally refers to storage techniques adopted, when you intend to reuse a resource in the future) where you memorize the values of known input, and should they be needed in the future, we could remember their outcomes, rather than calculate them again and again and again, which is a very tedious process and time consuming one also.

And that ladies and gentlemen is Memoization

What can I memoize?

You can memoize essentially, almost all types of function, but should you actually memoize all functions? and the abrupt answer is no don't.

You can memoize :

Pure functions (a pure function essential is a function that returns the exact same value for the exact same input everytime)
Functions with limited input range but repeatedly occuring
Functions that performs complex computations with repeated values, and also some API calls that are happening too frequent, but speaking of API calls, make sure to do a background check, because your browser is most likely using HTTP CACHING already to cache your accessed URLs in the browser.

Anything, aside from this, just be reasonable about it, and carefully think of the impact it might cause and the idea in principle for your applications.

What is the catch?

While there are a lot of useful articles online, explaining memoization, I often don't read about the side effects of applying this approach in your programs. So, in order to make that clear, I would like to inform you that memoization does a great job in terms of performance for your programs, but it does so in a trade for memory consumption, because you will need a lot of memory to store the previously computed values, and depending on the size and throughput of your transactions or computations, the variation in the amount of memory consumed will be reflected accordingly. Hence, keep that in mind when using this approach.

An Example

Enough talking, let's see some actions. And in this example, I will, show you how to create a simple greeter function that uses memoization to remember a previous user and displays a different message accordingly, and I am choosing this example just to demonstrate some really subtle instance, that is not all numerical and requires some computations like; fibonacci, squaring, summing, factorial, and just to mention a few, because you will see a lot of these examples online, but I just also want you to see a different use case and that you could apply the concept to pretty much any kind of function you wish, you can be really creative about it, so let's see some action.

const greet = () => {
    let users = {}

    return (name) => {
        if (name in users) {
            let message = name + ', you already seem to know your way around, please feel free to explore!'
            users[name] = message
            return message
        }
        else {
            let message = 'Hello ' + name + ', it looks like you are new here, let\'s get you all setup shall we.'
            users[name] = message
            return message
        }
    }
}

let greeter = greet()
console.log(greeter('Dave')); // Hello Dave, it looks like you are new here, let's get you all setup shall we.
console.log(greeter('Dave')); // Dave, you already seem to know your way around, please feel free to explore!
console.log(greeter('Precious')); // Hello Precious, it looks like you are new here, let's get you all setup shall we.

Breakdown

Here in this example, you can see that we have a function that returns another function, which is something called a closure and it is important in order to make the function able to remember the values on consequent executions, unless this, it will just start a new execution every time sort of.

Also inside the function, there is a variable, users, that stores the results of known inputs and values, that is like the cache(storage) for remembering the stored values.

The returned function takes a parameter name, and it uses a conditional to check if the name parameter is already stored in the cache, and if it is, it returns a different message and also updates the message in the storage accordingly, so that on future calls, it will return the newly stored message, and if the first condition fails, then the else block will make a new message for the user and store that in the cache(as in the variable users) and the displays the message to the user also.

And when we called the function the first time with dave, we get a welcoming sort of message, and when we called the function again with the same argument dave, we get a more friendly and familiar message instead, and when we do the same thing for a new argument, we get the process happening again.

It is important to note that without memoization used here, it will not be that easy to achieve this functionality, it is possible yes, but not what you want to do, it will require more lines of code and logic to get it to work perfectly, so save yourself some headaches really.

What next?

Well, now that you now know what memozation is and how it can be used and not used, you can take more control of the speed of your applications and apply some nitrospeed to your programs. Aside from this, there are some concepts and keywords that might be new to you, so do well to check them out too, in order to make some sense out of this explanation. I don't want to suggest, just feel free to explore, if you do so, you will find out something I don't know haha, so maybe a quick google search can deliver a plethora of resources to you really.

A few of them maybe:

-Closure
-Functional Programming
-HTTP Caching

Whatever I leave out, also include them for your own good.

Alright that is everything, thank you for reading, see you in the next article.

Happy coding!

How To Become Better At Problem Solving

Precious adeyinka — Sat, 04 Apr 2020 01:31:22 +0000

If you expect to hear something else rather than, GO FREAKING SOLVE SOME PROBLEMS!!!

Sorry, I yelled at you :) Ahem! Trust you didn't see that coming haha :).

TL;DR But seriously you guys, the only way to get better at Problem Solving is to solve more problems. I mean, give it an attempt and get stuck intentionally sometimes, break things, learn new ideas, discover new passions and all of that.

“We can not solve our problems with the same level of thinking that created them.”
-- Albert Einstein

Errhmm, you know what, I think, Einstien is literally correct.
You have to learn the Act Of Asking from those who know better and learn new ideas by so doing.

Ex: https://www.stackoverflow.com - half of the Programming World population knows Stack Overflow lol (It is like our own Modern Day, Hogwarts in the Movie Harry Potter), and just in case you don't know yet, well now you do and you can thank me later.

“ A problem is a chance for you to do your best.”
--Duke Ellington

Here is another one from Duke, if you think you will get better at solving problems without embracing errors and happy at "Uncaught Errors" error screens, sorry to disappoint you, but you might never get it right.

WHAT CAN YOU DO?
I thought you would never ask, silly!
The first step is to find a problem, there are tons of sites offering those services nowadays, a little google search and "Open Sesame" will do the trick right hehe :).

I personally find https://exercism.io really helpful (aside from the challenges and tasks, there are mentors that will help you get unstuck when you need to be, JUST ASK!).

Your second step should be to attempt the problem yourself, try and research, it will improve your discovery and research skills to be sincere.

How much time should you spend researching? I will leave that bit for you to decide on, nevertheless, there is a very interesting thread right here on DEV.to about this topic, so help yourself lol (https://dev.to/ben/how-much-time-should-you-spend-looking-something-up-before-asking-a-question-3i5m)

You can already guess the third step, ASK FOR HELP! (you gotta find somewhere to inscribe your SOS signal).

You should be able to describe clearly your problems, and what you have tried to do so far and what you want to be done to whoever you are asking or whatever platform you are asking from.

Conclusion:

I am sure you didn't expect this one, but I personally find this method an Ultimate Finishing step.

Documentation:

When I eventually solve a problem, I create a video explaining to an invisible user how to solve the same problem, and then I find somewhere to host it in the cloud. This will help me to remember how I solve a problem the next time I need it. I use Youtube sometimes because it will solve a lot of problems for those who will need it, and also has in it the potential to Generate income once people are looking for a similar solution like a hell lot right!
That is not a goal though but on a lighter note, (Passive Income is what they call it).

Well, I guess that is everything you need to hear from me for now.

Now, of course, this is a deep topic, and there are more ends to this, but you will discover that as you progress in your journey I am sure of that.
Good Luck!

OHH, one more thing though, please DON'T BREAK THE INTERNET, FIX IT!! :)

Note: I might just make a very elaborate video on this topic very soon and invite some people over to share some thoughts, just barely a thought in my mind though, I will let you know of any development.

HOW TO STAY MOTIVATED AS A PROGRAMMER IN 2020

Precious adeyinka — Sat, 25 Jan 2020 22:43:39 +0000

Image Credit: https://www.google.com/url?sa=i&url=https%3A%2F%2Fblog.simonsays.ai%2Fhow-our-emotions-affect-our-memories-permanence-part-2-7b8b9f6b5c14&psig=AOvVaw2DpganVYTNWiJiiVe0P51x&ust=1580077629102000&source=images&cd=vfe&ved=0CAMQjB1qFwoTCPiZ5cnln-cCFQAAAAAdAAAAABAD

'Progress is progress no matter how small'

The year has just begun, and It's okay to feel you are not making progress sometimes, we all do, in fact, I do the most, and that is the reason I have been holding back from blogging (Impostors Syndrome). But luckily I always find a reason to keep going on and on non-stop. So, I thought if you are in this position, this might be for you.

Let's talk!

Did you read the quote up there, 'Progress is progress no matter how small', exactly that is what it is.!

It happens to be very easy to feel frustrated and overwhelmed, especially when it comes to programming, because of so many reasons I can't possibly list out here. I mean the wealth of resources available on the net nowadays, the tech stacks, name it, there are just so many and it takes very little effort to become frustrated and give up. But the good news is, I might have discovered the best way to remain motivated while learning to become a programmer.

One of the mistakes I made when starting to learn programming was that I was learning too much and so frequently that I wanted to know it all and now. Where did it get me? Far! Yes far enough to make me aware of a little here and there. But that wasn't enough or will I say the best way to go about it.

The side effect:

Image Credit: https://www.google.com/url?sa=i&url=https%3A%2F%2Fwww.gulfbreezerecovery.com%2Frecognizing-substance-abuse-symptoms%2Fside-effects-2%2F&psig=AOvVaw1ojydPQGqZcX-UXwqTZ6am&ust=1580078825746000&source=images&cd=vfe&ved=0CAMQjB1qFwoTCMiNyYHqn-cCFQAAAAAdAAAAABAO

Because I was reading just too much and too frequently, it was so easy to forget things a lot and get overwhelmed because of so many things to know and learn. I thought I was supposed to know everything to become worthy. But I was wrong and now I realize the mistakes I made. That term is called (TUTORIAL PURGATORY) - Now you are stuck with youtube videos, Udemy course, skillshare, google searching, hoarding tabs, uh oh!! now you can see yourself, I gotcha!!!

And now for you, as a beginner Programmer, don't make that mistake FOCUSING ON SYNTAX, you heard me right? Yes! Most beginner programmers focus on syntax, and that is why they all write calculators or HTML forms as their first real project. haha Just kidding! I did that too lol.

But the idea is programming is an art, and the real essence is to solve problems, real-world problems.

Memorize this:

Image Credit: https://www.google.com/url?sa=i&url=https%3A%2F%2Fblog.simonsays.ai%2Fhow-our-emotions-affect-our-memories-permanence-part-2-7b8b9f6b5c14&psig=AOvVaw2DpganVYTNWiJiiVe0P51x&ust=1580077629102000&source=images&cd=vfe&ved=0CAMQjB1qFwoTCPiZ5cnln-cCFQAAAAAdAAAAABAD

PROBLEM-SOLVING, not SYNTAX MEMORIZING - did you get that now?

Alright, on to the good stuff, I know you are itching to hear it already, alrighty!

I have a few little tasks that you have to sacrifice though.
Here we go!

FIVE THINGS TO FOREVER REMAIN MOTIVATED IN WHATEVER YOU ARE LEARNING (not just programming):

1

Image Credit: https://www.google.com/url?sa=i&url=https%3A%2F%2Fgifer.com%2Fen%2F7BBQ&psig=AOvVaw1rrYqhTYPyQDXVy8NvtMP8&ust=1580077807322000&source=images&cd=vfe&ved=0CAMQjB1qFwoTCMC3h5rmn-cCFQAAAAAdAAAAABAD

You are probably tired of hearing this one - HAVE A SOLID PLAN (That means have the end goal in mind) - Someone would say, how do I plan when I don't even know enough about it yet! DO YOUR HOMEWORK!!! Go ahead and research... Having your end goal in mind is very crucial, and it will save you a lot of stress from learning a bit of this and that without anything to show off for.

Let's bring it home a bit, if you want a career in programming and you want to apply for a job, the first thing you need to be able to provide is the proof that you are the person for the job, what do I mean? Show Your Work, where is your Home Work, what have you done or been doing, what things did you break? (That basically means Do you have a portfolio, where are your project, what are you going to show the employer?)

I feel bad writing this article at this point because I was a victim of this for a long time, I knew a lot of things, but I didn't know it wasn't enough until I have to put it all together into an App for an employer to believe, get the idea?

So, you want to learn to program, be it Web or Mobile Apps, make sure you have an end goal in mind, be it a mobile app that helps you solve your math assignments, or reminds you when to wake up, or keep track of your life, a personal portfolio Web App or whatever, just have something has an end goal to build at the end of the day?

2

Image Credits: https://www.google.com/url?sa=i&url=https%3A%2F%2Fwww.pinterest.com%2Fpin%2F498632989970450281%2F&psig=AOvVaw2c1xa92vwcOpBvd8jv2zwM&ust=1580077378084000&source=images&cd=vfe&ved=0CAMQjB1qFwoTCJiAwt7kn-cCFQAAAAAdAAAAABAD

STAY FOCUSED - A lot of people miss it here, there are so many things distracting you, your friends might tell you PHP is lame, JAVA is for babies, whatever don't listen to them. Even the internet is your number one source of distraction, you are on youtube someone somewhere is raining ads on your screen, and it goes like "UDEMY 70% Discount become a LISP programmer in 7 days" nonsense! It's a trap, I am telling you because I know, don't click that link. I can say this because I know, I have over 1000 subscriptions for different things and it is bad now I am stuck because I feel I need to finish it all and know it all and get all the certificates in the world. NO NO NO!

Memorize this:

A step at a time, little progress every day makes a lot of difference at the end of the day

Little rain droplets, will soon flood your house if you don't stop it

So, number 2 is to be focused on what you want to do, you want to build your portfolio, do it one day at a time, remember I said programming is Problem-Solving right? Now, this is your/the/a problem, and you are learning the ropes, what do you do? Now, you understand the problem clearly, you need a portfolio website, alright, how can you do that, you don't know? research! (Google, youtube) Then create a sprint, a workflow, a timeline to follow through with every day till the deadline, yes deadlines are really important they help you quantify your success, and have measurable goals. You know the Number Crunching game thingy right?

Don't kill yourself, achieve something little you can do every day, like start with the wireframe, design the layout, have an end goal in mind, remember they are interconnected and also do your research, see what other people have done because the truth is we are all good copiers, yup you heard that right! The earlier you know that the better. And then proceed on to something slightly hard, like umm the header and the navigation menus, don't worry there is the documentation for these things.

3

Image Credit: https://www.google.com/url?sa=i&url=https%3A%2F%2Fimgur.com%2Fgallery%2FtYbgIYH&psig=AOvVaw1ETkyCDSmmyKr2ieAtgTCd&ust=1580077989471000&source=images&cd=vfe&ved=0CAMQjB1qFwoTCMCMpfbmn-cCFQAAAAAdAAAAABAD

Next up, JOIN A COMMUNITY - Yes, that sense of belonging somewhere will take you a long way than being a solo programmer, you will learn, better, faster and it will also teach you the habit of working in a team/community of like-minded people, and you will also find similar learners like you and you can ask and answer questions, I mean there are so many benefits of belonging to a community. Now, don't just be the one hiding and secretly learning from the Q&As, PARTICIPATE! it has a lot of health benefits too lol.

Don't be afraid to ask for help, if you don't know how? learn it! After a few bullies from Stack Overflow, you will learn, lol I can remember my very first question like it was yesterday Aha! Talk for another day lol.

4

Image Credit: https://www.google.com/url?sa=i&url=https%3A%2F%2Fwww.tangentsolutions.co.za%2Fapproach%2Fopen-source%2F&psig=AOvVaw2ZV7v3rJHu5w-D9dPmcMT5&ust=1580078098083000&source=images&cd=vfe&ved=0CAMQjB1qFwoTCJDczafnn-cCFQAAAAAdAAAAABAJ

CONTRIBUTE TO OPEN SOURCE - Very important, giving back to the community that made you huh, it is like a way of contributing and gaining recognition at the same time (2 in 1), you don't have to be a PRO to do this. One thing with open source is that it will grant you the experience and the knowledge you will need for your next big project or job interview. You will learn a lot faster, from the community and other people on what most matters to you, like how people build software from scratch and all that, kinda stuff. Guess what?

FREE!!!

One key thing though, be smart and follow people that look like they know what they are doing, follow them everywhere, and HIT that notification button to get every single tweet and stories and highlight, just follow up on these guys alright.

5

Image Credit: https://www.google.com/url?sa=i&url=https%3A%2F%2Fgiphy.com%2Fgifs%2F26n6IAaJLKmeO3EDC&psig=AOvVaw2gpv7MOkK3j3RC7eP0zoBE&ust=1580078267107000&source=images&cd=vfe&ved=0CAMQjB1qFwoTCIjP9fjnn-cCFQAAAAAdAAAAABAD

REPEAT - Have you gotten to this point? CONGRATULATIONS!!!
Now make sure you repeat the process, I never said it is a one-off. So, go ahead and do it all over again and again and again and again, I will keep saying again if you don't stop me really!

Alrighty, so the idea is to keep at it, right now I am somewhere in the world, righting my wrongs, don't make the same mistakes I made alright, learn better, faster and smarter. I have a word for you though, this year two things are really important, POSITIONING AND NETWORKING, I just wrote in caps. Do you know what that means? Work Smart & Not Hard, because it is easy to work hard. That's why they pay the CEOs big time.

Conclusion:

Image Credit: https://www.google.com/url?sa=i&url=https%3A%2F%2Fgfycat.com%2Fviciousthankfulkentrosaurus&psig=AOvVaw0Qoi-JQbWOrgHCohV327eg&ust=1580078372762000&source=images&cd=vfe&ved=0CAMQjB1qFwoTCLCKrq3on-cCFQAAAAAdAAAAABAJ

One last thing I should have mentioned is BALANCE - strike a balance in your life, everything does not revolve around programming, trust me I can say this anywhere, nobody likes programming more than I do, but you need to do other things too, strike the balance in your lifestyle, I can't tell you what to do as the case may be different with everyone, so manage your time properly, you can be cool as a programmer, yup, take selfies, go to the gym, take a walk, eat healthily, make friends, take a shit, ahahahhahah. who doesn't!
Do anything else, just make sure to STRIKE THE BALANCE!

At this point, if you are still feeling unworthy, PAUSE AND THINK - I want you to sincerely compare yourself from when you were about to read this article and Now that you are at this point, you don't know it, but I am sure you have gained one or two key points already. And if you haven't I think you should give yourself a little bit of time and read this article again, better still find yourself a mentor, I mean real offline mentor. Now, you know what to do!

So, there you go, now take a FIVE from the FIVE MOST IMPORTANT SKILLS TO KEEP YOU MOTIVATED in 2020, and make sure to kick asses okay, you are the BOSS, ain't nobody going to tell you that, you tell yourself.

You are now a FREEMAN!
say NO to TUTORIAL PURGATORY and say yes to PROBLEM-SOLVING - LEARN - BUILD - DEPLOY (LBD).

Spoiler ALert: This article is not an intense discussion on some of the topics I made mention of, and you can grow your knowledge about this things by making research on the internet. That been said, feel free to reach out to me anytime on social media.

I hope I have been able to help someone out there, till next time, PEACE OUT!!!...

HOW TO CREATE A CUSTOM PROGRESS BAR

Precious adeyinka — Sat, 18 Jan 2020 07:57:11 +0000

There wasn't a native way to create progress bars out the box with HTML, not until the HTML5 specification was released and new elements, Modern components and APIs was bundled in.

Before that, programmers have discovered several beautiful hacks to this problem, and today I will be showing you a very common hack also using purely div elements, a few CSS rules and javascript for the interactive animation.

How does it work?

This article is broken into 3 stages:

The HTML:

This section defines the structure for the elements on the page.
The HTML consists of 3 parent elements.

The first element is a div that defines a container for the percentage value of the progress bar, another option is to make this appear inside the progress bar itself.

The second element is also a div (but a super div), which is where the progress bar is housed. It consists of 2 div elements in total. The first one is the bar container and the inner one is the bar itself.

The third element is a button element, that we will use to increment the progress bar by 10 percent(10%) on every click.

The CSS:

This section defines the presentation and stylize the HTML elements.
The code itself is commented and there is really nothing much to say here if you already know how to read CSS just do your thing!

The Javascript:

The javascript is a 14 lines long code base and all it does is to fetch elements from the DOM and attach an event listener to the button element, this will, in turn, add a 10% increase to the bar element every time the button is clicked. It also includes a condition that will reset the bar width to 0% when the count reaches 100%. Ohh! and then it updates the text component with the current percentage value.

Just before I forget, of what use is an article like this without a demo, so here you go:

Disclaimer: This post wasn't intended to anger anyone, if you are a PRO, you are reading the wrong article, this is for the beginners, so do a good thing by sharing. Thank you!

Ohh Boy!!! Yet Another Feature, I think I am going to explode...!!!

Precious adeyinka — Fri, 05 Apr 2019 22:35:59 +0000

Yes, that’s what we all do.

Is it bad? No!

Is it good? Maybe!

As a developer or as anything the moment you shift careers? One of the things that happens under the hood is that you are signing up to be a life long learner and self developer... Yes you heard that right.

We have alot of developers title, but many times people forget this single developer title out every time :

.Self Developer

When you hear about new technologies or get a notification update for a new feature log on your favourite development environment ?

Don’t freak out...!!!

Relax you don’t have to learn everything.

"One thing I have learnt over time is, learn as you implement, don’t learn before you implement"

Okay that didn’t sound too fancy. But the idea is: Don’t task yourself with learning everything. You don’t have to know it all, you can learn a new idea or concept only when you need to use it, like when you really need it, and then apply.

Don’t disagree with me just yet, I have my reasons.

Reason is because no matter how brilliant you are, this is what happens to everyone and everything everytime:

Energy unused is lost.
Vitality unused diminishes
A day unnplanned is lost
You can’t keep time, you can manage time though, that’s where the perfection lies.

5.You should become a master at learning and practicing most of all..

This is just a few points from the universal registry of points...

Another thing is alot of people say read alot. Now I don’t have issues with that, but what I have issue with is, the concept, because it’s not complete.

"What is reading without practice?"

The full sentence should be:

" Read alot more and practice twice as that. "

Now that’s more like it!!!

This is not an article on how, to use Nodejs Nodemailer module or your normal fancy tech post, so there will be no need to make it even more verboose than it already is.

But in as much as we are all good at what we do. No doubt about that, there are little things that we should still remember, so I thought to share and remind us again…

TL:DR

This is an unminified(a more detailed information ) version of my article from someone else.
https://link.medium.com/1Dc7x7gmEV

Thanks for reading.