Terms & Conditions | Privacy Policy
Fire. *
It can shine forth as a candle lighting the darkness. Or it can burn everything in it’s path, leaving only ashes and ruin.
How does your team handle fire drills? When things go bump in the night (or smack dab in the middle of a work day), is it an opportunity to shine? Or just a tempestuous conflagration that destroys attitudes, team unity, confidence and business value?
I had the opportunity to “fire-test” our tech team this week. At HealthTalker, we are working toward running our entire infrastucture “in the cloud” using Citrix’s XenServer platform. Cloud computing provides all sorts of useful infrastructure features that make our platform that much more robust.
One component of this infrastructure is having SAN systems set up to ...
This post has 0 comments. Make a comment.
I’ve spent a fair amount of time the past few weeks working out the kinks in our development workflow. By “working out the kinks” I include “creating”, since there was no real workflow beforehand, at least not any formalized workflow. We use source-control solutions to manage our codebase and multiple environments to formalize the testing and quality assurance of our code. We are moving towards greater test coverage and will eventually include CI (continuous integration). We have a defined process for how client software moves through the environments. We are building out utilities to make the workflow simple and as error-proof as possible. We likely will institute constraints on who can move code where, deploy code, update certain ...
This post has 0 comments. Make a comment.
You may have heard of the software and business principles DRY, KISS, and the 80/20 rule. Excellent philosophies, each, but have you heard this one: Don’t Borrow Ahead Trouble. I’m not sure I can claim invention of this principle, but I certainly can claim the value of it.
What do I mean by “Don’t Borrow Ahead Trouble”, you may wonder. Let me briefly explain by referring to a real-world case I wrestled with here at HealthTalker.
HealthTalker made the decision a while back to partner with Bronto as our email campaign provider, leveraging their extensive API for communicating between our systems and theirs. We build solutions using the Ruby on Rails(tm) framework. Unfortunately, Bronto does not include an Ruby libraries, so the integration ...
This post has 8 comments. Make a comment.