I'd compile some examples for you, but I'm not sure how you'd interpret it :)
6,067 karma · joined July 30, 2015
I'd compile some examples for you, but I'm not sure how you'd interpret it :)
Before the pandemic, my wife and I worked from home while our kids went off to school. That made it really easy to have "special" time without concern for the kids hearing us or walking in on us.
With schools doing remote learning, that's no longer possible. Which means we're at the mercy of whenever the kids are soundly asleep at night. Which means we're more tired during those encounters, and it messes up our sleep schedules.
It's one reason I'm really, really looking forward to school returning to normal next fall (fingers crossed).
There are a few aspects of it that I'm really enjoying:
- I can now actually understand the disassembled code that I see during debugging. This includes recognizing some of the assembly patterns that appear because of ABI requirements and/or common programming idioms.
- I'm becoming comfortable with a programming idiom that I've never really used in the past: registers, flags, various kinds of memory addressing.
- It helps my understanding of compilers' lower levels / backends, and the related problems: register allocation, instruction selection, etc.
- It provides a clear path for my first attempt at writing JIT code (using Xbyak[0]).
So as Richard Feynman might have said, it's great fun!
You mentioned "contentious". Are you concerned that the conversation can't remain friendly, professional, and cordial for some reason?
IME, the effort needed to reduce unwanted noise depends a lot on the frequency range.
Very roughly speaking, dampening high-frequency sounds can be done with relatively thin and light sound-absorbing materials. Lower-frequency noise, including vibrations that shake the building's superstructure, require more extensive modifications.
It would be awesome if an actual acoustic engineer or architect could weigh in on this.
I.e., being shunned by Facebook or Google is a high-consequence, low-probability, hard-to-predict event.
You may as well treat it like building a factory in an earthquake zone.
I'm having trouble imagining how that's compatible with a democratic form of government.
A policy like that would, I think, provide a very clear roadmap for would-be dictators.
Can someone clarify if that's what the article is actually saying?
Now it's valid 99.99985% of the time.
People are good at rationalizing. I'm sure my earlier comment, and many others, would be sufficient justification for someone inclined to do nothing.
I guess I was assuming that anger and happiness are somewhat mutually exclusive.
In some cases, they're selective about which groups will and will not be sheltered from offense. And they may refuse to admit that, let alone engage in a public, civil debate about their choices.
And fwiw, you're welcome to just ignore any threads or stories that you feel are getting repetitive. Many of us have a personal list of such topics, but our lists may not match.
For my paid work (at multiple jobs), I've never been allowed to use C++ newer than C++11. At first it was due to incomplete compiler support, and later on it was because various customers were using older versions of RHEL whose standard version of GCC was something like 4.8.
Anyone else experiencing this?
We recently had a discussion on this topic: [0]
I've heard it said that in the U.S., the only reliable way for a non-union worker to get real protection from abuse is to personally hire a labor attorney.
In it, Pink describes two competing mindsets for approaching social issues. One prioritizes analysis and understanding as first steps; the other prioritizes activism unrestrained by fact-checking.
I'd be interested to hear his accusers' response to that interview. Experience tells me to withhold judgment until I've heard from all sides, and that interview was only with him.
[Disclaimer: The following is a description of my current thoughts on the topic. I could very well be wrong, but I thought sharing them might make for an interesting discussion.]
That said, I have an anti-PC view on this topic that AFAICT is somewhat a-religious. My perception (i.e., I very well may be wrong) has been that the pro-PC arguments I've heard contain some logical inconsistencies that I've been unable to resolve. And that some organizations with pro-PC policies use ad baculum or ad hominem attacks to avoid serious debate about their position's weaknesses. I think it's obnoxious to force others to obey their moralizing while refusing to submit their views to serious debate.
I shouldn't have presumed to speak for the parts of CT near NYC.
Even if one was inclined to open a good software shop in CT, you'd have neither low property prices nor an existing pool of highly skilled labor.
My worst-case scenario, perhaps totally unrealistic, is that this allows a drone with a camera to hover over my property, peeping in through the windows.
Are there any current / upcoming rules that prevent that?
But I'm not sure where the best place is to apply pressure:
(a) privately shame recruiters to the employers they represent, or
(b) publicly shame recruiters so that employers and candidates can avoid that recruiter, or
(c) publicly shame the employers who hire such recruiters.
Also, the anonymous nature seems like a double-edged sword. One could imagine hoax / malicious reports being submitted by competitors and/or rejected candidates. I imagine that once that loophole starts getting exploited, employers will rightfully ignore all the reports.