Gaslight Blog

Want to read more about Development? Let's take a look-sy:

02/04/14

5 Signs Your Business Needs Custom Software

Sometimes it can feel like huge corporations have all the advantages. But if you’re a small- to medium-sized business, you can give yourself a competitive boost with technology. In fact, investing in custom software development might help you solve a tricky business problem, boost your productivity or create an entirely...

Read More →

01/09/14

We're Presenting At CodeMash!

Chris Nelson Fri, Jan 10 1:45PM - 2:45PM Zambezi Room Component-Oriented: The Past and Future of Web Development Swing a stick in a crowded room full of web developers. You are almost guaranteed to hit someone who has worked with an MVC framework, and can probably name both a client...

Read More →

12/20/13

JavaScript, jQuery, and Angular Training (and Why Sharing Is Important to Gaslight)

Earlier this week, I had the privilege of joining SuperChris and 5/3 Bank employees in downtown Cincinnati for a JavaScript workshop. I was asked to come along to film the training in case other employees wanted to watch it later. As a design student, I was lucky to attend the...

Read More →

12/17/13

Mitigating Risk Through Technical Spikes

Our customers frequently come to us with an idea and, under tight time constraints, we need to validate that we can develop a component using a technology that we’re not entirely familiar with. It is impossible to keep up with all of the technologies out there and at Gaslight we...

Read More →

12/12/13

What the US Government Learned About Software From the Healthcare.gov Failure (And Some of Us Already Knew)

Part One: The Bad On October 1st, 2013 the U.S. Department of Health and Human Services released the Healthcare.gov website. The portal was intended to draw and enroll an estimated 7 million users over a six-month period. The release was a huge failure. Problems with the site were so bad...

Read More →

12/10/13

Maintainable and Scalable Systems with Rails Engines

We recently realized that this site (the one you’re reading right now) was getting a little too large to remain sustainable. We noticed that large parts of the app provided completely separate fuctionality and didn’t really need to communicate with each other. Maintaining these separate parts as a single monolithic...

Read More →

Like what you're seeing? Let's keep in touch.

Subscribe to Our Newsletter