09 September 2016
Get Your Codebase In Shape
It doesn’t take much reading in regards to rails before you hit the “Convention over configuration” line. In my early days of development I had little idea of what that meant, either in terms of implications or for concrete uses. Now when I see that, I immediately think of arranging files within your application, how everything has a place, and how putting things where they belong make it quick and therefore efficient to find the files that need to change, make those changes and then update specs or associated files easily. That’s less headaches, more features and happier client and developers at the end of the day.
08 September 2016
Why Focus on Efficiency During Development?
Time is money. If this was a movie and I was a learned monk, I’d leave it at that, turn around and walk away into the mist, leaving you on a journey to figure out the full meaning and implications of that for yourself. But this is a brain dump of where I currently am in how I develop, so I’ll go into the details of what I do to insure my time is well spent.
06 September 2016
Intro to the Intro
Roughly one year ago I decided to take up developing in Ruby on Rails full time. The reason I picked up rails was how quick it is to build applications out with it. Developing quickly and efficiently is a, if not THE, strong point of Rails as a framework. As such, I’ve put together a list of posts which I’ll write to dive into increasing your efficiency across the various stages of an application’s lifecycle.
26 August 2016
The Limitation of PaperTrail
PaperTrail is fantastic, but in every app I’ve worked on, there’s at least two classes of users:
User. Now, admins can change things and in some applications, users can, too. In business environments, different user classes may be able to edit your models. Any financial clients or ones with business sensitive information will want to keep an audit trail to see who’s updating what across the app. Out of the box, PaperTrail doesn’t support keeping track of multiple types of users. Good for us that PaperTrail’s provided us APIs to alter its behavior.
24 August 2016
Fast Server, Slow Browser
Here’s the situation: Your amazing developer team has rocked your world with caching and other optimizations to get data from your client’s Rails server over to the users’ browsers. Your monitoring shows requests that were taking a whole 80-90 seconds to serve are now only taking 1500ms (and all that time is actually spent transferring megabytes of html to the browser, actual data retrieval is ~10ms). These numbers come from a recent project I did for a client with production data. Now, to tackle the last piece of speeding it up… Chrome browser is taking MINUTES (6 minutes, actually) to fully build and render the page after it’s received the data. 100% unacceptable. Time to drop in some asynchronous data transferral and a specialized js library to keep things snappy client side!