OK, I admit it. I went through a phase when I first heard the word memoization where I ignored that it existed. After all, what could a technique with a name like that have to offer me?
Well, I finally threw away my pride, admitted it might be valuable and spent some time learning about it. Yes, it is a technique used in functional programming, but it is a technique that can be applied to any coding paradigm. And it can be quite valuable.
So to make my penance complete, I thought it appropriate to do a tutorial on memoization.
Now don’t let the term scare you off. It really is not a complex concept. The patterns for implementing it are a bit involved, but the concept itself is pretty easy to understand.
I just published the tutorial on memoization and you can access it below. Take a look and give me your thoughts.
If you are interested in taking this course, here is a link that will allow you to take the course hugely discounted on Udemy:
Here is the first tutorial in this section. It shows two techniques for computing a fibonacci sequence given two starting numbers and how long you want the sequence to be.
So this begs the question, how to get started? Well, as mentioned there are several books published about the subject, and I will be reviewing some of those in the future. But I think a great first step is to really understand some of the methods of the Array object. These methods were designed around functional programming concepts. For example, map, forEach, every and reduce are a few that are valuable to understand. And it just so happens we have a tutorial on some of those methods.
I just completed two tutorials on exception handling. The first shows how to use try catch statements in your code. The second talks about when you should and should not use try catch.
Take a look at both videos and if you have any additional rules to add for using try catch statements post them here.
I love the word obfuscation. It seems to reflect its own definition. To obfuscate something is to make it difficult to understand.
Now I find that a lot of my debugging is done with the console. At times I will open up the debugger, but for most things, I can figure it out pretty quickly using the console.
Over the years I have learned a few console commands that are very helpful. I know I would have loved to have these commands when I started out, so I put together a tutorial on some of the lesser known console commands. I think these can help you find a resolution faster.