2,131 karma · joined March 19, 2024
Not only that, the cases presented are likely better dealt with via inference tests. But the author's knowledge doesn't extend that far. And even going as far left, the posed question isn't even defined in the article. So how was a suitable methodology chosen? Well it wasn't - lets just throw this pretty picture up and whine about it.
The author is way out of their depth and should retract the article and take a formal, accredited statistics course.
People waltz in with assumptions and then complain when they don’t work because they don’t really understand the tools they are using. The author is one of them. It’s a bad article and the author should not be using or demonstrating things they clearly don't understand.
They are mostly useful for comparing batches not analysing an individual batch.
The author doesn’t know what they are talking about and is telling people as if they do. If he read any of Tukey’s material he might know. But no name dropping is enough clearly…
We have one service which has gone back to a Go program that runs locally using go run. It's then shipped in a container to ECR and then to EKS. The iteration cycle on a dev change is around 10 seconds and happens entirely on the engineer's laptop. A deployment takes around 30 seconds and happens entirely on the engineer's laptop. Apart from production, which takes 5 minutes and most of that is due to github actions being a pile of shite.
Notably one of our biggest security threat vectors is actually Windows. The security model on it is so crap it's either locked down so it's completely unusable via GPOs and behind DLP proxies and firewalls. Or the risk is accepted and as a regulated industry we get fined to death if anything goes wrong.
So no we aren't happy, we don't trust them but we have to gargle it anyway.
This is another Windows Phone. They shaft the entire platform for a decade to fulfil some stupid fucked up half baked ideology.
Imagine Windows if they invested in their customers rather than their stock price and ego. Imagine if they became a bastion of privacy and security. Imagine if they became someone we could trust.
The point is there’s a methodology to solve these problems already. Is this better? And can it use and apply it?
Edit: no VSWR constraint. Can add that later :)
Edit 2: oh or design a board for a simple 100Mohm input instrumentation amplifier which knows what a guard ring is and how badly the solder mask will screw it up :)
I have my own library of nuances but how would you even fine tune anything to understand the black box abstraction of an IC to work out if a nuance applies or not between it and a load or what a transmission line or edge would look like between the IC and the load?
This is where understanding trumps generative AI instantly.
AI happy as it worked the first 10ns of the cycle.
> The AI generated circuit was three times the cost and size of the design created by that expert engineer at TI. It is also missing many of the necessary connections.
Exactly what I expected.
Edit: to clarify this is even below the expectations of a junior EE who had a heavy weekend on the vodka.
Something tech startups are fucking terrible at.
I didn't even have 4G there. I was just wifi hopping as and when I needed it.
It's a toy and another damn thing to carry around and a load of marketing around it to sell it as a suitable replacement for proper kit.
Literally we all use eSIMs and just have downtime occasionally, which is partially the point of it.
Go look at the Invesco QQQ ETF on Morningstar and they're the only loss in the top 10. Also why you diversify your investments and don't go all in on TSLA. Ride it, dump it.
What is a problem is quality control. A lot of "stable" Linux distributions are buggy crap which has all sorts of weird problems and they are problems which I've had for 19 years. Also there are problems with stability which is due to people only doing the sexy work like rewriting the desktop environment every 6 months rather than fixing the bugs in it.
tl;dr: please concentrate on quality and stability, not longevity.