2 challenges, one healthcare app, continuously delivered (Part II)
(This post is the second and final part of a two-part blog and focuses on continuous delivery. Previous postGiven that the healthcare environment has such strict regulatory requirements and legal boundaries it is a challenge in itselfto write good software that fits the bill. We also were looking to make this a seamless experience for our customers. Our platform was composed of a few parts: a mobile app that works on both iPhone/Android, web platform and an dedicated device that allows to integrate with out web platform for fast sync of data - in cases where a phone is not available.
2 challenges, one healthcare app, continuously delivered (Part I)
(This post is the first part of a two-part blog, I will focus on continuous delivery in the second part.)I spent the last 3 years in building and supporting an exciting HealthCare app - Glooko - which supports people with diabetes get a unified view of their health with a single click. When I started on it, I thought of it as another software application, but was about to learn a lot more. First, I learnt that Software is more useful when it can be applied to people’s health. Further, I learnt that Software is also more difficult when it applies to people’s health - well, rightfully so. Here I detail, what I learnt and why it makes sense to build it that way.
Rails Concerns for Serializers
Serializers for RailsActiveModel Serializers pack a lot of punch when it comes to dealing with objects. Theyallow you to use configuration that takes care of generating the proper serialization forconventional rails objects.Once your code matures to where finding reuse is not difficult, you may run into a situationwhere you want to leverage shared functionality via mixins. I ran into such a situation and wasnot able to find quick, clear documentation. Hence this effort to write it down.
Glooko - Diabetes Management Platform
Isn't 40 mins too long for a build?
Yes, our CI build on @thatsMingle takes 40 mins.Yes, @thatsMingle is a ruby application. Yes, @thatsMingle runs on Java using JRuby.
Pushing ElasticSearch logs to Papertrail
Do you have your elasticsearch logs going to your logs folder? Are you still struggling to get them to syslog so that they could betransported to a log-archive system like we did?
Mingle Loves GitHub
Mingle has a new look and feel, if you have not seen it already. In improving the experience we have also been looking at improving how Mingle integrates with the world.
Mingle Wall Reader - Sync your physical card wall with Mingle
Some time ago we built a hardware integration to Mingle. We did not talk much about it at that time. Hence this post to revive the talk about hardware interface with Mingle. Also about other hardware projects that were done in ThoughtWorks around 100days of hardware.
Ephemeral ports in Unix
We learnt something while installing our app on a Linux box. We chose port numbers like 36601, 37601, 38601 for a number of clones of this app. When we restarted the app we found that we were not able to start one of the clones on its assigned port(say 36601).