Entropic Engineering DEFCON 32 Statement
61–70 of 187 posts
Re: Entropic Engineering DEFCON 32 Statement
#62Earlier quoted context omitted.
It's complicated and the information is all over the place hidden in reddit comments, the whole thing is a mess
The firmware developer is really the one causing most of the problems. If not for him, this would have handled amicably between EE and DEFCON.
If not for him we would not know that there is a dispute between EE and DEFCON. DEFCON would be still pissed with EE that they went overbudget, and EE would be pissed that they were not paid what they think are owed. EE would also be pissed that their logo was removed from the case which (rightly or wrongly) they thought was part of their compensation.
Without his actions we would be none the wiser about any of it, but clearly the relationship would be anything but amicable.
Re: Entropic Engineering DEFCON 32 Statement
#63Earlier quoted context omitted.
It's complicated and the information is all over the place hidden in reddit comments, the whole thing is a mess
The firmware developer is really the one causing most of the problems. If not for him, this would have handled amicably between EE and DEFCON.
Re: Entropic Engineering DEFCON 32 Statement
#64Earlier quoted context omitted.
The firmware developer is really the one causing most of the problems. If not for him, this would have handled amicably between EE and DEFCON.
Does not appear to be the case? If not for him we would not know that there is a dispute between EE and DEFCON. DEFCON would be still pissed with EE that they went overbudget, and EE would be pissed that they were not paid what they think are owed. EE would also be pissed that their logo was removed from the case which (rightly or wrongly) they thought was part of their compensation. Without his actions we would be n…
He is some sort of poorman’s vigilante and even embedding an unauthorized Easter egg with a BTC address.
Re: Entropic Engineering DEFCON 32 Statement
#65Earlier quoted context omitted.
[flagged]
I do a lot of hiring, and the moment I have to take race, gender or sexual preferences into account, is the moment I will give a big fuck you. I will not discredit the competencies of anyone that I hired or will hire in the future.
At least that has been the case in the past sadly. So companies are now sometimes over-correcting by applying positive bias towards minorities
Re: Entropic Engineering DEFCON 32 Statement
#66Earlier quoted context omitted.
It looks like a case of managerial miscommunication. Entropic seems to have expected that sending emails with higher budget estimates would give DEFCON the opportunity to say no if they did not agree, and took the lack of response as a sign of DEFCON’s agreement to the new budget. DEFCON seems to have either not read or ignored those emails and expected Entropic to work within the originally agreed-upon budget.
In what line of work/business can you proceed to incur more expenses without approval from the paying client? This can't really be what they expected.
E.g. many craftspeople bull you by the hour and give you a rough estimate how long it could take beforehand. If the thing they are fixing for you has 3 more faults that you didn't mention to you, they will mention to you that it costs more and if they should proceed.
That is totally common, but the increased estimate needs to be communicated clearly and get an OK from the customer.
Re: Entropic Engineering DEFCON 32 Statement
#67Earlier quoted context omitted.
It looks like a case of managerial miscommunication. Entropic seems to have expected that sending emails with higher budget estimates would give DEFCON the opportunity to say no if they did not agree, and took the lack of response as a sign of DEFCON’s agreement to the new budget. DEFCON seems to have either not read or ignored those emails and expected Entropic to work within the originally agreed-upon budget.
In what line of work/business can you proceed to incur more expenses without approval from the paying client? This can't really be what they expected.
Jokes aside, we routinely work for clients without any contract. Contracts get finalized usually by the time a prototype (1/4 - 1/2 of the whole job) is done.
Corporate world is slow. They really like it when you come in and start delivering. Having something to show makes it easier for them to get the project green-lit.
There are obviously some reserves just in case it wouldn't pan out and I still feel quite uneasy. It works, though.
Haha, reminds me that the risk sometimes goes both ways. Like that one time we've got 100% paid for 1/2 the work and then kept working to finish the other 1/2. Can't betray that kind of trust.
(Not related to this drama. Just another data point from elsewhere. It's nice to see others to start working first and only call lawyers second.)
Re: Entropic Engineering DEFCON 32 Statement
#68Earlier quoted context omitted.
I was thinking it may have been something like that. But it's still shitty to a) wait until the project is complete to tell them they're not getting paid, and b) erase credit (I don't see any good justification for this. It's literally the reason they were getting a discount in the first place, and they went to quite some effort to do it)
They didn’t wait until the project was complete. They issued a stop work order due to being over budget and also some “bad faith” charges they noticed. DEFCON then sent their own team to handle the production run. Credit was not erased from the PCB nor the software, which were the parts Entropic was contracted to do. They declined to include entropic on the plastics, which is understandable given that Entropic didn’t…
And issuing a stop work order doesn't mean you can just not pay for the work done so far. It means you're not paying for any further work.
Re: Entropic Engineering DEFCON 32 Statement
#69Earlier quoted context omitted.
It's complicated and the information is all over the place hidden in reddit comments, the whole thing is a mess
The firmware developer is really the one causing most of the problems. If not for him, this would have handled amicably between EE and DEFCON.
> EE has tried multiple times over the past months to negotiate fair compensation for work completed prior to June 7th, but attempts at resolution have been unsuccessful.
> Once the manufacturing was fully completed, we were offered a one-time “take it or leave it” amount worth well under half of what we were owed pre-stoppage. Given that what we were owed was already discounted by 25% in order to hit agreed upon cost targets, this has had a huge impact on our small team. We are also still owed substantial sums for parts that we purchased on behalf of DEFCON for use in the badge. Again, all subsequent offers to negotiate a settlement in good faith have not received any productive response.
Re: Entropic Engineering DEFCON 32 Statement
#70Earlier quoted context omitted.
The firmware developer is really the one causing most of the problems. If not for him, this would have handled amicably between EE and DEFCON.
No. It might have been kept hush hush without the stunt, but there’s nothing amicable about it. > EE has tried multiple times over the past months to negotiate fair compensation for work completed prior to June 7th, but attempts at resolution have been unsuccessful. > Once the manufacturing was fully completed, we were offered a one-time “take it or leave it” amount worth well under half of what we were owed pre-stop…