Family Man. Passionate web developer currently residing downtown Chicago. Purple belt in Brazilian Jiu Jitsu. Pizza lover.

Website Launch: Champion Spotlight

I launched a new website dedicated to finding champion spotlights: for the game League of Legends (LoL).

If you haven’t heard of League of Legends:

League of Legends is a fast-paced, competitive online game that blends the speed and intensity of an RTS with RPG elements. Two teams of powerful champions, each with a unique design and playstyle, battle head-to-head across multiple battlefields and game modes.

100% of the website is built on Vue.js and the champions are loaded via an API.

Technology Stack

  • Amazon S3 (static website hosting)
  • Amazon Route 53 (DNS)
  • Amazon Cloudfront (CDN)
  • Vue.js

The goal was to start simple. I find it easier to iterate on something in production than to continuously add features without ever making it into production.

Biggest Challenge

Implementing S3, Route 53 and Cloudfront was the biggest obstacle. Every article on the internet seemed to be slightly different than what I needed. One thing I’ve learned over the years programming is that perseverance pays off. Eventually after spending hours configuring settings the website eventually worked!


Building Champion Spotlight was a blast and learning experience. Overall I learned about the AWS infrastructure, filters in Vue, and that I’m able to learn new technologies on the fly.


Introduction to Vue.js 2 Filtering with Lodash

Filtering in Vue.js is simple thanks to the filter function built into Vue. Let’s take a look at an introduction filtering with Vue.js and Lodash.


Each Vue app requires a HTML element to bind with. Generally the HTML element is a div with a unique id attribute. In this example the Vue instance is bound to simple-filter.

<div id="simple-filter">
var app = new Vue({
    el: "#simple-filter"

Basic list unfiltered

Next let’s add default data and display the list.

You’ll notice v-for on the li element. This essentially means for each element in the array do something. In our case print the element between the li element.

<div id="simple-filter">
        <li v-for="animal in animals">{{ animal }}</li>

var app = new Vue({
    el: "#simple-filter",
    data: {
        animals: ['Zebra', 'Lion', 'Shark', 'Dog', 'Bear', 'Monkey']

Produces the following list:

  • Zebra
  • Lion
  • Shark
  • Dog
  • Bear
  • Monkey


Vue.js has built in functionality to filter arrays. The basic idea is to iterate over each element with a condition. If the condition is true the element stays in the array. If the condition is false the element is removed from the array.

Within the v-for instead of using the regular animals array in the previous example it is referencing a computed property filteredAnimals. Using the computed property ensures the list is always up to date when searchText is updated.

<div id="simple-filter">
    <input type="text" v-model="searchText" />
        <li v-for="animal in filteredAnimals">{{ animal }}</li>
var app = new Vue({
	el: "#simple-filter",
    data: {
    	searchText: "",
        animals: ['Zebra', 'Lion', 'Shark', 'Dog', 'Bear', 'Monkey']
    computed: {
    	filteredAnimals: function() {
        	var self = this;
        	return this.animals.filter(function (animal) {
            	    return _.includes(animal.toLowerCase(), self.searchText.toLowerCase());

filteredAnimals updates itself when searchText changes due to the nature of Vue. The filter function on this.animals is provided by Vue. Each iteration of this.animals passes an animal element to the function. Within the function a true or false value should be returned. Returning true indicates keeping the element and false instructs Vue to remove the element.

In the filter function notice _. this is Lodash. In short Lodash is a library that contains commonly used utility functions such as the includes function. The includes function searches an array, object, or string for a given value. The value in this example is the user provided text searchText. In addition I’ve added a toLowerCase() because users may not always include capital letters. Forcing the compare to be case insensitive is useful for this use case but may not in every case.

Filtering the array does not actually update the animals array. Instead a new array is returned which is then returned from the filteredAnimals computed function.

Working example below:

How To Bind An Interface To An Implementation In Laravel

Binding an interface to an implementation promotes good coding practices. As a result the code is less coupled, more maintainable, and testable.

Why might someone want to bind an interface using Laravel? To put an abstraction between the application and the concretion. A concretion is a class that implements the interface. It is a specific implementation, in our example it will be Amazon S3 file storage provider. The application doesn’t care which implementation it receives just that it receives an implementation with the guaranteed functions.

Lets build functionality to interact with files on a storage provider such as Amazon S3. Initially all files will be uploaded and deleted on S3 only. There are other ways to accomplish this and the main goal is to demonstrate how to bind an interface to an implementation and not so much the actual code to upload to a storage provider.

Create An Interface

The interface will determine which functions are available on the concrete implementation through the binding.

Create The Concrete Implementation

The concretion is an Amazon S3 file storage provider. This file is where Amazon specific upload/delete functionality goes.

Create The Laravel Service Provider

The Laravel service provider is the mechanism that binds the FileStorageInterface to the S3FileStorage class implementation. This means if we use dependency injection for the FileStorageInterface or use App:make it will automatically resolve to the S3FileStorage class.

Using The Interface

In the below example we are not using the implementation directly. Instead it is automatically resolved through the service provider which returns the concrete implementation. Laravel will automatically resolve dependencies if they are in the __construct() functions. We can see below that the controller doesn’t know about Amazon and nor should it. I am only using the controller in this example to provide a demonstration. There are other places where we would use the storage provider that might better organize the code.

Final Thoughts

If we wanted to swap out for Dropbox or some other provider the impact is minimal, create a Dropbox implementation and change the provider. The application would now use the Dropbox implementation instead of the Amazon S3 implementation.

Following this pattern can also help separate the application from Laravel which could make reusing this code in other projects easier than if the Amazon S3 code were included in a model directly. Definitely think about how to best structure your code and not to fall into the framework convenience trap of putting everything in a model, controller or view. In most cases there are better places for code than those 3 areas.


Magento Upgrade 1.7 to 1.9

Recently I upgraded a Magento site from 1.7 to 1.9 and recorded the steps I took to upgrade. This should work for other versions as well, but in my case it was 1.7 to 1.9.

Before the upgrade backup entire site so you can rollback if necessary.


  1. Visit <>/downloader and login with your regular admin credentials.
  2. Select “Put store in maintenance mode” in the Settings section.
  3. Click the check for upgrades button.
    1. All items that can be upgraded will display in a different color.
  4. Select items you wish to upgrade using the dropdown next to the installed version number.
  5. Click “Commit Changes” button to start the upgrade.
    1. Text should begin to appear in the console as Magento is finishing the tasks.
  6. Upgrade is finished.
  7. Check the site is up and running properly.

Post Upgrade

A few minor errors occurred after the upgrade and here is how I solved them.

  • If the maintenance flag is still active remove the maintenance file by rm maintanence.flag
  • Apache was complaining that index.php and downloader/index.php were group writeable. Change permissions on the index.php and downloader/index.php to 644.
  • PHP threw an error in file app/code/core/Mage/Core/Controller/Varien/Front.php saying Call to member function rewrite() on a non-object. If you are using a cache restart the caching mechanism. E.g. sudo service memcached restart
  • Admin URL displayed a blank white page also commonly referred to as the “White Screen Of Death”. This was fixed by downloading the Magento zip file from Magento and uploading the necessary files to app/design/adminhtml/default/default and skin/adminhtml/default/default. The upgrade appeared to have deleted those files so they needed to be re-uploaded to their respective locations.

Framework Convenience Trap

The idea is “x” framework provides a level of convenience that can make developers sloppy.

This often happens because frameworks tend to make developing easier. So easy we forget to take a step back and figure out how all the pieces come together.

If the framework is modeled on the model view controller (MVC) pattern. The convenience trap for developers is adding unnecessary amounts of logic into controllers or models. It’s easy to do and get the work “done” and out of the way if no testing is involved. Generally the problem with putting unnecessary amounts of logic in controllers or models is hard to test which subsequently causes the application to be brittle.

For example:
Oh looky here something database related this needs to go in a model or hey this interacts with the user’s input this probably goes in the controller.

The framework should not be the application, but a portion that compliments the development.

Note: The above generally applies to larger apps and not small apps that may have a short lifecycle.

How to mitigate the framework convenience trap?

  1. Write tests for the application. If tests are written chances are the structure of the app is designed better.
  2. Learn software best practices.
  3. Don’t code in a silo. Talk to other developers.
  4. Realize no one has perfect code and let someone critique your code. DON’T TAKE IT PERSONAL.

Simple Techniques To Influence Your Future

The future is unpredictable, however many techniques can influence your future to put you where you want to be.

Knowledge Is Power

Educate yourself. Knowledge is power.


Personal and professional networks are invaluable. Put yourself out there, talk with people.


Become a great listener. Listening well is a difficult skill to learn, but can yield amazing results. Listen a fraction longer than what feels comfortable and you will hear things you normally wouldn’t. People love to be heard.


Read blogs, books or what ever sparks your interest.

Hard Work

Put in the hard work upfront and receive the benefits later.

Positive Attitude

Use a mistake to your advantage. A mistake can be a learning opportunity to better yourself. Check and adjust.


Go out there and seize the opportunity. Don’t wait for an opportunity to find you.


“You miss 100% of the shots you don’t take” – Wayne Gretzky

Lastly be true to yourself. Live your life with honesty and integrity. People will feel the aura that surrounds you.

Awesome list of free beginner, intermediate, and advanced programming courses

Programming is useful and important.

I like to compare programming to oil in that cars require oil to operate and business require programmers. If a business intends to compete most likely they have an IT team. Many times the competitive advantage for a company relies on technology. Most technology if not all requires software development.

Even if very basic programming interests you there are some awesome courses. Some courses are self-paced and some have deadlines.

Awesome list of courses

Consumer Power On Social Media

Believe it or not you have power in your fingers tips through social media.

If you’re a regular on social media then mentioning your favorite brands can be powerful whether the experience was good or poor. I’ve encountered a few poor experiences and each occasion I reached out via twitter. In most cases I received a response within a few hours and they have offered to resolve any issues.

It is a win-win situation. Any good manager will appreciate the good and bad. If the experience was not up to par hopefully the manager will provide an incentive to comeback.

Ultimately most companies don’t like bad PR. Generally large companies have social media teams that handle responding to customers. Information spreads very rapidly and it is crucial to resolve issues quickly before it escalates. Notably Comcast had disaster to clean up when one man posted his conversation with a customer service rep while trying to cancel his service.