Crooked Code – Page 4 – We'll help straighten out the code…

Front End Certificate at Free Code Camp – Complete!!

Five months and one day after I discovered Free Code Camp, I’ve completed my Front End Certificate.

frontEndCert

It took a little longer than I had originally planned, but considering that in addition to learning HTML, CSS and JavaScript from scratch, I maintained a full time job and tried to spend (at least some) time with my family (including coaching a season of baseball), I’m pretty happy with the accomplishment.

A couple thoughts on the process….

When I discovered Free Code Camp, I rolled up my sleeves and began the front end development section with tunnel vision, focused only on completing the certificate. Along the way, my focus broadened… I began to realize that this process isn’t just about completing a certificate, but becoming a strong developer.

To that end, I searched for additional resources to supplement the Free Code Camp curriculum. I covered a lot of these resources in a previous post, but mostly it involved listening to podcasts, reading books, watching YouTube videos and practicing algorithms.

I also started this blog. If you would have told me before I started this process that I would start a blog on learning to code, I would have labeled you crazy…

I’m an introverted guy and generally keep my thoughts to myself, so expressing myself in these posts isn’t exactly second nature. I think, however, that doing so has significantly enhanced what I’m getting from this process (and hopefully helped at least a couple others in return).

I’ve also found that trying to explain the solution to an algorithm is, in many ways, much harder than writing the solution itself! I think this has certainly helped strengthen my coding skills and plan to continue working through the solutions to many of the freeCodeCamp algorithms and projects here at crookedCode.

So, if you find yourself getting frustrated with your progress in your own learning to code journey, take a step back and ask yourself what else you could be doing to broaden your learning experience.

And finally, I want to say – Learning to code is hard!

This journey has been difficult in many ways I could not have predicted at the onset. First, of course, learning a new skill (any new skill) can be difficult. Coding is certainly no exception, in fact, I’d argue just the opposite.

I feel the difficulty is often overlooked in the many articles (at least the ones I’ve read) that proclaim everyone can learn to code. Many of these articles fail to mention that it’s going to take a lot of work and a lot of extremely frustrating, trying moments, especially if you’re teaching yourself.

I’m not arguing against the idea that people should learn to code… If learning to code interests you, then by all means, let nothing stand in your way. Before you start, however, make sure that it’s something you really want to do and make sure you’re prepared to commit the time and mental energy to accomplish your goal.

In addition to the difficulty inherent to learning to code, many other aspects of the journey add to the difficulty…

Time management has been a big one for me. Keeping a full time job, having a wife and two active sons and learning to code is a very full plate. Through most of baseball season, I just coded whenever I could fit it in the schedule…

It seemed like there was something going on every night and throughout the weekend, so whenever there was a break, I would try to put some work in. I’ve got to say though, that pace is unsustainable if you value your mental health and the happiness of your family.

Since baseball has finished, I have blocked off two evenings and one day on the weekend that I devote to learning to code. Everything else (at least when I’m not at my full time job) can be spent with family or catching up with stuff around the house.

If you are learning to code and have other personal commitments, I highly recommend blocking off a schedule of when you plan to work. Otherwise, you always feel like you should be working and everything else in your life takes a back seat, and suffers because of it….

Of course, there are other things like maintaining self-confidence, battling impostor syndrome, deciding what to learn, setting up a development environment, etc., etc. but this post is already longer than I had planned. Just know that if you are struggling in your journey to learn to code, you are not alone, there are plenty of us out there in the same boat.

So, if you’re still reading this, thank you and good luck on your own journey. I’ll keep posting here at crookedCode to try to make things easier for those that actually read it. As for right now, I’m off to start the back end development certificate at Free Code Camp…

-Jeremy

FCC Intermediate Algorithm Scripting Challenge – ‘DNA Pairing’

Today, we’ll cover freeCodeCamp’s Intermediate Scripting Challenge ‘DNA Pairing‘. The challenge here is to write a function that accepts a string of characters and returns a 2D array of matched base pairs.

If you’re not caught up with your molecular biology, here’s a quick lesson…

Molecular Bio 101 (mostly not needed to solve algorithm)

DNA is the double stranded nucleic acid that carries your genetic information. Each single strand is composed of units called nucleotides, of which, there are four – cytosine (C), guanine (G), adenine (A) and thymine (T). In double stranded DNA, these nucleotides bond in specific base pairs, A with T and C with G.

DNA stores all kinds of biological information and make up our chromosomes, which, in turn, make you who you are… Enough bio, let’s get back to solving the algorithm….

Bio Class Dismissed…

As we get into the intermediate and advanced algorithm challenges, each challenge will have multiple (even many) approaches to a solution. My plan with Crooked Code is to explain the solution that I used, then search for solutions used by others in order to illustrate the various ways an algorithm can be written.

This is what freeCodeCamp gives us as a starting point for ‘DNA Pairing’:

function pairElement(str) {
  return str;
}

pairElement("GCG");

function pairElement(str) {

return str;

}

pairElement("GCG");

The instructions provided for this challenge tell us that we’ll be getting a string as an argument and we must return a 2D array that matches up each element (letter) with it’s base pair counterpart.

Let’s get started working on a solution…

I started by ‘splitting’ the string argument into an array using string.split() method. I covered string.split() in depth here. I also created some variables that we’ll use later in the function. My ‘pairElement’ function now looks like:

function pairElement(str) {
  
  var singleArr = str.split("");
  var doubleArr = []; //blank array to house 2D end result
  var element = "";   //element and match will be used in our switch statement
  var match = "";

}

function pairElement(str) {

var singleArr = str.split("");

var doubleArr = []; //blank array to house 2D end result

var element = ""; //element and match will be used in our switch statement

var match = "";

}

We now must scroll through ‘singleArr’ and pair up each element with it’s matching pair. We can use a for loop to scroll through the array, but how can we match up the pairs?

A bunch of if/else statements would work but a switch statement is a better option here. A switch statement will evaluate a given expression, then transfer control to the case that matches the outcome of the expression.

I’ve included the syntax of a switch statement written by mozilla in order to make the explanation easier.

In our case, the expression will be just a letter, as will each case value. We can then write a statement to be executed for each individual case.

//syntax of switch statement found at https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/switch

switch (expression) {
  case value1:
    //Statements executed when the result of expression matches value1
    [break;]
  case value2:
    //Statements executed when the result of expression matches value2
    [break;]
  ...
  case valueN:
    //Statements executed when the result of expression matches valueN
    [break;]
  default:
    //Statements executed when none of the values match the value of the expression
    [break;]
}

//syntax of switch statement found at https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/switch

switch (expression) {

case value1:

//Statements executed when the result of expression matches value1

[break;]

case value2:

//Statements executed when the result of expression matches value2

[break;]

...

case valueN:

//Statements executed when the result of expression matches valueN

[break;]

default:

//Statements executed when none of the values match the value of the expression

[break;]

}

To sum up the logic for our algorithm…

split the given string into an array
loop through array and match each element with it’s pair
‘push’ each new pair into 2D array
return 2D array

At this point, we’ve covered everything needed to solve the ‘pairElement’ function. If you’re working through the freeCodeCamp curriculum you may want to go try to solve it on your own, otherwise, read on…

Spoilers_ahead

Here’s the solution to the ‘DNA Pairing’ challenge that I came up with:

function pairElement(str) {
  
  var singleArr = str.split("");
  var doubleArr = []; //blank array to house 2D end result
  var element = "";   //element and match will be used in our switch statement
  var match = "";
  
//loop through singleArr and pair element with it's match
//push element and match onto 2D array
  for (var i = 0; i < singleArr.length; i++){   
    element = singleArr[i];
    
    switch (element){
      case "G":
        match = "C";
        break;
      case "C":
        match = "G";
        break;
      case "A":
        match = "T";
        break;
      case "T":
        match = "A";
        break;
    }
    doubleArr.push([element, match]);  
  }
  return doubleArr;
}

function pairElement(str) {

var singleArr = str.split("");

var doubleArr = []; //blank array to house 2D end result

var element = ""; //element and match will be used in our switch statement

var match = "";

//loop through singleArr and pair element with it's match

//push element and match onto 2D array

for (var i = 0; i < singleArr.length; i++){

element = singleArr[i];

switch (element){

case "G":

match = "C";

break;

case "C":

match = "G";

break;

case "A":

match = "T";

break;

case "T":

match = "A";

break;

}

doubleArr.push([element, match]);

}

return doubleArr;

}

The freeCodeCamp wiki page (written by @Rafase282 and @sabahang) provides 2 solutions to this algorithm challenge. The first, ‘basic’, solution is very similar to mine, using a switch statement, so I won’t include it for the sake of redundancy.

The second, ‘intermediate’, solution uses an object, and we haven’t really covered objects in much detail here at Crooked Code. I’ll include the code below so we can see a second, very different solution, but won’t provide an explanation, as objects are far too big of a topic to cover at the end of this post.

function pairElement(str) {
  //define a map object with all pair possibilities 
  var map = {T:'A', A:'T', G:'C', C:'G'};
  //split str into a char Array
  strArr = str.split('');
  //replace each Array item with a 2d Array using map
  for (var i=0;i<strArr.length;i++){
    strArr[i]=[strArr[i], map[strArr[i]]];
  }
 return strArr;
}

function pairElement(str) {

//define a map object with all pair possibilities

var map = {T:'A', A:'T', G:'C', C:'G'};

//split str into a char Array

strArr = str.split('');

//replace each Array item with a 2d Array using map

for (var i=0;i<strArr.length;i++){

strArr[i]=[strArr[i], map[strArr[i]]];

}

return strArr;

}

You can see an explanation to this solution at the wiki page.

That’s it for now, hopefully this helped straighten out the code…

-Jeremy

FCC Intermediate Algorithm Scripting Challenge – ‘Boo who’

This post will cover freeCodeCamp’s intermediate algorithm scripting challenge ‘Boo who’.

‘Boo who’ challenges us to write a function that checks if a given argument is classified as a boolean primitive. If so, return true, if it’s anything else, return false.

The solution, once written, is quite simple but there are a few key concepts we have to understand before we can get there.

Here’s what FCC gives us as a starting point:

function booWho(bool) {
  // What is the new fad diet for ghost developers? The Boolean.
  return bool;
}

booWho(null);

function booWho(bool) {

// What is the new fad diet for ghost developers? The Boolean.

return bool;

}

booWho(null);

Now, we have to figure out… What the hell is a boolean primitive?

First, let’s consider what boolean means? Boolean is a word used in both math and computer science. In computer science, it generally refers to a data type or a variable that can have only one of two values, usually true or false.

Boolean variables are useful in controlling the logic of an algorithm and are generally used in conditional statements such:

if (bool){
  //if bool is true, do something
}else{
  //if bool is false, do something else
}

if (bool){

//if bool is true, do something

}else{

//if bool is false, do something else

}

Second, what does primitive mean? Mozilla, as always, gives a pretty good description of a primitive. Basically, Mozilla tells us a primitive value ‘is data that is not an object and has no methods.’

Tangent on Primitive Types vs. Reference Type

According to the latest ECMAScript standard, JavaScript has 7 data types. 6 primitive types which are string, number, boolean, null, undefined and symbol and one reference type – object.

The difference between the two types becomes confusing when you consider that JavaScript provides constructor functions that allow you to wrap boolean, number and string values as objects, which changes them from primitive to reference type.

Consider the following:

var str = new String ('hello world');

//'hello world' is a primitive string value
//str is now a string object

typeof str;  //'object'
typeof 'hello world'; //'string'

var str = new String ('hello world');

//'hello world' is a primitive string value

//str is now a string object

typeof str; //'object'

typeof 'hello world'; //'string'

Problems start to arise if you try to use a string object like a string primitive. Keep in mind that a string object is still an object, and behaves like one.

For instance:

var str1 = 'primitive string';
var str2 = 'primitive string';

str1 === str2; //true

//however

var obj1 = new String('object string');
var obj2 = new String('object string');

obj1 === obj2; //false

//string objects are two completely different objects and will only equal themselves

var str1 = 'primitive string';

var str2 = 'primitive string';

str1 === str2; //true

//however

var obj1 = new String('object string');

var obj2 = new String('object string');

obj1 === obj2; //false

//string objects are two completely different objects and will only equal themselves

Given that JavaScript will allow you to use the methods associated with an object prototype on the primitive values (example below), it is best to use primitive types whenever possible.

//example of a string prototype object method used on a string primitive

'hello world'.toUpperCase(); //'HELLO WORLD'

//example of a string prototype object method used on a string primitive

'hello world'.toUpperCase(); //'HELLO WORLD'

FYI, Effective JavaScript by David Herman has a good section on why primitive types should be preferred to using object wrappers and I derived some of my examples above from those found in his book.

Ok, enough about Primitive Types, hopefully this has been more than enough info to solve ‘Boo who’.

End of Tangent

Check out the Mozilla link above for further explanation of primitive values (or this one for info on the Boolean object), but for our purposes in solving ‘Boo who’ we now know that the only boolean primitives are true and false.

So, now we have to fill in the booWho function above, checking if bool equals true or false. In doing so, we’ll use the strict equality operator (===) vs. the loose equality operator (==), as the latter will convert the two values to a common type before checking equality, which is not what we want.

At this point, we’ve gone over all the tools you’ll need to write the booWho function, so if you’re working through the freeCodeCamp curriculum you may want to go try to solve it on your own, otherwise, read on…

Spoilers_ahead

Here’s the solution to ‘Boo who’ that I came up with:

function booWho(bool) {
  if (bool === true || bool === false){
    return true;
  }
  return false;
}

function booWho(bool) {

if (bool === true || bool === false){

return true;

}

return false;

}

As you probably know, || is the logical operator ‘or’ in JavaScript, so this function will return true if bool equals true or false.

The freeCodeCamp wiki provides an even shorter solution using the ‘typeof’ operator, written by Rafase282.

function booWho(bool) {
  return typeof bool === 'boolean';
}

function booWho(bool) {

return typeof bool === 'boolean';

}

Both solutions solve the ‘Boo who’ algorithm challenge and pass all the test cases at freeCodeCamp.

That’s it for now, hopefully this helped straighten out the code…

-Jeremy

My Learn-to-Code Journey: 3 months in…

I started my learn to code journey in late February, 2016, when I signed up for freeCodeCamp. So it’s been about 3 1/2 months and I figured this was as good a time as any to share my thoughts, progress, tools that I’ve found valuable, etc, etc.

First, a little background on what led me to this journey…

I’ve been doing drug discovery/pharmaceutical research for nearly 20 years. Last year, I found out that my job was moving to a different part of the country and for many reasons, not the least of which was apprehension over relocating my two sons, we decided not to make the move.

After a lot of soul searching (and driving my wife crazy), I decided to shift my career and learn to code. In fact, the real light bulb moment was reading Derek Sivers post ‘Should you learn programming? Yes.’ It’s where I discovered freeCodeCamp and everything seemed to snowball from there…

Stumbling on that Sivers post was just what I needed and I’ve since become a huge fan of his. If you haven’t read or watched anything by Derek, do yourself a favor and check out his site. He has a unique perspective on life that’s completely refreshing when compared to most of what you encounter in the world today.

Ok, enough background…

Looking back at the last 3 months, it’s hard to put into words everything I’ve gone through in learning to code. So far the journey has been fun, frustrating, time consuming, enlightening, tiring, exciting, stressful, rewarding, humbling… Basically, it’s been a roller coaster ride.

It seems like one minute I feel like I’m on top of the world and that I can do and create anything. Then the next minute I feel like a total idiot and don’t know anything. Then genius again, then an even bigger idiot than before… You get the picture.

Free Code Camp Update

For the time being, I still have a full time job (and coach my son’s baseball team) so I don’t have as much time as I’d like to devote to coding. I’ve put in a lot of late nights and weekends and, despite the two huge time commitments mentioned previously, feel like I’ve been able to make a ton of progress.

I’m nearing completion on the Front End Development Certificate at freeCodeCamp. I’ve completed all of the Algorithm Scripting Challenges and most of the Development Projects. The only projects that I have left are to finish my Tic Tac Toe game, then build a Pomodoro Clock and a Simon game. These, obviously, will take some time, but I should get them done within the next month or so. You can check out my projects on my Codepen page.

I’ve also started on the Back End Development Certificate. The first lesson was on Git, then you get right in to Node.js and Express.js. The biggest thing I’ve learned so far on the back end (in addition to reinforcing once again that I’m an idiot) is that I need to become comfortable in the command line.

Thoughts on Free Code Camp thus far..

I feel that freeCodeCamp, in providing projects with increasing levels of difficulty, provides a great path to follow in learning to code. On the other hand, I feel some of the learning modules are lacking. For instance, having gone through the git and npm learning modules at the beginning of the back end certificate, I don’t feel like I learned much and have little more understanding of how to use them now than when I started.

I don’t think, however, this is a negative for freeCodeCamp (and not sure if it was purposefully constructed this way or not). After all, what is the purpose of freeCodeCamp?? To prepare you to become an employable full stack web developer?

Part of this whole process is learning to become resourceful and knowing where and how to look for answers when you run into problems. Something at which I’ve become increasingly skilled. Is it frustrating to pause in the middle of a project to go look up how to code something? Absolutely. Over and over again? Yup… But in the end, I’ll be a much stronger programmer for it.

In addition to Free Code Camp

In a previous post, I mentioned some of the resources I’ve been using as I make my way through the front end cert at FCC. In addition to these, I’ve been broadening my knowledge of software development in general through the use of other sites, listening to podcasts and constantly searching for ways to learn (including starting a blog!!).

One of the other sites I discovered is Codewars.

Having finished all 3 algorithm sections at FCC, I was looking for a way to further my algorithm solving skills. I haven’t used the site extensively yet, in fact, I’ve only worked through about 4 or 5 ‘kata’ (which is what Codewars calls their algorithm problems), but I plan on going back on a fairly regular basis to stay fresh with Javascript as I work through the backend at FCC.

After you solve a given ‘kata’ , you can see the solutions of previous users. In fact, I’m planning on writing one of my next posts on an embarrassingly long solution I wrote that others had solved in one line. Ha! Live and learn I guess…

Like I said before, I’ve also gotten in the habit of listening to podcasts on my commute to and from work.

Some of my favorites, in no particular order are: JavaScript Jabber, CodeNewbie, Coder Radio, Eat Sleep Code, Becoming a Data Scientist, CodePen Radio, Simple Programmer, Software Engineering Daily and anyone that interviews either Seth Godin or Derek Sivers (The Tim Ferriss Show has great interviews of them both).

More Learning Tools

As I said before, I’ve used a lot of the tech websites (Mozilla, Stack Overflow, W3schools, etc) to learn as I went through the Front End course. I’ve decided to try something different on the back end. I signed up to audit a Node.js course on coursera. I can’t give any feedback on how useful the course is or whether it will help with the back end cert at FCC, as I just signed up for it yesterday, but I’ll be sure to write a future post about it.

While listening to the tech podcasts mentioned above, I kept hearing, over and over, the advice to create a blog. So I did… And I’m happy I did.

I have no idea how many people this blog will reach in the end, but one of the great benefits of it has been in reinforcing everything I’ve been learning. I know one of the best ways to really learn something is to try to teach it to others, but I didn’t realize just how true this was.

Even in writing a post about the solution to a Basic Algorithm Scripting challenge, I’ve really had to solidify my knowledge of the JavaScript language and understand the methods and data types that I’ve used. So, if you want to check if you really understand something, try explaining it to someone else…

As for advice on creating the blog itself, Simple Programmer (John Sonmez) created a great, and free, blogging course that walks you through the steps of creating a blog. If you’re considering creating your own blog, I recommend signing up for his course, it’s what I used to get started.

Damn this is post is long…

On the remote chance that anyone has stumbled on this blog, and on the even more remote chance that you’re still reading, let me leave you with this..

If you’re on your own journey in learning to code, you are going to go through some rough patches and getting though those times are going to be extremely difficult. My advice is this… Don’t take the easy way out, it’ll just lead to more rough patches.

What I mean by that is if you are looking to solve problem x, or write some code to accomplish y, the easy way would be to google it, find some code that someone else has written, copy and paste it into your project and move on… This may solve your short-term problem, but will get you nowhere in the end.

I’m not saying don’t use google to solve problems or look up ways to write something in whatever language you are using at the time. I do that all the time. What I am saying is take the time to learn how the code is written, or the logic behind the algorithm and go write your own solution…

That’s all for now, I’m off to continue my journey…

-Jeremy

FCC ‘Seek and Destroy’

This post will work through ‘Seek and Destroy’, one of freeCodeCamp‘s basic algorithm scripting challenges. This challenge will help us introduce the Arguments object and callback functions.

The Seek and Destroy challenge states that ‘provided with an initial array (the first argument in the destroyer function), followed by one or more arguments’ we need to write a function that will remove the values of all the arguments given after the initial array, from the initial array.

Sounds confusing, I know… Let’s visualize it to clear things up.

function destroyer(arr){
   //write a function that can be called 
   //with any number of arguments provided 
   //(see destroyer call below)
   //and remove those arguments from the initial array(arr)
}

destroyer(arr, value1, value2, value3, value4);

function destroyer(arr){

//write a function that can be called

//with any number of arguments provided

//(see destroyer call below)

//and remove those arguments from the initial array(arr)

}

destroyer(arr, value1, value2, value3, value4);

One of the major problems we have lies with ‘followed by one or more arguments’… If we don’t know how many arguments there will be, how do we write a function to handle them?

The answer to that comes in the form of the Arguments object. JavaScript provides a local variable ‘arguments’ that acts like an array with an element for each argument passed to the function. You access the arguments just like you would an element of any other array like so:

arguments[0] //contains the initial array
arguments[1] //contains the first value to delete from the initial array

1 2	arguments[0] //contains the initial array arguments[1] //contains the first value to delete from the initial array

The arguments object makes solving this algorithm challenge much easier. Looking forward at ways to solve this problem, we need to a) access the arguments we need to delete from the initial array and b) somehow remove those arguments from the array.

Storing arguments for easy access

The first thing we’ll do is create a new array and store all the arguments (other than the initial array) in it.

  var argArr = [];
  
  for (var i = 1; i < arguments.length; i++){
    argArr.push(arguments[i]);
  }

var argArr = [];

for (var i = 1; i < arguments.length; i++){

argArr.push(arguments[i]);

}

As you can see, arguments can be treated like any other array… Here, we used the length property and looped through arguments (starting at element 1 so as to avoid the initial array, which will be passed in as the first argument, or arguments[0]). Setting it up this way will handle any number of arguments passed to the destroyer function.

The push() method in JavaScript is used to ‘push’ new elements on to the end of the calling array.

Tools we’ll need to remove arguments from the array

In order to remove the arguments from the initial array, we will use the filter() method. The filter method introduces a concept we haven’t talked about here at CrookedCode: the callback function.

A Quick note on functions in JavaScript

The power of functions, and what they allow you to do, are core to successful JavaScript programming. Functions can be passed to and returned from other functions. They can also be stored as variables.

A function that accepts another function as an argument is called a higher-order function, whereas, the function that is passed as the argument is called a callback function. The Eloquent JavaScript chapter on functions is a great tutorial on the use of functions in JavaScript.

Eloquent JavaScript also devotes an entire chapter to higher-order functions. I highly recommend reading and working through the examples in both of these chapters. If you’re looking for something a little quicker, JavaScriptissexy.com has an excellent article on understanding callbacks and higher order functions.

The filter() method accepts a callback function and performs that callback on every element in the calling array. If the callback returns true for a given element, that element is kept. If the callback returns false, obviously, that element is not kept.

As stated above, filter() calls the callback function on every element of the calling array, but it does not mutate that array. Therefore, you must save the kept elements as a new array.

The one final tool we’ll need before we try to solve this algorithm is the array.indexOf() method. indexOf() will return the first index at which a given value is found. If the given value is not found, indexOf() returns -1.

Putting it all together…. (finally)

We’ve already created argArr[] to hold the values that we need to delete from the initial array. We now need to write a callback function for filter() that will return true if we want the element to stay and false if we want to delete that element.

We know that indexOf() will return -1 if a given value is not found. We also know that we want to keep elements of the initial array that aren’t found in argArr[]. So, for each element of the initial array, lets call argArr.indexOf(), and return true for values of -1. Therefore, we’ll be returning true for (and keeping) values that aren’t in argArr[].

Like so:

function destroyer(arr) {
  // create array to store arguments to be deleted
  var argArr = [];
  
  //cycle through the arguments object and store in argArr
  for (var i = 1; i < arguments.length; i++){
    argArr.push(arguments[i]);
  }
  
  //filter out values found in argArr
  //if value is not found, -1 will be returned from indexOf() 
  //therefore the callback will return true and the element will be kept
  arr = arr.filter(function(val){
    return argArr.indexOf(val) === -1;
 });
  
  //return new array
  return arr;
}

function destroyer(arr) {

// create array to store arguments to be deleted

var argArr = [];

//cycle through the arguments object and store in argArr

for (var i = 1; i < arguments.length; i++){

argArr.push(arguments[i]);

}

//filter out values found in argArr

//if value is not found, -1 will be returned from indexOf()

//therefore the callback will return true and the element will be kept

arr = arr.filter(function(val){

return argArr.indexOf(val) === -1;

});

//return new array

return arr;

}

Wow… This post covered a bunch of stuff we haven’t previously gone over here at CrookedCode, hopefully this helped straighten out the code for you. See you next time…

-Jeremy

FCC ‘Slasher Flick’

Today we’re going to work on freeCodeCamp‘s Basic Algorithm Scripting challenge – ‘Slasher Flick’. This will be a pretty short post as we’re really not going to cover anything new, I just wanted to go through this algorithm to show how short and concise a solution to a problem can be.

The ‘Slasher Flick’ challenge is to ‘return the remaining elements of an array after chopping off n elements from the head’.

This is the starting point FCC gives us:

function slasher(arr, howMany) {
  // it doesn't always pay to be first
  return arr;
}

function slasher(arr, howMany) {

// it doesn't always pay to be first

return arr;

}

As you can see, we need to write the body of the function ‘slasher’, which accepts an array ‘arr’ and a number ‘howMany’. slasher should then return ‘arr’ with ‘howMany’ elements removed from the head, or beginning, of the array.

We can actually accomplish this challenge with just 1 line of code. To do so, we’ll use the array.slice() method, which we first used in the ‘Title Case a Sentence’.

If you remember from that previous post, array.slice() is a method that returns a new array (which is what we need this function to return). It takes 2 arguments. The 1st argument is the index of where the returned array will begin, which is conveniently given to us as the argument ‘howMany’. The 2nd argument for array.slice() is the index of the final element to include in the returned array, and is optional. Since we’ll be returning the entire array after cutting off ‘howMany’ elements, we’ll only use 1 argument. If you wanted to include ‘arr.length’ as the second argument to make it more clear, that would work too.

Now, given we have everything we need to return the wanted array, here’s the solution:

function slasher(arr, howMany) {
  
  return arr.slice(howMany);
}

function slasher(arr, howMany) {

return arr.slice(howMany);

}

This function now returns the given array with ‘howMany’ elements removed from the head.

Obviously this algorithm is pretty simple, it’s part of the ‘Basic Algorithm Scripting’ after all, but I wanted to cover it to show that sometimes the solution can be pretty straightforward and simple… No need to overthink it.

Hopefully this helped straighten out the code for you.

-Jeremy

FCC ‘Title Case A Sentence’

Today we’re going to work through another of freeCodeCamp’s Basic Algorithm Scripting challenges – ‘Title Case A Sentence’. To solve this challenge we must write a function that accepts a string, then returns that string with the first letter of each word capitalized and the remainder of each word in lowercase.

We’ll be using concepts that we’ve covered in previous posts (i.e. for loops, string methods, and arrays) and adding a couple new things like method chaining and some new string methods.

As I’ve mentioned previously, in JavaScript, the data type String has many methods associated with it. W3schools has a good intro to these methods, MDN covers the string object on a deeper level.

Here’s the starting point given to us by freeCodeCamp.

function titleCase(str) {
  return str;
}

titleCase("I'm a little tea pot");

function titleCase(str) {

return str;

}

titleCase("I'm a little tea pot");

We’ll start solving this challenge by breaking the given string (str) into an array of words, the same way we started ‘Find the Longest Word in a String’.

  var wordArray = str.split(" ");

1	var wordArray = str.split(" ");

Quick tangent – we haven’t discussed yet that JavaScript can be tested right in your browser. If you have a question about what a snippet of code does, just plug it into the console of your browser and test it. To make sure the str.split() method that I just created is doing what I want, I plugged it into the console in Chrome and tested it.

var str = "I'm a little tea pot";
var wordArray = str.split(' ');
console.log(wordArray);
["I'm", "a", "little", "tea", "pot"]

var str = "I'm a little tea pot";

var wordArray = str.split(' ');

console.log(wordArray);

["I'm", "a", "little", "tea", "pot"]

As you can see, str.split(‘ ‘) is splitting the given string into an array, with each word as an individual element. Now I’m confident in continuing with the solution to the algorithm challenge…

Next, we need to iterate through the array and capitalize the first letter of each word and lowercase the rest of the word. To iterate through the array, we’ll use a for loop. To handle the upper/lowercasing of the words, we’ll need a couple new string methods.

For a deeper understanding, and a list of many more string methods, check out the MDN page on strings. Today, we’ll be using charAt(), toUpperCase(), toLowerCase() and slice().

toUpperCase() and toLowerCase() do exactly what they sound like, they return the calling string value in upper and lower cases respectively. charAt() allows you to access a specific character of a string and takes one parameter – the index of the character you want to access (indexes of strings start at 0, just like arrays).

slice() allows you to access a specific segment of a string. It takes two arguments, the indexes of where you want the segment to start and finish. The second parameter is optional, if you leave it out, the slice will start at the first index you provide and continue to the end of the string. Very important – all four methods mentioned above return the value of a string, they do not change the calling string. See code below for demonstration…

var str = "I'm a little tea pot";
var newStr = str.slice(3);
console.log(str);
I'm a little tea pot //original string (str) unchanged by slice()
console.log(newStr);
 a little tea pot    //slice starting at index(3) was returned to newStr

var str = "I'm a little tea pot";

var newStr = str.slice(3);

console.log(str);

I'm a little tea pot //original string (str) unchanged by slice()

console.log(newStr);

a little tea pot //slice starting at index(3) was returned to newStr

Now, as mentioned above, we can chain these methods together using dot notation, so that after one method is called, a second method is called on the returned string of the first.

var str = 'test';
var newStr = str.charAt(0).toUpperCase();
console.log(str);
test         //again, original string left unchanged
console.log(newStr);
T            //toUpperCase was called on charAt(0) and returned to newStr

var str = 'test';

var newStr = str.charAt(0).toUpperCase();

console.log(str);

test //again, original string left unchanged

console.log(newStr);

T //toUpperCase was called on charAt(0) and returned to newStr

Check out this post on method chaining for a better understanding.

We can use everything we’ve talked about to get the first character of a string and capitalize it, then get the rest of the string (starting at index 1) and lowercase it. Putting it all together looks like this:

function titleCase(str) {
  //create an array to hold each word in the string
  var wordArray = str.split(" ");
  //loop through each element of the array
  //capitilize the first character of each word, lowercase rest of word
  for (var i = 0; i < wordArray.length; i++){
    wordArray[i] = wordArray[i].charAt(0).toUpperCase() + wordArray[i].slice(1).toLowerCase();
  }
  //turn array back into string and return  
  return wordArray.join(" ");
}

function titleCase(str) {

//create an array to hold each word in the string

var wordArray = str.split(" ");

//loop through each element of the array

//capitilize the first character of each word, lowercase rest of word

for (var i = 0; i < wordArray.length; i++){

wordArray[i] = wordArray[i].charAt(0).toUpperCase() + wordArray[i].slice(1).toLowerCase();

}

//turn array back into string and return

return wordArray.join(" ");

}

Several notes on the above solution…

We used the join() method, which does the exact opposite of split. join() is an array method that returns a string delimited by what you pass as an argument. In this case, we gave an empty space (” “) as the argument, so each element of the array was joined together separated by a space.

Also, you will note that we used a ‘+’ to connect 2 parts of a string together. This is an easy way in JavaScript to build a string. It can be used with both literal strings and variables as such:

var a = 'this'
var b = 'you ' + 'can ' + 'connect ' + 'strings ' + 'like ' + a;
console.log(b);
you can connect strings like this

var a = 'this'

var b = 'you ' + 'can ' + 'connect ' + 'strings ' + 'like ' + a;

console.log(b);

you can connect strings like this

Hopefully this straightened out the code for you… See you next time.

-Jeremy