4 ms·
So the software is shit, like most special purpose business software. The tech's response isn't what justified the software limitations, it is the other way aro
by naner 16y ago
So the software is shit, like most special purpose business software. The tech's response isn't what justified the software limitations, it is the other way around. Nobody really wants to design or build this stuff so this is what they end up with. I've seen it hundreds of times. (I used to do consulting for small businesses and interned with an engineering contractor before that.)
- Semiapies 16y agoWe clearly need a way to make medical data systems sexy enough that talented, skilled folks build startups to try to horn in on the market. No, I'm not being flippant or joking. It would be a fantastic thing if even a handful of people see this story, go, "I could shit out better software then that!", look into HIPAA and other complications, consider a moment, then say, "I could still shit out better software than this," and get to work challenging the status quo.
- shrikant 16y agoT. H. I. S. I would narrow it down to "nobody wants to design this stuff" - in most enterprise software shops (mine, for e.g..), the 'sexy' jobs are either purely on the technical side ("let's code!"), or purely on the business side (account/relationship management). Nobody wants to to the bridge stuff - the actual hard work of translating the business requirements into a half-way decent technical spec that the "let's code!" group can get cracking on. And this is true from both the buyer and seller's sides. I suppose that this is because in such places, people's contributions are 'objectively' evaluated by either revenue generated or LOC, and the poor business analyst has no such conveniently measurable metric attached to her.