While the whole exchange must’ve sucked for them, I’ve found their reaction extremely amusing at times, especially the carpet banning for life of everyone within a country/state to the offending party. But hey, that’ll definitely show AMD how to hire those coreboot developers

  • floofloof@lemmy.ca
    link
    fedilink
    English
    arrow-up
    36
    ·
    edit-2
    14 days ago

    They complain about unprofessional communications then fill this article with whining like this:

    Weeks elapsed with little to no activity, because they were super busy pretending to be doing something else out in the abyss of phantom world.

    And they never seem to consider that maybe their own code wasn’t as great as they thought:

    He finally built the coreboot ROM with our code, flashed it, and tried to boot the laptop, which displayed an FSP message. Max said he was surprised it made it that far. Why? We told them our code just needed debugging, but they didn’t want to believe it.

    Why does the author expect it not to have problems? I know from experience that you can hand over your best, most thoroughly tested code to someone else and they’ll immediately find a problem you have never seen. How professional are these people if that surprises them? “But it just needs debugging!” is not the response of someone who knows what they’re doing and just needs a second pair of eyes on the code.

    In the end this blog post backfires. They paint themselves as an arrogant and problematic client to deal with.

    Edit: After reading the links in another comment on this thread (sorry for the instance-specific link, will fix if someone can advise me on a better syntax), and in this reddit thread this is evidently only the tip of the iceberg when it comes to Malibal’s behaviour. Definitely a company to avoid.