11–20 of 216 posts
Yet in my whole professional life I've never had a chance to do it despite putting the idea forward.
One of my old colleagues who managed to observe a client was met with hostility and questions from the people he was observing.
Other times clients want to dictate and have no dialogue in defining requirements.
Earlier quoted context omitted.
If you do learn the business, you have to explain to management why you wasted all that time. You cant say your application is cheaper in user errors, downtime, maintenance, licences, change requests etc... as that would mean all the other expensive software is garbage.
Domain expertise is not wasted time. It makes the difference between a useful application and a pile of code. Developers should not assume they know more about a business domain than the people working in it.
Earlier quoted context omitted.
If you do learn the business, you have to explain to management why you wasted all that time. You cant say your application is cheaper in user errors, downtime, maintenance, licences, change requests etc... as that would mean all the other expensive software is garbage.
Domain expertise is not wasted time. It makes the difference between a useful application and a pile of code. Developers should not assume they know more about a business domain than the people working in it.
Earlier quoted context omitted.
Domain expertise is not wasted time. It makes the difference between a useful application and a pile of code. Developers should not assume they know more about a business domain than the people working in it.
Isn’t that the job of a product manager, though? To figure out what the product should actually do?
Earlier quoted context omitted.
Domain expertise is not wasted time. It makes the difference between a useful application and a pile of code. Developers should not assume they know more about a business domain than the people working in it.
Isn’t that the job of a product manager, though? To figure out what the product should actually do?
As a semi retired software engineer and currently 4th year Med student, I still maintain a dream of building a usable EHR that puts the clinical, patient-focused side of things first. Currently implementations allow for increased billing recovery, but at a cost to both doctors and patients.
I just don’t know how you’d start in competing with something like Epic or Cerner, from a business side of things.
Earlier quoted context omitted.
Domain expertise is not wasted time. It makes the difference between a useful application and a pile of code. Developers should not assume they know more about a business domain than the people working in it.
Isn’t that the job of a product manager, though? To figure out what the product should actually do?
I’m not at all surprised. As a semi retired software engineer and currently 4th year Med student, I still maintain a dream of building a usable EHR that puts the clinical, patient-focused side of things first. Currently implementations allow for increased billing recovery, but at a cost to both doctors and patients. I just don’t know how you’d start in competing with something like Epic or Cerner, from a business sid…
I don't work with them anymore due to some fundamental differences (it's been almost a couple of years) but thought it was related to what you're talking about and possibly something you'd be interested in.
Possibly the only way you could compete with Epic or Cerner is to innovate on things in a way that can't be denied. It wouldn't be the first time slow giant companies fall because they did not advance, but it is much harder because the barrier to entry is absolutely enormous.
I worked a tiny bit over a year around 2013 at a hospital network and was on a team that maintained custom integrations with Cerner, an EHR system. It was by far one of the coziest jobs I ever had. Low stress environment, redundant meetings, etc. But development of any kind of god awful. It was extremely sluggish, lots of red type, and seemed to follow a manual QA approach over any sort of automated testing. Things w…
The jobs are easy, and you can go months without doing any real work whatsoever. The company might not even care (since for hospitals, sales cycles are often measured in years, and minor upgrade cycles are often measured in months).
But this kills any desire to do anything. Almost no developer with any motivation or skills, wants to work somewhere where they do nothing useful and have no real work to do -- even if the pay is good, you can literally feel your brain rot out, and you start to be worried you'll never get hired at a "real job" ever again.
It's just a bad cycle of events all around.