We specialize in creating innovative software solutions to complex problems.
Check out our new blog, Coding Commentary. We've had the privilege (and fun) of working with some extremely large code bases that have been touched by many different developers. The blog contains tidbits of knowledge gleaned from finding and fixing bugs that managed to evade detection for months or even sometimes years.
Recent Cargo Decoder Posts
-
ERG 2016 coming soon to Cargo Decoder
The 2016 Emergency Response Guidebook has been released. We are working to add the 2016 guidebook to Cargo Decoder and will issue updates to the app as soon as this ...
Posted May 2, 2016, 6:35 PM by Marsh Gosnell
-
Emergency Management magazine features Cargo Decoder
Cargo Decoder has been featured in an article in Emergency Management magazine. Tablets’ Mobility, Connectivity Lead to Adoption by Emergency Managers describes how emergency managers are increasingly relying on tablets ...
Posted Aug 3, 2013, 7:48 AM by Marsh Gosnell
Recent Coding Commentary Posts
-
Swift is swift!
Cargo Decoder Plus for iOS and iPadOS has been rewritten in Swift. I am very impressed with Swift and how much smaller and more maintainable the code base for Cargo ...
Posted Sep 17, 2019, 8:18 PM by Marsh Gosnell
-
Intellij IDEA vs. inertia
Inertia is a pretty hard force to change. As a long time Eclipse user, I found it pretty much met my needs despite a few reoccurring problems and cruft. Despite ...
Posted Aug 3, 2013, 8:34 AM by Marsh Gosnell
-
Google CodePro Analytix
When I work on C or C++, I turn up the compiler warning level to the highest setting because I firmly believe that a compiler warning is a bug you ...
Posted Oct 25, 2012, 8:07 PM by Marsh Gosnell
-
Build it Once, Run it Everywhere
Cargo Decoder is designed to run on just about every version of Android and on just about any Android device with a single APK. I presented the tricks and potholes ...
Posted Oct 28, 2011, 5:46 AM by Marsh Gosnell
-
equals is not your friend
I
fixed a bug in a Java application recently that took me a while to find because the code looked OK
but was fatally flawed. The statement
that caused all ...
Posted Jun 22, 2011, 5:29 AM by Marsh Gosnell
|
|