4 ms·
For me, it was in the attempted follow-up, "We told them almost impossible, too risky, do it for 2025! --- and they just didn't listen!" (real quote in [1]) My
by refulgentis 2y ago
For me, it was in the attempted follow-up, "We told them almost impossible, too risky, do it for 2025! --- and they just didn't listen!" (real quote in [1])
My alarm bells go off loud when people invoke tropes indirectly and lazily, hoping it'll influence my perception of a situation
DEFCON isn't the pointy-haired boss stereotype that needs you to deliver exactly $X, this quarter, with duct tape and glue. They know tech and wouldn't have talked a team saying they can't do it until 2025 into 2024.
Well, what if they really wanted it for publicity?
DEFCON had 0 stake in a new Raspberry Pi release, and Entropic self-reports they were the ones with early access to an unreleased product and decided it was the right vehicle. [2]
[1] We were clear as early as our first conversation in January that the risk in trying to push to mass production of this size and on this timeline was immense, even advocating for a DEFCON 2025 release of this particular badge. DEFCON’s Badge Team remained confident that they could meet and mitigate this risk.
[2] The specifics of what they requested in January were extremely difficult / almost impossible, but we had been working with Raspberry Pi as a Design Partner and had early access to the unreleased Raspberry Pi RP 2350, a chip that would enable exactly the kind of device DEFCON was requesting.
- aftbit 2y agoThat's kinda weird too, as DEFCON does electronic badges every other year, so they would not really be able to delay this project until 2025, but would instead need to delay to 2026 and hire a different vendor for 2024.