So the SCC just hired a new IT guy and he is busying himself upgrading their website.  Mostly it’s just downloading and installing upgrades and new software, but he says there are things that jQuery can do to reduce the load on their server.  By folding a few things into AJAX calls instead of full page loads, not only will it be a better experience for the user, it will save them on bandwidth costs with their ISP.

He says that in this domain, because Assets cannot be created or edited by users, they will be the best candidate for moving forward with the SCCAPI rollout.  He’s convinced that an API will help the community somehow.  Whatever.

The first snag he hit was with the interference in the Javascript environment caused the TurboLinks (automatically installed with Rails 5).  After much confusion and some googling, jquery-turbolinks was discovered and implemented.  This one comes with a small price though: our JS will end up running on every page.  The time/memory it takes will be minimal, but we have to watch where we step to make sure we don’t get into crazyland.  TL;DR: Turbolinks caches everything in the world to speed up navigation for the user, but doesn’t bother to help the javascript (re)run, but jquery-turbolinks fixes that.

Onward.

I think the hardest part of projects like this is pretending their real.  A paid job with an actual product is an entirely different world from a dreamed up domain model with the intent of nothing more than technical exercise.  Coming up with excuses to use certain programming features is a terrible way to move a product forward (or make any money for that matter).

Financially, as well as technically, speed is my main concern.  Flashiness is subjective to the client, functionality is subject to the market/competition, all that matters is finishing.  That is my goal, that is what will move things forward.  Don’t judge me.

Advertisements