Sad to read this from Jeroen Wiert Pluimers

Sad to read this from Jeroen Wiert Pluimers

https://wiert.me/2018/02/11/do-not-download-the-embarcadero-patch-for-rad-studio-10-2-2/#comment-408479

https://wiert.me/2018/02/11/do-not-download-the-embarcadero-patch-for-rad-studio-10-2-2/#comment-408479

Comments

  1. After Idera’s acquisition and R&D centers shutdown, including the Spain one, I was offered to be MVP but I refused, as I couldn’t think of a way Embarcadero could keep evolving the product and guarantee a minimum of quality. Even I still love the product, sometimes you have to be consequent with yourself and I couldn’t see myself defending the product against others. In my case, I’m just looking forward Embarcadero to be sold to another company that believes on hiring engineers to evolve the product. Fingers crossed 😁

    ReplyDelete
  2. If I had been an MVP now, I would have resigned from it. It is unacceptable to not be able to raise criticism. If Idera require a MVP to smile and be happy when the state of things are falling to bits, the title no longer has any value.

    ReplyDelete
  3. Not good. I really need to spend a few days with Lazarus to see if it’s viable for me. I don’t want to give emb anymore money.

    ReplyDelete
  4. My allegiance is with the product and not the company.

    I stand by all the people who put hard work into making it better over the long years, and I stand by them even when they were doing mistakes. Because, you do your best and shit happens.

    If I ever would feel that Delphi is not product worth supporting then I will pack my things and go home. Until then, I will stand by it trying to help in any way I can.

    And at the end I don't really care what people may think about the title, about my integrity or even me.

    Having said that, I am really sorry that Jeroen Wiert Pluimers is no longer MVP.

    ReplyDelete
  5. Please note: There is nothing wrong with being an MVP, but there is something wrong with Idera's idea of what an MVP should be able to do. I am not saying that existing MVPs are puppets, but that they SHOULD have the right to put the finger on things that are not right.

    ReplyDelete
  6. I also thought about becoming an MVP but the agreement would have prevented me from voicing criticism. I value the right to my own opinion higher than the access to free products, even though I still like the product.
    Of course that means that if I lose access to the products through my employer (who currently pays for my subscription) I will no longer be able to support my open source projects. I'm unlikely to pay for Delphi out of my own pocket. But, Hey, I've still got valid Licenses for Delphi 5, 6 and 7. ;-)

    ReplyDelete
  7. ... and 10.2.2 was my last renewal, if there won't be improvements (mostly on the quality of the product) I guess that I'll have to rely "only" on C# and C++. My idea is that they don't care about the quality of the product, they just want to add features (broken or not) so we can feed them with our subscription money.

    ReplyDelete
  8. It is obvious fact that Embaracdero suffers from poor leadership and that goes deep.

    Its general manager needs to be replaced with someone that can actually manage the products to bring back the quality that we have relied on for all these years.

    Until that happens we can expect much of the same.

    ReplyDelete
  9. And i say it again: Shame on you ... embarcadero.
    We don't get what we pay for!

    ReplyDelete
  10. Lars Fosdal I don't know what happened between Jeroen and Embacadero in this case, so I am not going to comment on that one here. On the other hand I have to step in to clarify some things regarding being an MVP and criticizing.

    Of course can an MVP criticize! We are in fact encouraged to give feedback on the product internally. The point here is the channel where this feedback is given. Each MVP knows about this policy beforehand and nothing changed here since starting the MVP program.

    There are a several internal channels for an MVP to discuss, criticize and suggest things. I don't want to give more details here, but the benefits of being an MVP are way more than the free licenses (in fact I have returned mine to be used for others, because I don't have a need for it).

    Becoming an MVP is weighing these benefits against the ability to publicly criticize. Public criticism would probably widen my public visibility (obviously), but the internal channels are more direct, more powerful and have more impact. There was never a doubt what to choose.

    MVPs do criticize, even if not perceivable in public. MVPs are involved and make a difference - often not as much as we would like, but we are working on it.

    ReplyDelete
  11. Do not wonder now. As an employee of the Catholic Church, you are also fired when you marry a divorced person. Isn't Idera a kind of religious sect?

    ReplyDelete
  12. People are romanticizing Delphi quality of the past. I remember Borland/Inprise/CodeGear/Embarcadero receiving lots of complaints for a few Delphi releases. And the better releases still had issues. Long time newsgroup readers know.

    Ralf Stocker In the Church's eyes, the employee would be married to two spouses without an annulment to one. Polygamy is a crime in the U.S.

    ReplyDelete
  13. Uwe Raabe In my experience, Jeroen Wiert Pluimers is a genuine nice guy, and I can't remember him ever raging in public in an unreasonable way - actually not even in a reasonable way - which make the whole debacle even weirder.

    ReplyDelete
  14. Lars Fosdal I fully agree with your perception of Jeroen and thus can't see any sense in this either, but as I said: I don't know nothing about this issue other what Jeroen already stated in his blog.

    ReplyDelete
  15. MVP is just like any of us, but with benefits (licenses, direct channels of communication, visibility, etc). Jeroen can continue (and he says, he will) adding value to the community, if he wants to. Also, I dont think he was doing it just for the licenses, so no problem there. Now, I read his blog, and I dont see any big damaging post, so whatever happened was over some other event which I cant see. I do think that there was no need to backslash at Emb. If they removed your MVP, done, you continue with your own licenses if you have one and if your interest is on the community, if it wasnt, then the MVP thing wasn't for you.

    ReplyDelete
  16. MVPs are encouraged to provide constructive criticism. I have a process in place where they can talk directly to product management with concerns, and many of them also talk to Atanas from time to time if their concerns warrant it. We also have regular briefings where we solicit their feedback. I personally field some of their concerns too.

    Not sure what happened to his Tech Partner status. This is news to me. I'll ask him for details on that.

    Even public criticism that provides constructive value for the community is allowed.

    ReplyDelete
  17. And just to clarify on the lack of communication channels in general ("having to rely on internal communication between the MVP network and EMB is not really a convincing option") in fact we have Quality Portal. This is where the original issue was filed promptly by a couple of customers we are grateful to (like anyone else who files bug reports) and we acted on it by disabling the download to avoid affecting others. So I'd say communication works.
    And criticism is well accepted, even when it is not factual. The hotfix was tested and installed on dozens of computers with no glitch. I have in on 2 machines. In same particular cases it doesn't work, though, and we are investigating it further.

    ReplyDelete
  18. Marco Cantù I see a disconnect between "dozens of computers" and millions of licenses sold. We have less than a thousand users, yet we test with a dozen test users first, then several dozens of pilot users, before the actual rollout, and we have a homogeneous environment. Delphi users, not so much.

    ReplyDelete
  19. Marco Cantù "The hotfix was tested and installed on dozens of computers with no glitch."

    Perhaps for the future, consider letting MVPs and Tech Partners (who will surely be affected by any problems in a general release) have a few days to test before throwing the update/hotfix over the fence? :)

    ReplyDelete
  20. Lars Fosdal you are most certainly right in terms of more testing... what seems enough it is never... we did only internal QA testing (the dozens of computers). Not a public, external testing, as we often do.

    From what we have seen so far, and we are still researching, there is no issue with the fixes, "only" with the installer that should copy the files in the right place. On some machines, it messes up. That's not exactly something you'd expect...

    ReplyDelete
  21. Eivind Bakkestuen I can also say that MVP/tech partners testing it is a good idea, and something we often do, but skipped for this hotfix.

    ReplyDelete
  22. Marco Cantù Please ensure I'm on the mailing list for such update/hotfix testing, as I can't seem to have received any messages on this particular subject for quite some time. Thanks!

    ReplyDelete
  23. Will it fix an installation broken by the first patch? Or do I have to reinstall?

    ReplyDelete

Post a Comment