Sales Insanity
-
username: royal_poet trust level: 2 (Not locked) In the last 100: Visits: 14/50 Topics Replied To: 11/10 Topics Viewed: 85/264 Total Topics Viewed: 1665/200 Posts Read: 56394/23181 Total Posts Read: 159822/500 Flagged Posts: 0/5 (max) Flagged By: 0/5 (max) Likes Given: 60/30 Likes Received: 420/20 Liked on Days: 45/7 Liked by users: 65/5 Status: Below requirements.
-
Why is there so much bullshit in this thread, Jesus. My own fault for trying to discuss the actual topic.
-
It's not removed... it's that version 6 of software A does not play nice with version 2 of software B. 7 plays nice with 2 and 6 is great with 1... just 6 and 2 results in a combination where 2 needs an additional software licence enabled.
Yay retardery.
-
because we're at td
-
That still doesn't make sense to me.
Ok, so your product is A6 and the other company's is B1.
You release A7 at some point, they release B2 at some point.
A6 doesn't work with B2.
... isn't that the other company's fault? Or... why not just tell A6 users to not upgrade B to B2?
But you have an update to A6 which allows A6 to work with B2. But you nominally charge for it? But you've been giving it away for free because customers have been upgrading to B2 without your knowledge I guess?
I must be missing something here, because it still looks like you went out of your way to break A6. (And I'm assuming B is from a different company-- if you also control B then it's even dumber.)
-
Embarrassingly, both A and B are ours. Result of some corporate merging. This is what makes this such a wtf. You'd think we would test our own stuff... prolly was forgotten as there is a new release every 4 months due to clinical safety concerns.
And yes, we knew we would break A6 - it needed done. It expected to receive certain data in an unsafe, non-compliant way. It's stupidly half-baked. It can receive data correctly, it's just that the software B interface was not set up for this initially.
Really, 2 should never have been sold as an upgrade there. But if it must be sold one should enable the licence and fix the configuration so it can send safely... but of course sales!
-
And yes, we knew we would break A6 - it needed done. It expected to receive certain data in an unsafe, non-compliant way. It's stupidly half-baked. It can receive data correctly, it's just that the software B interface was not set up for this initially.
Really, 2 should never have been sold as an upgrade there. But if it must be sold one should enable the licence and fix the configuration so it can send safely... but of course sales!
But you've giving the license away anyway.
Why not just proactively do it to all your affected customers? Don't even go through the sales department, just fucking do it.
-
Anyone but the German business unit (not part of Europe) is doing exactly that.
-
Send them a free licensed geography book
-
tempting lots of happy feels with that idea
-
How about executing a
SELECT email_address FROM customers WHERE country_code = 'DE'
and e-mailing the clients yourself, thus bypassing the sales drone?
-
lol.... we third line supporters have little access to such crucial information... but I sit next to a lot of senior people I can sick on folks. It has perks.
-
Recently, my company has been pushing to sell updates to the imager software that allow some funky things.
This made my skin crawl, and of course someone in here mentioned THERAC right away. And rightfully so.
Why the fuck should we upgrade something that works, and is capable of killing people either by accident, or by not working right?
because funky new features...
Can you absolutely 100% percent guarantee that absolutely nothing will stop working because of the upgrade?
no
Does this increase the quality of care for the patients in any way?
no
Does it require a massive investment in time and money from the company, and all employees, just to MAYBE get back to the level of service we were at before the upgrade?
yes
Fuck your upgrade.
-
This. And if it's security updates then airgap that shit.
-
@Lorne_Kates said:
Does this increase the quality of care for the patients in any way?
no
Funky updates would have a huge morale benefit.
-
-
Must share this one at work. That's ace.
-
If it makes you feel better I know of a health care middle-ware-translator-rator system written in Java that charges for SSL/TLS support but DICOM is free.
Clearly you Euro-weenies are doing it
wrongright(?).
-
Free and DICOM is usually a frightening combo. Just what DICOM is that implementing anyway, I get a nervous twitch these days when I read "fully compatible"....
I was in the bowels of a rtplan object today to check why 3rd party software doesn't process plans. That fully compatible pos gets confused when the plan intent is set to "CURATIVE" instead of "curative".
Gee thanks.
-
I can't say more than DICOM because I refuse to spelunk the shit code to find out more details. If it choked to death over a common but not-in-the-standard scenario I would not be surprised. I don't know how big they've made it on your side of the pond but they have had training session in London...
EHR systems shitting the bed over character casing does not surprise me anymore.
-
The thing with dicom is that its more of a guideline than a standard. everyone implements it differently and then supplies a cert of conformance to state what they actually did. So whenever something fully implements dicom... you can only shudder at what it actually does. The big vendors can't even decide on how they want to do UIDs. Do I have a leading 0 or no leading 0. And of course the patient pays the price in the end. I spend countless hours manually fudging dicom files a week so some system can process them. I love my trusty dicom editor.
-
-
Well noted.
Now when someone says, "But trans-late-amiddle-ware-aphire understands DICOM" I can say, "Yeah. And trunk has two different meanings in 'Murican and Queen's English. Think that won't happen between systems? Remember X and Y that 'talk' HL7?"
-
Fuck it, there are people I know that claim to understand English but are frequently confused by words. And shoulder aliens.
-
Hella Lossy 7. Always fun. We use that on our onc suite to interface with the HIS/RIS systems of the hospital. I dunno who I had recently anymore that managed to import all DEAD patients from their main system into oncology... guess they need radiation in their coffins.
-
-
-
Yeah don't get me started on Ethnicity/Race mappings...
"White goes to...C"
"Asian goes to...M"
"Black goes to...N...what the fuck?"
"Native American goes to...R...seriously? Racists ass honkies!"
-
What? Ace was awesome.
-
-
A competitors biometric fingerprint verification cannot tell Asian and Black people apart. It words fine on the whiteys, but that is it.
-
A competitors biometric fingerprint verification cannot tell Asian and Black people apart.
I am deeply interested in hearing about how a fingerprint scanner can tell your race.
-
-
-
Not seen the source code sadly. But from what I have seen onsite it works fine with white people, but then when another person tries to use it they are either not found or someone else of another ethnicity is brought up. Maybe something about the pattern? I dunno.
-
She's got some Nitro-9 ready to disagree with you.
-
Oi, Professor?
-
Does anyone remember which episode that was from? I'm pretty sure he was arguing with Jayne.
-
Jane, you ignorant slut!
-
"Well, Germany is not part of Europe. I don't see why I'd have to do this. It's a 20 000 Euro licence and I get a 0.2% bonus of what I sell. Not doing it."
Screwing
peasantscustomers over$€40d? Why, that's just theBritishAmericanGerman way!what? @deadmau5?
I don't think they were asking about your dinner.
```text
Flagged Posts: 0/5 (max)
Flagged By: 0/5 (max)Can someone be knocked out of TL3 for too many :badger: flags received?
-
-
-
Can someone be knocked out of TL3 for too many flags received?
No. The flags only count if the staff agree with the flag - for flags they're deferred so don't count.
-
NoYes. The flags only count if the staff agree with the flag - for flags they're deferred so don't count.FTFY
-
-
-
This is discourse.
THIS! IS! DISCOURSE!
{kicks a phpbb admin into a bottomless pit}
Um, actually, the pit isn't bottomless. We hardcoded a FLOOR to the pit because Real Users don't actually understand looping and bound checking.
THIS! IS! DISCOURSE!
{kicks a phpbb admin into a deep pit}
Um, actually, it isn't deep. I've never once EVER used a pit greater than 1 meter, so no one else should either.
THIS! IS! DISCOURSE!
{kicks a phpbb admin into a 1m hole}
Um, actually, percussive force via kicking isn't a feature. That's doing it wrong, kicking is for adjusting the height of a chair STOP KICKING WRONG! You're doing it wrong. KICKING is a UX hack for devs. Read the keybindings, we PUSH not KICK!
THIS! IS DISCOURSE!
{pushes a phpbb admin into a 1m hole}
Um, actually, permabans are not supported by Discourse, just set a date that's 1 year into the future and make sure you check that date before it expires and reset it for another year.
{phpbb admin steps back out of hole, starts doing things}
THIS! IS! DISCOu-- umm, what's going on?
phpbb admin: I replaced Discourse. It took me five minutes, and done.
{{user is banned permanently}}
-
-
@Lorne_Kates said:
Um, actually, permabans are not supported by Discourse
Weird, discodevs love banning and anonymizing and kicking people out.
-