Spencer Hirata

Welcome to my portfolio! This website contains information on my current and previous projects. Each panel is clickable to either the live site, or the github repository. Most of these projects were made while in school, so underneath is a legend for the symbols you'll see next to each project. If you're looking for my Resume, it'll be in the Navbar or hamburger menu above.

Code Fellows:

Launch Code:

Personal:

Arizona State University:

Click here to learn more about me!

Hey guys! Thanks for checking out my website!

I'm very passionate about putting my best work out there and using my full stack knowledge to create applications that better the world. Currently, one of my dreams is to startup my own software company that provides several patches to the holes I see within technology.

Currently back in school complete my bachelors in Software Development at Lake Washington Institute of Technology. I'll be publishing more projects here along the way.

My education really comes down to two coding boot camps, namely Launch Code(2017) and Code Fellows (2019). As with most coding boot camps, they focus their efforts to teach students current industry standards like GIT version control, Test Driven Development, the Github workflow, AGILE Scrum with Jira, proper modularization, working in teams of 4 or 20, etc. Of course, they also teach the most up to date technologies to prepare you for full stack, front end, or back end jobs. Three of my main projects on this portfolio come from Code Fellows, with two coming from Launch Code.

Auto Emailing System

As a front desk assistant at Adept Tax Services, I was tasked with contacting clients with outstanding balances. The invoicing technology didn't notify these clients enough, so that role then fell to me as a reoccuring weekly task.

With approval, I created an emailing system that scraped a report of relative data, cross referenced that report with a table of client email addresses to formulate templated emails that addressed the individual or organization and their amount owed. Following the live deployment, several clients whom haven't paid in several months had finally paid for Adept's services.

This panel doesn't click to the github repository because it isn't my software to give out. I'd be very happy to implement something similar for a different client if asked to.

Curve

With every Code fellows project, our instructions were to make something cool in a week. But this one was different, we were told to make a website that utilized a clickable circle that would change competencies and proficiencies of an individual. The idea of the application was to be a tracker of an individual's growth as an employee at a company or a student at Code Fellows.

As a joint team of C# developers and Javascript developers, our team of 20 experienced the ultimate industry mock we could have possibly asked for. Our C# team provided data that would fill up our circle as well as handle Authorization and deploy it to Azure. The javascript team was in charge of making GraphQL requests to the C# team's API, storing that data within the React Redux store in our Gatsby Application, utilizing Apollo's framework to make calls after the single page build, updating our several components with that information we just stored, while managing protected routes and providing documentation/tests to every javascript function in our front end. We learned maybe 10 new technologies as a team of 20 in a week, and still came out with a hell of a project.

We used Jira and had daily scrum meetings with our clients and integration teams. Again, this was as close to industry experience than we could have asked for. This panel clicks directly to the live link.




Hubbub Community

Hubbub Community is my most prized work. Through several cups of coffee and a lot of hard work, my team and I created an extendable NPM application that offers a client-server relationship. We designed the architecture for how a client should look, and how that client interacts with servers. Using web sockets in Node, a user would run our NPM package which would startup the client side application, which would then send them to our base application which is a chat app.

The chat app consists mainly of common chatting app features. Users are capable of chatting, instant messaging, making rooms, changing their nickname, etc. Again, using web sockets, we were able to accomplish a basic functioning chatting app. Very cool to try it out with your friends if you ever get a chance. Assuming you have NPM installed, copy and paste these commands in your terminal to run our application:

npm i -g community-hubbub
hubbub

The coolest feature about this project? Other Developers can expand the application. We structured this application to have a very simple client that emits one event, and listens for two. The server has to provide all the logic based on that one event emitted from the client(s). We made a template server to show how developers can contribute and add on to our application! Click on this pannel to see the github repo holding all the applications to figure out how they interact!



FE-RD Game

One of my more recent projects, this application is a game that calls out to my FE-API (listed below) for starting stats using Superagent. It is using the React and Express framework to server side render data to the browser. The game itself has fighting functionality, leveling up features, enemy unit difficulty progression, and a healing feature. Play the game for yourself and see how far you can get! Should look good on any device! The game might take a while to start up (20 seconds) because there are two heroku applications communicating with each other

Fire Emblem API

Some background to what this project is about: I'm a huge fan of Nintendo's Fire Emblem series. While I was in school at Code Fellows, we were told to use 3rd party API's for some of our classwork. One API we used a lot was the Star Wars API (SWAPI) which inspired me to make a Fire Emblem API. I want this project to be open source, where other passionate FE developers and I can build this project to the same level as SWAPI.

Migrate Life app

For it's time, it was a great node application. One of my three projects made at Code Fellows. The idea behind this application is to browse other locations in the US that you might want to move to in the moment. You would be able to select a region, that would then API call for a list of cities within that region. The list of cities that would come back would then make another API call to fetch more data specifically about the cost of living of several items, and the current temperature. All this data was then populated on the page, allowing the user to be able to make a choice of what city sounded good to them. Users were able to save their selection in the database.

Some of the biggest challenges with this application was managing all the data in our backend. We had to make one API call that needed a Lat-Long box, which made sense to have regions like North, South, East, and West. Once a user clicked on their desired region to live, the server would temporarily store that list of cities returned back, to then make dynamic API calls FOR EACH CITY RETURNED to a different service. That second call would then tell us several normal cost of living items you would find in that city. Getting the information was tough to begin with, but we added in the functionality to save cities that a user liked to be able to compare later. My team and I worked hard to make sure data was being sent in the right directions and were stored properly. Very proud of my team's hard work and our accomplishment of a great and (was at the time) functional website.

Unfortunately, even though this application was working at the time, one of the APIs has changed their free user plan. One of my members have recently shut down the live application, so it is no longer live. This panel clicks to the repository of this project.



ez-email NPM package

ez-email is an NPM package I had recently created that is meant for fast and easy code without going through the hassle of learning other emailing packages out there. Check it out by clicking here! (500+ downloads in the first week!!!)

AIMprove game

In the gaming realm, the first person shooter genre has been a hit for decades. I've always had urges to practice my aim, so that I would have advantages over opponents. This static webpage is that "practice mode" I've always hoped for. Though not graphically fantsastic, you do have to click your mouse within precise boxes in order to mimic hitting targets.

The reason why this has been overdue is my lack to integrate an actual database to this front end to keep track of scores. Eventually when this game comes out (hopefully soon, but 3 jobs kill your time), it will have database functionality and a timer on the game window.

Pachinko Game

I worked amongst a team of back end and front end junior developers to create a version of pachinko. The website is run using python flask (a python framework), that can handle get and post requests. In addition to python flask, we use another extension called PyMySQL which is used for database functionality with user login and top scores. The game itself was created using Phaser.io, a javascript framework. I contributed to the game framework, game design, and website design.





Box Game

"One of the best first semester games I've seen"

CS Professor

Definitely not anywhere near my greatest work, but the highlight of this app is more to demonstrate my progress as a developer and game designer from 4 years ago. For one semester of a computer science course, this was a grand achievement no doubt. I touched base on a library called pygames that popped up the game window and key inputs. Every key input would refresh the window of the new box position in game.

I could very easily recreate the application using React, but I would say the game is better having lived it's time :)

Blog Website

This is an older project that used Python Flask for backend routing and database queries. I used PyMySQL as the technology for integrating SQL into this blog website. Users were able to view all or specific authors, individual blog pages, create accounts and view protected routes. The website is not live, I would have to look at the code again in order to deploy.