This article makes me wonder about comparative analysis against other models and brands. It is good Sig Sauer produced a failure mode analysis. Where are the competitive analysis documents?
It also makes me wonder if the reason it can't fix some of these issues is because it is working around patent issues.
It appears based on some other court documents that Sig with the P320 intentionally excluded a trigger tab safety based on marketing decisions to be competitive, which every other striker-fired handgun has included. That along with some other issues appears to be the basis for where the P320 design went wrong.
> This article makes me wonder about comparative analysis against other models and brands. It is good Sig Sauer produced a failure mode analysis. Where are the competitive analysis documents?
Presumably buried in the woods along with whatever shenanigans went down to award XM17 to Sig over Glock without going through the full predescribed testing in the first place
The reason they can’t fix these issues is someone in leadership likely literally has Narcissistic Personality Disorder, and is quite literally incapable of acknowledging a mistake or problem. To the point they’ll inevitably torpedo the company rather than take any ownership or responsibility.
If the Board is smart, they’ll fire the person before it gets to that point - but if they were smart, they probably wouldn’t have hired the type of
person to get them into this mess in the first place.
What is the personality disorder that makes someone with no medical training believe they can diagnose "likely" mental health disorders in Generic Executive in a company they have no direct relationship with?
What is the personality disorder where someone refuses to consider the possibility of something happening despite a public and long term pattern of repeated behavior which matches that possibility occurring, unless some otherwise impossible bit of evidence from an expert who has a duty to never talk to them about it weighs in?
That's not really an Occam's Razor conclusion. I would say the reason is that multiple lawsuits were already filed, and to admit the gun was defective essentially means you lose all the suits overnight. At the time, they chose to ride it out because they didn't know how many of these guns were actually defective.
My guess is it was a perfect storm where the defect rate was low enough to escape their quality control but high enough (or perhaps delayed long enough, meaning it takes years for the defect to appear) to lead to a clear signal after the horse got out of the barn. Enough suits were filed that they perhaps risk bankruptcy if they lose all of them.
That's just my speculation, and seems to be more plausible than some side effect from mental illness.
That was less than a year ago, and well after these issues have been escalating for years.
The co-ordinated gaslighting, projection, denial, etc. are also a clear pattern going back years as well.
The employees clearly being aware there are issues and being afraid to speak up due to internal retaliation, the lawsuits against entities merely trying to protect themselves from preventing people from carrying P320’s into their facilities until this gets figured out, etc. as well.
No one goes to this amount of effort to deny they have a problem (and control others to prevent them from acknowledging there is a problem) without an impetus like that.
I’m not saying the underlying engineering problem is a result of a mental health problem with someone in leadership. Though it likely doesn’t help!
I’m saying the market problem SIG is having (and the serious consequences of it) are due to the mishandled response to a real issue in engineering/manufacturing in a way which stinks clearly to me of NPD.
It’s the doubling down, attacking anyone who notices a real issue, gaslighting everyone, etc.
Hell, when even Brandon Herrera is telling them to fuck off due to the gaslighting?
It’s epic in this case. And NPD folks have a nasty habit of ‘taking down the ship’ as they escalate. It’s damn near the defining consequence that makes it a personality disorder.
Which SIG is definitely heading in that direction.
I agree that the tone was really awful and hostile. I'd give the company a 50% or less chance of recovering from this.
A few months ago I read a story about a woman who worked at sig and was sexually harassed by her boss and was demoted and fired. I can't remember if she was involved (as a witness) in an injury lawsuit about the P320 or what, but reading her story made me remove any possible sympathy I could have for her. Makes me sad I bought my P365 even though it's a great weapon.
> someone in leadership likely literally has Narcissistic Personality Disorder
What a wild, unjustified claim. Not every arrogant fool has NPD. If you want to throw that claim around you best be ready to cite the clinical definition.
The clinical definition where someone is unable to recognize any fault or problem in their behavior to the point of severe pathology, and delusion, including attacking or manipulating others?
Have you seen the press releases and lawsuits? It’s quite literally crazy what they’re doing.
And executives set the culture of a company, and someone with the described personality characteristics are particularly prone to enforce that type of behavior on an entire companies culture.
I’ve seen it play out quite clearly before in person.
Why work so hard to continue to avoid the actual issue and clearly present behaviors and facts?
Or do you think such persistent and blatant pathological behavior just happens naturally from otherwise well adjusted executives acting in good faith?
And clearly since you've seen it play out that way, there are no other possible situations that could result in similar behavior. The possibility that a public admission of fault could play a role in ongoing or future lawsuits definitely doesn't have anything to do with it. Nope, only one conceivable motivation for hiding the truth, which is conveniently located in a single guy, who is definitely not just a run-of-the-mill arrogant fool.
I take it you haven’t actually read the linked posts from SIG? Read them and then tell me I’m wrong.
No lawyer or PR person in their right mind would EVER okay that type of response. And with the facts as we know them coming out, those responses were deeply pathological.
You know, I actually hadn't, but they were nothing I didn't expect. Of course they were lying. Lots of people without NPD lie. They were in a hole, and they thought digging was their best way out. Playing on fears of gun-grabbing is a plausible if clumsy angle to take. If their design had been less borked, they might even have gotten away with it. That's why lots of unethical but otherwise grounded PR types have historically okay'd this kind of thing.
You can debate whether they're still "in their right mind" by your preferred definition, but it's increasingly preposterous to say their behavior is evidence of an executive with NPD. This is just not that special, dude. People are just like this.
Uh huh, sure. Definitely nothing particularly spectacular here at all.
How many gun companies have had this level of scandal again? The only one I can think of is Taurus in the 80’s.
Doesn’t sound normal at all, actually.
What really amuses me about these kinds of conversations is how invested people are in insisting that when it walks like a duck, quacks like a duck, is at the pond with the ducks, and looks like a duck - it totally isn’t a duck, because… I don’t know. They don’t like ducks? Or ducks are boring?
Oh, it's pretty spectacular. Just not evidence for NPD. That was your thesis, right, this very specific clinical diagnosis? Do you still remember that? You desperately want to believe this bird you found at the lake is a rare, special species of duck, but it's just a mallard.
And in that case, the problem would not be discovered until 1) someone opened a bug report, which rarely happens, because any competent user would just disable auto-updates, and 2) that bug report would be investigated, which also rarely happens.
Buttons on a microwave are like features on a car (or in a software program). Great for comparative marketing, but do you really need all those features? Do they make it better?
I bought this microwave, currently $74.97 and even my six year old could use it. I'm not blind, but I can't imagine why anybody needs all those buttons. I bought this because it saves me a couple seconds every time I use it. It is a better, simpler design, cheaper, and appeals to my favorite design principle: "what can we remove to make this better?"
The only downside is that the electronics and mechanical parts are not built to last. But that's generally true of the expensive microwaves too, and they have more things that will break rendering the whole thing useless.
https://www.amazon.com/dp/B00BGTNY8O/
Great for comparative marketing, but do you really need all those features? Do they make it better?
Depends what you value. Sounds like you are optimizing for speed of input, so a couple dials are going to be the best option. I like digital for the precise input. I throw a slice of cheese in for 8 seconds because I know that’s how long it takes to get it from cold to to room temperature. It’s a little harder to pick exact, short times on a dial. It is more of a trade off than one type of control is inherently better.
I actually really enjoy the sensor cooking on my microwave. Single press reheat button, defrost by weight works really well, specific food cook modes are spot on (potatoes, popcorn, frozen veggies, chicken). Like, would you not want to just press a button once and have a, evenly cooked chicken breast? Or just put some frozen veggies in a bowl, press a single button, and they're nice and steamy every time?
Frankly, what does "designing hardware as a EE" have to do with software issues your parent has described? Pine64 sells PinePhones, but doesn't do any software development, not even kernel drivers. That's not "failure", that's the expected outcome. You got what you paid for. The community does an amazing job supporting the hardware, but there's only so much you can do with self-motivated volunteers on such a complex project.
There are other projects out there where you pay for both hardware and FLOSS software development, such as Librem 5 with PureOS.
EE here. Not really about admin/IT. But I do wonder sometimes if I should have done software as a career. Mostly it's a grass is greener feeling when I hear about the high end of the salaries. But I do very well financially, the jobs are stable, and I write cool software to solve my own problems, rather than grinding on someone else's Jira tasks. I do lots of IT and computer admin stuff too, but also on my own terms. Setting up simulation clusters, remote hardware automation, development environments, storage, etc... so much so that our department hired a guy to take on some of that work.
Another EE here. I suspect that there is a lot of "greener grass" going on (oh look! I spy with my little eye, grass beginning with G). I've been doing software dev for most of the past quarter century. My current hobby is Eurorack synthesis and I build/solder about half of the items from DIY kits. The ones that I'm mostly into are built around STM32 microcontrollers (I threw out all my C/C++ books about 15 years ago - oops!).
I can't find info on what radio you used. Code like this would be more fun to see with links to the hardware design. Is any of the design documented and published?
It was https://www.amazon.com/gp/product/B0768WQ989 but it cost significantly less than that at the time - there's a whole bunch of compatible devices. Basically anything that has a UART at one end and a USB adapter at the other end would work, but we chose something in the 915MHz range because the 2.4GHz spectrum on location is just lousy and it's not in the range that most teams run controllers so it wasn't likely to interfere with that either.
99 times out of 100 when I think I might need a regular expression, I find it far better to code the search in python directly rather than using the regular expression engine at all. It's far easier to understand and you can run a regular debugger on it and use regular comments. In the 100'th case, I'll code most of the expression in straight python and a very small piece using the regular expression engine.
By straight python I mean things like 'for', 'split', 'startswith', 'find', and regular character indexing.
So for me this post is a solution to a problem that I just avoid.
I still use YNAB4 regularly. I have a paid copy from before they moved to an online model. I'm running it on ubuntu in wine. It still works fine.
I had never heard of Actual till today. It looks like it would cover my use case. I'm not sure why I would have switched, though, as YNAB4 still works for me and has no recurring charge and is fully local.
I'm in engineeering at a major engineering company historically using simulink and matlab. Python took over here in large part because matlab licensing caused so much friction, and we wanted to scale the simulink and matlab models up to run on a cluster of machines. We wanted to give scripts to people without matlab licenses quickly. etc. It was not the cost per-se, but the red tape.
We also ditched simulink because it is very difficult to version control and collaborate with a graphical interface.
Matlab is pushed heavily in the schools so all the engineers knew it and were comfortable with it. Matplotlib and numpy mimicing matlab very closely allowed the transition to be easy. We're not looking back. Only a handful of people still use matlab for their individual work because the python camp hit critical mass and the transition is not hard.
Matlab working to control serial ports, ethernet, visa/gpib instruments, all without the friction of getting extra licenses was icing on the cake. Matlab has a buy the cadillac model: the wheels, doors, hood, gas cap, mirrors are all optional add-ons. Each point causes friction, as only a few people had the whole tool, and therefore nobody could reliably share code.
It also makes me wonder if the reason it can't fix some of these issues is because it is working around patent issues.
Pure speculation.