More than doctors? Feedback cycles in the OR and ICU get pretty fucking short.
I do think the overall premise is silly, programming isn’t that special in this regard in my opinion. Most professions are like this, they just might not be the most visible ones like politics, journalism, show biz.
Software developer have more to learn from other professions than they often think (the old engineering professions understand this a bit better)
Somebody that has claimed 20 years of experience and doesn't at least know instantly (this doesn't require "thinking" about for minutes) that this is a one liner in the shell or a few lines of pick your poison script, Perl, Python, Ruby, who cares, even if they can't remember the specifics is not an expert in programming.
And I get it, there are highly specialized people that get very deep in the weeds in maybe HPC or embedded, even so most of them will at least still be aware, but moreover these people lack the knowledge to comment on programming or software engineering in the large, I wouldn't call them experts outside their limited domain if they really can't begin to know where to look to do a fucking permutation of a word list.
The old saying that for some 20 years of experience is 1 year and 19 repeats probably applies.
You're absolutely wrong on a number of points. A SoC stands for "system on a chip", it refers to a single die (if you want to get pedantic, there are multi-die packages but this does not apply here) package, a "bare chip" if you will.
The ESP32 is a SoC. It's available in QFN packaging (Quad Flat Pak No Lead).
The ESP32 is available included with a number of "modules" (and of course devkits). These modules are designed for production use and it can be economical to do so. You clearly don't have the foggiest idea about these product lines so don't seem to be in a good position to comment on the economics.
Why would you need to sign an NDA? There are decaps readily available. Most ESP32 models have a separate die for the flash memory, but everything but the flash (that is uC, WiFi, BLE, and peripherals) is on a single die, which sounds like a SoC to me (The definition of SoC devices have always included devices with off-die RAM and Flash). These aren't "a bunch of components on printed circuit boards" as you initially claimed.
Wrong. There is melena, which is a generally unmistakable consistency of black sticky stool (nothing anyone would identify as "blood") that is indicative of upper GI bleeding - not the colon. It doesn't really indicate severity because it may be fast or relatively slow. Both upper and lower GI bleeding can be serious in terms of acuity or seriousness of disease (cancer).
However if the internal bleeding from the upper GI system is brisk/fast enough it will come out bright red. This can happen to people with esophageal varices (sequela of liver disease and cirrhosis) or brisk stomach or duodenal ulcers and the prognosis is usually poor, but very likely they will be getting emergent endoscopies and/or mass transfusion if they make it out of the ED.
You can't tell by color.
> That may be an internal bleeding.
Colonic bleeding is just as internal and will typically be red or maroon.
Just a little aside for those doing a search in the future: many things you consume can also turn poop reddish so be sure to think about what you had for dinner if you've just noticed it. For example; beetroot, red wine, berries, stuff with food colouring etc.
In particular what you ate the past sveral days since it takes time to go through (exactly how long depends on your diet and body, but I think 2-3 days is common and a another couple of days is not uncommon). It takes long enough that it is easy to forget.
Are you kidding? Ibuprofen like most NSAIDS is terrible on the GI tract and the kidneys. People with healthy kidneys are usually fine with short courses, but even people with relatively mild chronic kidney disease should avoid NSAIDs.
People in their 20s that overuse NSAIDs end up needing kidney transplants. it's not that uncommon.
The most common cause of peptic ulcer disease of this demographic (affluent westerners) after H pylori is NSAID use.
> It has fallen out of favor because it's known to cause an exceedingly rare but deadly syndrome in a tiny percentage of children
This has really nothing to do why aspirin has less common use among adults. Aspirin has poor analgesic effects relative to the doses and the risks of GI complications.
> acetaminophen results in tons of hospitalizations every year.
The impact of NSAID related complications is far greater in terms of kidney transplants and upper endoscopy interventions, and related ICU stays.
This is misleading. Tylenol in therapeutic dosages does not seem to have much ill effect on the liver, it is not like alcohols or other direct liver toxins. Even people with advanced stage liver disease can receive acetaminophen. When it becomes toxic at supratherapeutic doses it is very toxic.
I was just trying to clarify some muddled discussion about different layers of the networking stack. The original comment about port names instead of port numbers didn't seem to be made with an understanding of the different layers.
DNS has SRV records. That is all you need, that is your solution, it exists. That they are not widely adopted in the manner you propose may be unfortunate, but completely upending protocols doesn't seem like a better or more realistically adopted solution either.
> Your experience is quite limited. Too limited to have a meaningful opinion on this subject frankly.
I am having quite the big problem with this getting downvoted. The poster is spot on here and this needs to be communicated. Not doing so is irresponsible. Overconfidence in this regard is extremely dangerous and there is no nicer way to say this.
You can not reasonably assume that you are able to judge something works reliably without understanding how the error cases look. Especially if these are capsuled from you and or you dont know what to look out for.
This is at the very core of why something like the post scandal was possible. People repeating the same mistake in this very thread is just really bad. The only thing worse would be not telling them this.
Please don't cross into personal attack. If you know more than someone else, that's great, but in that case please share some of what you know—without putdowns or snark—so the rest of us can learn.
No one else but you can provide you with experience. Hardware has both bugs (defects) and it fails, sometimes in ways not gracefully. An experienced multidisciplinary developer is certain to encounter them at some point. Depending on the discipline this may be a very common occurrence or it may be rare. Devs working at either extremes of scale are more likely to encounter these problems. Defects may go unnoticed due to software workarounds of all things
A very common problem is bugs caused by cosmic radiation if you want an example. But bugs in silicon are also not rare and really difficult to catch. You really got to stick your neck out and hope you can actually proof that through stuff like debugging with electron microscopes. Especially if it becomes an issue of responsibility between different departments. The monetary stakes make this all the more difficult.
Hardware bugs are simply capsuled better so people dont recognize them as such. Its the same mechanism at play as for people who assume software normally functions. They are also just unaware of the inner working.
Stuff is just really complicated and people should manage their expectations. I get that going from assuming to have a solid base to no such thing existing is difficult to handle but there is no sensible way around that. Not doing so gets you stuff like the article.
I do think the overall premise is silly, programming isn’t that special in this regard in my opinion. Most professions are like this, they just might not be the most visible ones like politics, journalism, show biz.
Software developer have more to learn from other professions than they often think (the old engineering professions understand this a bit better)