It made me feel like I'm talking with someone role-playing a therapist; it's just my worldview but if I want to talk about how something made feel I will talk about it but dislike to be directly inquired, is evident that this is way of thinking is more common in men than women of course.
There are a lot of ways to inflect this question. To ask it bare is usually not the best.
Note in the authors third approach they first validate the feelings and then ask for more details. That is a really great move. Tailoring that to the vibe of the situation is where it’s at. It really does work like a charm.
It definitely depends on rapport and how authentic someone is being. If someone asks me this and I know they genuinely care about me, I'd be happy to share. If there's less rapport, it will definitely feel like a person who can't read the room is trying some sort of social mind trick.
At some point when you go to extreme lengths to pick the softest wording possible you yourself become an accomplice, they didn't "summon", that word is better for fantasies where they summon spirits or beasts like shai-hulud, here the fitting word would be "forced" as in "Iran government forces families of exiled journalists to stop any criticism against them"
To summon someone implies force both in the "real world" use and in the mythological use.
In the real world it generally means to order, with the implication that there are consequences to failing to appear, and the consequences in this case are clear from the juxtaposition of wanting to shut up exiled journalists and summoning their families.
In mythology it typically implies incantations etc. forces the entity to appear.
There's nothing soft about that wording. If anything "to summon" is often used to imply a level of disdain and lack of legitimate basis that is not implicit in "to order"
The word summon comes from Anglo-French somundre and Old French somondre (or semondre), meaning "to call, send for, or notify". It derives from the Latin summonere, meaning "to remind privately, warn, or hint to".
To summon is the correct word in this case. The fantasy meaning comes from thee power politics between one that summons (usually: a king) and the one being summoned (usually the serf).
I sincerely doubt that if someone hears 'summon' today, they think about Dungeons and Dragons-style summoning of fantasy beings. They more likely hear 'to be made to appear in front of [a state power / a court / ...]"
As such, current understanding is closely aligned to the etymological meaning.
Even summoning in fantasy tends to imply the entity being summoned has no choice in the matter. If anything, summoning in fantasy is usually stronger, in that there is a tendency for it to imply the entity is powerless to resist.
I would prefer to be summoned and threatened, forced, or even exiled, than get outright assassinated by quadcopter, airstrike or sniper rifle (or something else).
I definitely want to see that state+population table in mobile as a single element that I can just scroll to not 3 elements fighting for horizontal space thank you very much.
You understand how subjective that is right? Someone might expect that the database doesn't do the last commit step while other people is perfectly happy that the database engine checks that it has enough writing permissions and is running as a user that can start the process without problems.
Sure, where you draw the line will vary between projects. As long as its exact placement doesn't matter too much.
For me personally, I tend to draw the line at write operations. So in your example, I'd want a dry run to verify the permissions that it can (if I expect those to be a problem). But if that can't easily be done without a write, then maybe it's not worth it. There are also situations where you want a dry run to be really fast, so you forego some checks (allowing for more surprises later). Really just depends.
Recently I got to know at an interview how company A (big western company) acquired another company years ago and are now working on redeveloping code that was an important part of the acquisition which fails to scale beyond the original use case.
This kind of stuff during interviews is a lot of learning in itself especially if you’re working already in the same area.
yeah, I've gotten this kind of knowledge from an interview before. They let slip a little something as to the project you will be working on, you start asking given the project you described I wonder if... and then they tend to tell you how it is.
It made me feel like I'm talking with someone role-playing a therapist; it's just my worldview but if I want to talk about how something made feel I will talk about it but dislike to be directly inquired, is evident that this is way of thinking is more common in men than women of course.
reply