©
HealthTalker, LLC.
63 Chapel Street,
Newton, MA 02458. All rights reserved.
Terms & Conditions | Privacy Policy
Terms & Conditions | Privacy Policy
I had the unique privilege to go hear Seth Godin speak in downtown Boston a couple weeks ago. As a recent convert to the Seth-Fandom tribe, it was quite a treat to hear him live and see what he’s really like. I was not disappointed.
Seth took the audience on a brief catch-up of his books and how the story weaves through them. He ended up by talking a lot about the concepts from his latest book: Linchpin. If you haven’t yet read it, I highly recommend it. It’s a refreshing look at what it means to work passionately.
After speaking for a bit, Seth opened it up for question and answer time. I took the plunge and asked one: “You speak about the need to ship as well as the goal of treating work as art. How do you deal with them when they are in ...
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 7 comments. Make a comment.
Observations, commentary and perspectives on word of mouth, life in a start-up, and the challenges of the pharma industry.
