For the third time since February, devCodeCamp graduates are working on a “Startup Weeks” project for Scanalytics, Inc. The first two endeavors were a smashing success, which has led to a growing relationship between the two startup companies. Even better, devCodeCamp graduates get an amazing opportunity to continue improving upon their arsenal of skills while working with real-time data pulled from the Scanalytics’ devices located in Ward4.
The first team of devCodeCamp graduates built an emulator that allows a computer, tablet, or mobile phone to simulate the SoleSensor-embedded mats used by Scanalytics’ clients. The second team of graduates built out a heat map visualizer using data collected by Scanaltyics’ predictive analytics platform.
The most recent team of graduates, which consists of Marissa Torres and Lao Vue, will focus on building a mobile web interface for Scanaltyics’ dashboard. The developer team will be responsible for choosing a web framework, improving the efficiency of authenticating a client user, and coding out views that will display relevant data pulled from the Scanalytics API on various charts and maps.
“Marissa and Lao represent the best of the best when it comes to devCodeCamp graduates. Their displayed work ethic, collaboration skills, and gained technical skill set made it an easy decision to put them together to work on a great project for an awesome company.” – Michael Terrill, devCodeCamp Lead Instructor.
Day 1 & 2
The first day of the Scanalytics Project Part III began with a kickoff meeting to ensure all parties were on the same page. The meeting included Marissa, Lao, Michael (project manager), and Scanaltyics CTO David Webber.
David’s enthusiasm mixed with the developers’ eagerness to get started brought a great energy to the room. After David walked through parts of the Scanalytics API and the developers got the necessary clarification on the project features, Marissa and Lao began to put together a game plan.
The remainder of Day 1 and the entirety of Day 2 consisted of research. The best way to learn is to dive into a project, which is why Marissa and Lao built a test Python Django application.
On the third day of the Scanalytics Project Part III, the developers got together with their newly gained knowledge of Python, Django, and OAuth 2 after a weekend of researching. The team beamed with confidence, ready to take on the project head first.
Marissa and Lao began the day accessing source code from Scanaltyics. From there, they made a virtual environment with Python and Django to get started on dissecting the source code and building upon the provided foundation.
As with anything else, the road to glory can be met with a few bumps along the way. The team powered through minor errors regarding displaying the login page. The small hiccup was nothing more than a learning experience, which would only set the team up for future success. Using provided credentials, Marissa and Lao were able to access the current dashboard as well as Scanalytics’ API to retrieve various necessary data.
After a successful Day 3, Marissa and Lao were ready to dive further using Scanaltyics’ API. Unfortunately, the team hit a snag logging in and being properly authenticated using their own personal accounts. However, the issue was resolved after a brief meeting with members of Scanalytics.
Using the proper credentials, the developers got full access of the dashboard and began their descent into getting the authentication working more efficiently for client users.
With Day 4 going a bit slower, the team has high expectations for the fifth day of the project. Their goals include adding code to provide more functionality for themselves as well as users. Along with that, the team wants to get a jump start on getting the views prepared for the mobile dashboard.
On Day 5, the developer team got into a groove and made huge strides on the Scanalytics Project Part III.
Marissa and Lao combined their use of proper credentials with their written code to view data of their created accounts after a successful log in. Upon entering the authentication token from the dashboard, the team was able to retrieve an array of data displayed via JSON format. With this information, the developers began to work on improving the efficiency of how a client is able to log into their own dashboard. Marissa and Lao wrote more code to enable a login that only requires a username and password, which eliminated the need of having a client user provide more information.
With access to the code written by the previous teams of devCodeCamp graduates for the heat map, Marissa and Lao began researching how they can work with the JSON to display data on various graphs. Along with that, how the displayed data will look on a mobile device was another area of concentration.
Day 6 & 7
The sixth and seventh days of the Scanalytics Project Part III were spent diving deeper into the project and adding code for more functionality.
Marissa and Lao spent Day 6 checking in with Scanalytics to give them a status report and get some clarification regarding some of the features. After a successful and productive meeting, the development team got back to work. The first task they accomplished was branching off a provided repository. From there, they began to add code for basic functionality to get the provided skeleton running. They also made the necessary adjustments regarding the navigation bar, as well as, adding a homepage.
Marissa and Lao spent Day 7 fixing the way clients will be authenticated on the dashboard going forward. They also spent a majority of their time working with the heat map repository (project that was built by devCodeCamp graduates on a previous “Startup Weeks” project). Once Marissa and Lao felt well acquainted with what they were working with, they began to work on the drop down for the sub location name. The development team then spent the rest of the seventh day researching the line graph to work with the JSON in order to display the data from the Scanalytics’ devices properly.
A majority of the work on the eighth day of the Scanalytics Project Part III was consumed by the heat map. Marissa and Lao continued to research how the heat map, which is written in Angular and PHP, works. It is one thing to step through code they wrote, but it is another beast entirely to dive into a coded-out project and understand fully how it is operating. The good news is they could begin to get a better understanding by researching the libraries and stepping through the code line-by-line.
One of the biggest issues Marissa and Lao did face was getting the heat map to run and display properly. The main reason for the issue had to do with Django not wanting to cooperate with Angluar as fluently as initially anticipated.
The two developers created a folder with all of the files from the heat map repository in order to create their own sandbox to work in. After much dissection and playing around with the code, they were able to successfully pull data from the JSON by running the heat map by itself.
On Day 9 of the Scanalytics Project Part III, Marissa and Lao made some huge leaps towards achieving MVP on the project.
After spending the morning continuing to try to get the heat map (Angular/PHP) to cooperate properly with the Django app, the two developers had a massive breakthrough. They were able to re-route each file with the correct file type, using an identified change in syntax to achieve the task. From there, they were not only able to display the heat map properly, but they also could use the JSON file with the grid as anticipated.
To the casual observer, it may not seem like a big deal. However, Marissa and Lao encountered a roadblock that had the potential to set them back at least a day. Instead of giving up, they remained persistent in their pursuit of identifying the problem and coming up with a great solution to solve the problem. All parties involved were thoroughly impressed with their achievement on the cusp of the final days of the sprint.
With a successful Day 9 behind them, Marissa and Lao turned their focus to putting the finishing touches on the heat map, as well as, testing the dashboard via the mobile web interface to ensure everything is working as Scanalytics expects.
The heat map, which was written to construct squares and repeat for all the data available rather than created as one 6×6 grid, needed to be changed. The main change was to go from one long array of data with style squares to actually being a 6×6 grid. On top of that, the developer team provided additional validation to not print X, Y, and C when no data is pulled through.
Marissa and Lao were able to test the mobile web interface by using an iPhone and Wi-Fi to successfully connect to the dashboard via the mobile device. After testing was complete, the two developers spent the rest of the day adding styling for the dashboard page and home page, as well as, writing documentation for Scanaltyics.