robocat 3 days ago

That is awfully close to blaming the engineers.

You don't know what kind of pressures they are under to deliver.

I know of significant compromises in all the software I have written, and I would make hardware mistakes if I had taken the electronic engineer path. Sometimes we have to prioritize and I've never had an unlimited time budget on any project (not even my own).

Projects with no issues are mostly dead!

  • aftbit 3 days ago

    Well high pressure to deliver is sort of a poor culture isn't it? I agree we should be forgiving of others mistakes, but I also think we ought to strive to develop better solutions that lead to fewer bugs at any given velocity.

  • db48x a day ago

    A poor engineering culture usually exists because management broke it, rather than because the engineers failed to create it. Of course I have no insight into how Elgato is run, so I am not pointing fingers. I merely state that there is certainly evidence that their engineers are not focused on quality.

KeplerBoy 3 days ago

How does the corruption point to a software engineering issue? What could cause corruption and how could it be avoided by better software engineering?

  • mschuster91 3 days ago

    It's a culture issue when such cases don't get caught in testing and support staff either doesn't know about it (=the scripts are bad), doesn't get told that there is a workaround (because clearly there is), or (the worst of the possible options) gets told to act like everything is fine.

    • crote 3 days ago

      It's a race condition which involves physical interaction with the product, which only occurs during a very rare operation, which looks pretty much identical to a genuine hardware defect.

      This isn't something you can just trivially unit test. If you don't see this happen multiple times during initial hardware development, you are never catching it. A single failure of a prototype can easily be attributed to a manufacturing defect - especially if it was hand-soldered.

      Once it's in the field replacing the 0.01% of units suffering from random issues under warranty is far cheaper than having an engineer spend weeks trying to diagnose every single weird failure mode. Unless it affects a number of units, it's just not worth the money. You have to consider that support doesn't get a "the LEDs stopped working when I unplugged the device immediately after flashing it" message, they just get "the LEDs don't work". Support scripts are made for horses, not zebras.

      • mschuster91 3 days ago

        > Once it's in the field replacing the 0.01% of units suffering from random issues under warranty is far cheaper than having an engineer spend weeks trying to diagnose every single weird failure mode. Unless it affects a number of units, it's just not worth the money.

        It does affect a number of units, that's the point, and it's serious enough that the brand image is suffering. Just google "elgato unreliable" - tons of results, and when the top result is a Reddit post in the official Elgato subreddit of all places literally titled "My elgato experience has left me with nothing but hate in my heart", all alarm sirens should go fucking off.

        To top it off, Elgato used to be a German brand right out of Munich [1]. German products used to be noteworthy for top-notch engineering and reliability...

        [1] https://www.reddit.com/r/elgato/comments/18k92zy/my_elgato_e...

        [2] https://en.wikipedia.org/wiki/Elgato