phonebanshee

I don't have a lot of experience with hospitals, but what I do have (via relative with life-threatening heart issues, including most recently a pacemaker) says that "I was feeling 80% well when I went in, I was only there because the doctors wanted to be thorough and check my vitals overnight" isn't normal. It seemed more like "hmm, you're not dying, go home" was the general rule. And not unreasonable, either; unless you need to be in a hospital, you probably shouldn't be. Never felt like we were getting pushed out, but they definitely encouraged us to go home. Excellent insurance, so that wasn't the issue, and there were several multi-day stays, including post-surgery. Pre-covid (but within the last three years), so space wasn't an issue either. [And the person's doing great now. +1 modern medicine.]

Except that it also depends on the definition you're using for "implies," so the normal use of English breaks things if you're really asking about logic. For example, dog implies "likes dogfood" is a reasonable thing to say, but "doesn't like dogfood" certainly includes dog outliers who only eat, say, kitchen scraps, and refuse dogfood. So no, a implies b doesn't let you say not a implies not b, given the normal definition of "implies."

I suspect though that this is the kind of quibbling that will quickly pass the interview test; you say something about dogfood and colloquial use of _implies_, the interviewer says "oh no, we're talking about formal logic where implies means..." and you go on from there. And frankly, that's the kind of interview question that's useful, since if you assume that marketing people use the logic definition of "implies" you're going to be in all sorts of pain in real-world meetings about developing software.

IMHO no one reviews resumes like that. You're almost always going through a huge stack of resumes, spending very little time on each one.

Businesses should have the expectation that they can hire zero H1B workers. The suggestion is that they do something in exchange for that privilege.

Is this just a small sample size? There aren't that many EEs working on software, certainly compared to the whole universe of software developers.

Or change the law. Not particularly likely with power shared between two parties of course.

Isn't that easy to game? You set up a bunch of shell companies that offer jobs. Problem solved.

You vastly underestimate the desire of people for things to look 'nice' where 'nice' is defined by exactly what they mean when they say it. If you want a 'nice' display of data that's input by users, you're often going to butcher it by doing things like converting everything to lower-case, then maybe upper-casing the first letter. Because 'nice.'

It's horrifically wrong, of course, but no one is going to think you're a reasonable person for insisting that correct wins over nice.

Imagine a real-world scenario where you're displaying a list of names of users, where the users got to type in their own names. You can either use what users typed in, or you can do something like process it so it's in the American idea of initial caps. You can't possibly do localization, since it's a list of names of people in the US, so it's melting pot of names from all over the world, and you never asked for user input of what you'd use to localize it anyway [and no, you absolutely can't figure that out from just the name itself]. You can't use what users typed in, because the design team thinks that looks like a horrible mess (and it is; users are laughably bad at data entry). So the design team wins, and you butcher everything by pretending that toLower() plus toUpper() for the first character of every word is a sensible thing to do. (And yes, that's a painful real-world example of software I've shipped and that was used by millions of people.)

Interesting that I was wrong - another data point in the "it's more complicated than you think it is" column. I always thought you were supposed to drop them (because I was explicitly told so by a French engineer I worked with in the 90s, talking about one particular poster, and many years later still assume that one hallway conversation was enough to make that THE OFFICIAL RULE without bothering to actually check...)

That's completely language+locale dependent. For example, here'an alphabetical list of Irish surnames - https://www.duchas.ie/en/nom?txt=M. You'll notice that sort order ignores an initial O or Mac (or Ni or Bean, etc).

toUpper is definitely language-dependent. For example, in Irish there are initial letters that are written as lower-case even in all caps. Wikipedia's example is amusing, since it's a photo of a government passport office sign - the all-caps version of Oifig na bPasanna is OIFIG NA bPASANNA (photo https://upload.wikimedia.org/wikipedia/commons/thumb/f/f8/AL..., article https://en.wikipedia.org/wiki/Irish_orthography#Capitalisati...). It would look utterly bizarre to write OIFIG NA BPASANNA. And this isn't at all an unusual construction in Irish, it happens in personal names all the time.

Plus, there's the issue of diacritical marks. Irish keeps long marks over capitals, but French drops accents. Do you plan to do é => É (required for Irish - POBLACHT NA hÉIREANN is the all-caps version of Poblacht na hÉireann [the Republic of Ireland]) or é => E (common practice for French)? You have to get it right, and you have to know the language to do that. (Poblacht na hÉireann also illustrates the fact that initial caps is also a language-dependent idea; you absolutely can't write Poblacht Na Héireann - that makes my eyes burn just looking at it.)

(And before you say, well, Irish isn't a language spoken by very many people, remember that it's an official language of the European Union. If you're writing software to be used by EU agencies, you're going to have to care.)

Don't forget that idea is inverted for lots of the US (like Florida and Arizona). You gather indoors during the summer, in air conditioned spaces. Winter is when you're outside more often.

Thinks are very different here in Seattle. No one I know is gathering with anyone indoors. You might have a couple friends over and stay outside, but indoor gatherings with multiple people are shocking insanity and just wouldn't happen.

That reasonable level is certainly nothing below C level. Bezos, sure. Some VP at AWS? No.

And it depends on existing skillsets too. I did a recent project where I almost certainly would have used Terraform if I already knew how. But the choice was between "learn Terraform" and "do this in a Makefile," and the "learn Terraform" was clearly crazy overhead at the time.

I'm guessing that you work on server-side stuff, because most people who do mobile/desktop work would say exactly the opposite if they desperately had to come up with a general rule: do whatever you want for servers, but you have to do things right for mobile/desktop. Those are your servers, and you can fix them whenever you want. You push software to end users, and it's gone forever.

You're a member of the Deer Defense Corps, though, and this time you're much better armed than the hunter. You've also had twenty years of training for your mission. It's just that the hunter is really hard to see. You don't have to care about a hunter running away from you, that's not your job.

Given that there are very few B2s, they're only going to be sent against the most valuable and well protected targets. Those are the most likely to have very alert defensive assets in exactly the right place to go after the B2s.

Sure, history has definitely been useful for me. But I've been involved in a few version control system changes, and as long as the old system continues to be available for reading, cutovers are fine.

You're misunderstanding the tool. It's only calculating a small part of total costs. "These values account for only the O&S costs of units (not acquisition costs or other costs)."

People have been saying variations of this for several decades. So far they've been wrong.

Read the last paragraph first. In fact, only read the last paragraph, where the author explains that they have zero expertise and are basically just making it up based on a bunch of pages they found on Google.

The problem is geography. He wants to serve his constituents. Email makes it far too easy for people who aren't his constituents to take vast quantities of his and his staff's time.

You just described email.

Not really. You often need to make extensive changes in those kinds of external dependencies, so you really do want them in your source tree.

That's not a thing in California. Loans on residential property are non-recourse, so if you owe more than it's worth you just stop paying.

Our vet did point out that cats eat carbohydrates; they tend to love the innards of their prey, and those often contain the undigested things mice etc eat. No idea what percentage of their diet that makes up though. (It wasn't a conversation about carb percentages in cat food)

It's not. Many things taste awful, including other kinds of juices.

You live in a world where the dominant programming languages include things like JavaScript, PHP, and Python. It's not that no one cares about functional programming, it's that almost no one cares about _any_ kind of structure. (Yes, that's an exaggeration, but not by a lot.)

None. Music by it's very nature is designed to draw you into it's world. If you want background nose, use background noise.

Why do you think that?

httpss://en.m.wikipedia.org/wiki/Pension_Benefit_Guaranty_Corporation