Comment Re:Just impacted by this myself (Score 1) 45
Hopefully, they had chosen a service plan with a bandwidth cap and, typically, astronomical overage fees.
Hopefully, they had chosen a service plan with a bandwidth cap and, typically, astronomical overage fees.
I'd be concerned that these APs provide commercial NAT IP addresses, so not ideal for server applications.
I had Google Fiber in a house, but moved to an apartment about a mile away. I took my fiber jack and router with me, without telling GF that i'd moved (paperless billing oc). I attached my GF router to the the fiber jack preinstalled at the apt, and it just worked, without ordering service. But it now issued a commercial NAT IP. When I swapped-in the exact same model jack from my house, I got a routable Internet IP and could continue running my public services. Google never objected.
I was poised and willing to do this in the past. Living on a middle-floor of a building that had apartments on both sides (with a common back wall) I could have provided service for 17 neighbors!
Blowin' fat clouds
ISPs don't really charge customers to supply them with bandwidth. They run a toll scam. They charge customers to stop throttling and rationing them.
Optimally, your email server would silently drop the connection and waste the spammer's time waiting for timeout. You don't want to return a code for "bad email address", since that just helps the scumbags.
I have my own domains so I like to generate unique emails for each merchant or other resource I sign up with. I also add a numeric code at the end.
Most of them hate it when you use their own name in YOUR email address, so I just reverse it. Yahoo would become oohayxxxxx@mydomain.com.
But the numeric code isn't random. I grab today's Julian day number and use that so I can also see how long it took for my address to be compromised.
oohay24322@mydomain.com is what I would use if I had to provide a "permanent" email address when signing up for a yahoo address today.
or HCL. or RAAS INFOTEK.
I worked through Cognizant as an internal help desk rep for Faecebook a few years back. The Cog management style sure seemed focused on making busy work and delegating wholly management work to the team.
As FB's help desk reps, we were invited by the client, FB, to join internal chat rooms where other reps asked for help with issues. Our Cognizant mgt ordered us to read these groups but to never, ever post questions there because they were afraid our questions would betray how poor our training had been. They posted people in the chat rooms to watch and report if they saw any of us participating. That was bad enough, but when I privately reached out to FB employees for help, THEY also reported my name to my Cog overseers, so it was a lost cause getting help.
I worked for Cognizant a few years ago. Fully-remote internal help desk rep for Faecebook. We were hired to work in the scenic Austin TX downtown office, but were switched to WFH due to COVID. Most of us quit later when they pushed to bring us BTO, but to a sterile office park leagues away in an adjacent county. I signed on so I could bike to work downtown, enjoy the culture vibe, and go for a relaxing ride around the lake after work.
All of the Cog company reps, leadership and my team's mgt. were Indian. They could have been racists, or they could have been a team of established associates.
We desk grunts were all local to Austin and looked like a diversity spread. It included a few people who didn't really seem to have tech/cs qualifications at all.
However, before that I'd worked for HCL, the Indian-dominated on-site tech provider at NXP semiconductor factory.
My on-site supervisor, who was Latin but could easily pass as Indian, recounted that he'd been invited to a meeting where he was the only non-Indian. Everyone was speaking English as it was their common language, so he had no trouble understanding. They were openly declaring that no non-Indians were going to get raises or promotions and laughing and joking about it. Pretty sure that was racist.
The universe seems to curve in ways that observable matter and it's mass can't explain. Examples are the accellerating expansion and galaxies sticking together despite appearing to spin too fast. The explanaion is that something else curves space.
The universe seems to act like a 4-dimensional bubble rising to a surface, with lots of smaller bubbles clinging to it's outside and denting the interior. As it gets closer to the surface, pressure drops and the bubble expands. It's a matter of the pressure gradient. Within the bubble, galaxies concentrate around the dents.Sometimes enough matter concentrates that it tears off and forms a bubble of it's own (black holes).
The worst "slackers" are those who are able to conceal it while also meeting work goals. Right?
How dare they not deliver themselves unto the office to have ever-more productivity squeezed out of them?!?
A couple of years back, I biked to work daily in downtown Austin. Since pea-headed twits treat the bike lane as a "just going to be a second" parking lane, I frequently have to swerve out onto the street to avoid these obstacles. A driverless test car decided to pace me one morning and rode along in the auto lane just behind me. It refused to move when I had to change lanes, forcing me to swerve back into the bike lane and screech to a halt. It actually SPED UP as I drifted left and signalled my lane change! It would have run me down if I hadn't known it was there.
@pz: Your comment is typical of those who are dead-set against giving wfm any traction. But your point is a straw man.
Nobody is arguing that every role is a fit for wfhm. Nobody is arguing to dismantle factories in favor of wfh.
So you're "right" but your point is inapplicable. You're "winning" against an argument that your opponent does not stand on.
We know wfh works more often than it fails. The failures are the rare instances, so yes let's try wfh for everything and see what sticks.
To the systems programmer, users and applications serve only to provide a test load.