Code Challenge #11: JavaScript Functional Programming

Written by - - Aggregated on Tuesday June 12, 2018

Previously on the code challenge #10, we delved into lazy loading images for performance, you can check out the challenge post and solution.

This week on the code challenge, we'll be re-visiting the basics of JavaScript with Arrays. Arrays are like containers which hold various data types.

While these containers are useful for holding various data types it is important to understand the manipulation of arrays to analyze and utilize withheld data. This is done with the use of specific functions which are actionable on Arrays called Methods.

The Challenge

This challenge is quite unique such that we will be using some really useful built-in array methods to manipulate the provided arrays. Three arrays are provided and each comes with 3 problem parts to be solved. In the first array:

In the second array:

In the third array:

Complete these problems using any array method in the best way possible. Useful methods include:

Note that you can write your results to the DOM or even log to console, whichever is fine by you.


This challenge can be completed by using any technique or method. However, try to completely solve each part in as little lines as possible using functions.

Goals for this Challenge

On completion of this challenge you should be able to:


In a bid to make this more fun and challenging, a bonus will be to complete this the challenge parts without the aid of built-in methods and functions.


To get started quickly, a base codepen containing required arrays is provided. These arrays to be utilized contain objects with data in key-value pairs.

Fork this base codepen to get started

This previous Scotch post could be useful to you in solving this challenge.


On completion of the challenge, if you wish to showcase your work and receive reviews, kindly,


The solution to this challenge will be released on Saturday. Happy coding!.

« Building data science teams to have an … - Facebook Code - Redecentralising the web »