4 ms·
I believe DEF CON on this, because the other side of the story --- that they vindictively withheld payment from Entropic and later harassed the firmware develop
by tptacek 2y ago
I believe DEF CON on this, because the other side of the story --- that they vindictively withheld payment from Entropic and later harassed the firmware developer --- just doesn't make any sense. We are probably talking about rounding error sums of money for the conference organizers themselves.
- gavinhoward 2y agoNational politicians have taken bribes for less.
- woodruffw 2y agoNational politicians have legible incentives. What’s the incentive for DEF CON here? It’s not like they’re apart from the community; people know exactly who they are, and the existence of their conference is tied entirely to the community’s perception of their leadership.
- JonChesterfield 2y agoPeople do petty stupid things. My priors align with the client having unreasonable expectations and then squabbling over the inconsequential bill. That is totally a thing that clients sometimes do.
- tptacek 2y agoHaving spent a very long time as a consultant, a thing vendors sometimes do is commit to unrealistic project schedules and then attempt to invoice their way out of the hole they've dug for themselves, and by "sometimes" I mean "every times, every of the times", it is one of the most common ways consulting projects blow up. When your project blows up, the professional thing to do is to resolve the problem with the client before billing another hour over the SOW. The common, crazy thing to do instead is optimistic invoicing: the client must share our priors, we're all reasonable people, so we'll just implicitly revise the SOW to match our learnings on this project and proceed, prioritizing what we believe would be a successful delivery of the project over everything else. That rarely works. Serious consultancies routinely eat billable weeks of time in order to meet client success criteria and retain relationships.
- ainonsense44 2y agoWhat's "SOW"?
- maxbond 2y agoScope of Work
- jdlshore 2y agoI’ve always seen it as Statement of Work, but either way it defines the work that will be done.
- kailden 2y agoI read it as “Statement of Work” which is description of the work to be performed/delivered, although often much more general than a full technical specification, sometimes in a comedically tragic way.
- squigz 2y agoHow much money do you think the DEFCON organizers make?
- tptacek 2y agoTheir top line is 8 figures annually.
- squigz 2y agoDo you have a source for that?
- Rebelgecko 2y agoSeems reasonable just looking at number of attendees * cost
- tux3 2y agoThe groans you hear on Reddit and social make it sound like this isn't DEF CON's first time finding itself in this kind of kerfuffle with a contractor Why reach for a stop work order if the whole thing is a rounding error. Entropic seems like they were able to finish, except that cost was an issue
- mvdtnz 2y ago> Why reach for a stop work order if the whole thing is a rounding error. My interpretation is that the project was at risk of not being delivered. No doubt Entropic had made and broken many promises leading to the stop work, and at some point DEF CON needs to take ownership of the project in order to ensure delivery.
- refulgentis 2y agoFor 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.
- ryandrake 2y agoThe whining in the Entropic's statement about how "extremely difficult / almost impossible" the project was is what gets me. Come on--you're grown-ass adults that signed a contract to deliver X work by Y date. Nobody cares how hard it was. I've been on the other side of the coin many times, managing a small vendor who's in over their head, and I try to have empathy, but where is the project manager? Where are the milestones and checkpoints? They didn't suddenly stop-work out of the blue. I'd guess multiple checkpoints were missed, and everyone knew this was coming. And that’s not even mentioning the Easter Egg! Good grief!
- jdnsndn 2y agoExactly. A badge is not really rocket science, there are no real hidden risks. I read about the $20 target price, which I find quite hard to reach, but that is something you know before you agree to deliver X by date Y costing Z
- InsideOutSanta 2y agoI think the issue is that they got used to pulling a rabbit out of a hat with their badges. The budget they have for them is apparently ridiculously low, and it seems like sheer luck that it somehow worked out in the past. At some point, defcon must have confused luck with skill. Meanwhile, others paid the price for that by working "for exposure." This year, it blew up in everybody's faces. Whose fault is it? Defcon, for having unrealistic budgets? Contractors, for taking on an unrealistic project for the prestige? IMO there's plenty of blame to go around.
- M4v3R 2y agoI would say the fault is on the both sides. Defcon being so big knew that someone will pick up their unrealistic budget. But it’s still the contractor’s fault if they took a project with full knowledge of its scope and agreed on the price, and then did not deliver.
- tptacek 2y agoThe whole point of being the vendor is that you're the party with the expertise to know what is and isn't a realistic budget for a project. Clients ask for unrealistic stuff all the time; part of your job is saying "no".
- lukan 2y agoWe are not talking about a ordinary computer nerd - newb buisness relationship here.
- trte9343r4 2y ago> After going overbudget by more than 60%, several bad-faith charges, and with a product still in preproduction, DEF CON issued a stop work order. My reaction was "only 60% over budget"? This is a low volume custom computer. The way Defcon pushes promotion and recognition, I do not think they paid full commercial price.
- 2y ago
- Sakos 2y agoI don't understand why DEFCON deserves the benefit of the doubt, but Entropic and dmitry don't. Here's Entropic's response: > 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. > Once a month, we billed for our work and submitted an updated estimated per badge final cost - committing as costs built to discount our work as necessary in order to hit DEFCON’s per unit cost targets. > In June, after 5 months of late night work, badges were fully designed, prototypes were working, and mass production was ongoing with the manufacturers we contracted on behalf of DEFCON. We billed DEFCON for our most recent work, discounting our labor by 25% in order to meet the agreed upon targets. Unfortunately, we were instead met with a work stoppage request and informed we would no longer be paid for services already rendered. https://www.entropicengineering.com/defcon-32-statement https://www.entropicengineering.com/defcon-32-statement It feels to me like DEFCON is relying on being able to say "well, we're DEFCON" when defending themselves, and people like you are just blindly trusting their word. How many times have big organizations like this screwed their suppliers? And yet DEFCON is "clearly" innocent? You must be joking. At least wait until we get a better picture of everything before deciding on a judgment of any of the parties involved. It's going to take time before we find out what actually happened.
- tptacek 2y agoDEF CON is making a falsifiable claim, that Entropic blew their budget and billed outside the SOW. Entropic is handwaving (who gives a shit what RPi hardware they had access to?). I'm not in DEF CON's corner generally but my priors as a consultant lock in pretty solidly on this being a consultant fuckup.
- debugnik 2y agoEntropic says their bills were discounted to still meet the per unit cost target. Isn't that a falsifiable statement that contradicts Defcon?
- 2y ago
- robxorb 2y agoThat a mostly-finished, working project of this complexity ends in fiasco can't be the fault of the contractors. What failed is communications - and apparently only on one side. Both Entropic and Dmitry were shocked by this outcome; not communicated with.