PHP package manager
Your product owner has an idea for a new sort of wiki. The wiki will be very simple, providing a short summary about the subject and then a list of links to related resources below the summary; the summary and the links will be user generated, all via an API you will build. You should aim to spend 2-4 hours on the task.
I truly despise these types of coding exercises.
I argued against supporting two separate platforms that accomplish the same goal. I argued for making the desktop site responsive to replace and sunset the jQueryMobile application. My arguments won the day.
Bite Squad’s goal at that point was to have a good, solid, manageable software product to support their business. They hired talented, experienced developers to do that. They realized somewhere along the line afterward that the effort was not worth it.
A lot of my time at Bite Squad was spent streamlining the food ordering process on our desktop and mobile websites. The foodify project was one of the most significant development efforts undertaken for desktop.
Since the beginning of time, collateral has been input into the LOS by means of a form that integrates with NADA. Due to the limitations of the NADA bookout service, new and rare cars are generally unacceptable to our system. The solution was to allow manual collateral input. Because we started collateral with NADA, the system was already somewhat complex, though some care was taken to abstract out the bookout type. Still, our solution had to expand upon that abstraction, particularly in back-end persistence and front-end KnockoutJS field bindings.
Snapshots are a fundamental part of how the LOS functions. The problem was that we were treating snapshots like second-class citizens. Time for a refactor.
There were somewhere between 15 and 20 bugs reported. The actual number of bugs was unclear because many of them were overlapping or interrelated. So for three weeks, I fixed bugs whack-a-mole style, fixing one, then another, then going back and re-fixing the original after coming back and finding it broken anew… over and over and over again.
In an effort to better document FG LOS software, primarily for developers working directly with the code, I was tasked to find a PHP documentation generator that would work well for our codebase. We were mainly interested in ease of use, but were also keen on a solution that offered decent default styling.
The user story goes something like this: As an admin, I want updates to FinanceGenius LOS admin settings to propagate to the customer-facing LG portal so loans funnel in seamlessly.
The fine folks at *terrible contractor we were using that I will not call out by name* decided that if a lead funneling in from LoanappGenius (LG) did not transmit to a client’s FG LOS correctly, a cron would try again five minutes later. With any application, things can go wrong. With LG, things do go wrong. I start by interpreting mysterious and totally ambiguous error status codes. If I haven’t hooked you by this point, keep reading anyway.
After botching my local Homebrew development environment, I decided to create a virtual instance to facilitate FG development. This way, no matter what crazy things I decide to do on my Mac in the future, nothing will affect my ability to contribute to the project. And if I screw up my virtual environment, I can quickly recover it. My documentation provided a template for the steps required to build a local environment programmatically using Ansible so that current and future developers have only to clone the software repo, download VirtualBox and vagrant, and `vagrant up` to begin coding.
