I remember my older brother being moved by professionals when he was in the Navy. They came in and packed everything up including the waste basket by a desk... with all the paper trash in it. There was one thing damaged, which they told him about. His motorcycle fell over during the move and had a slight dent in the fuel tank. He looked at it and told them not to worry about it since he had a larger one on the other side.
He was really impressed with their services and if I ever use professional movers, I'd want folks like that.
I was the primary ops guy (well before the concept of devops and when separation of duties was important) and ended up being the primary troubleshooter for problems. During one of the meetings between DEV, QA, RC, and I, the software architect exclaimed that RC had to be exaggerating since he just said it took X time to transfer the installer from one machine to another.
I looked at him and said the installer is ~200MB in size, 20 seconds is more than reasonable. He started arguing that the network connections had to be at least 100meg links so it shouldn't take more than 2 seconds. It went round and round, until I realized he didn't understand that network links were in bits/sec. At this point, he was refusing to listen and started disparaging everyone 'against' him. I gave it one more go and showed him the unit conversion and basic math on file size, rate, and time.
For a while, it looked like he was trying to get everyone arguing against him released since he was an 'architect' and everyone else was engineers and I was just the ops guy. Too bad for him, he didn't realize in the land of inflated titles, I was the security, storage, and infrastructure architect. I just felt it was presumptuous and relabeled myself the ops guy.
I realize it was a tongue in cheek comment (at least interpreted that way), but that was a serendipitous opportunity for the young lady's boyfriend. I know I've had several such opportunities with my now in laws. Regardless of the differences of opinions, nothing wins over people more than just helping when help is needed.
Stopped reading at "while all the US grids operate on the same frequency, those frequencies aren't always aligned—the peak in the AC of one grid may line up with the trough in a neighboring grid". Practically every regional grid is interconnected to it's neighbor. If they get this basic infrastructure wrong, I'm unwilling to fact check the rest of their premise.
I didn't even read that far :0 The point of my comment was their lack of understanding of how the existing transmission system is connected to their neighboring regions. This is the base infrastructure of the electric energy market (long term, day ahead, and spot markets). These interconnects between regions (grids) requires that frequency is in synch and any deviation will cause a disconnect.
It's not lying if you're careful how you respond to their question on salary. I always respond with my compensation is $X, where X is my previous year's salary, bonus, and cash value of PTO and other benefits.
But he was lying. That's different. What you're making is irrelevant, and if it is for them (i.e. the company you're interviewing at is making an actual problem of not knowing), then you don't want to work there. What you're looking to make is much more relevant.
Everything seemed reasonable until he complained about the lack of access to "telephone pole infrastructure".
I can't speak for all 50 states, but in Indiana the pole infrastructure is actually the power utilities where anyone can request (and are mandated by the state regulatory body to have equal access to all) permission and access to attach to the poles. The process IS painful as the power utility has to perform engineering studies regarding the attachments to their poles, for each steenkin pole. The requestor pays for all such studies.
It's not the current location that's retrieved. It's the approximate location of when you sent the message (or as I mentioned previously, the location of your map view in intel if you send the chat from there) or other "alert" event.
Considering most of the alert events are location specific events (playerX captured/attacked/deployed portalX, linked portalX and portalY), playing the location based game exposes your location to other players.
He was really impressed with their services and if I ever use professional movers, I'd want folks like that.