> all the useful artifacts from it happened naturally because product and dev were so closely aligned.
Aren't you just saying that DDD wasn't proposed as a solution to the problem because the problem didn't exist? Starting to jog is a smell that you're out of shape, if you were in shape you wouldn't need to start jogging.
One of the ideas that DDD pushes is that product and dev should be closely aligned. The reason that's emphasized is that it isn't the case in a lot of organizations. Of course you could try to avoid all orgs with these kinds of problems (I haven't been able to, unfortunately), but the question is, if encountering an org that _does_ have problems, what solution would you propose?
Completely agree. I mostly get around by bike or running and I doubt I'll use scooters very much, but I'm excited for these to come to the city. The more people there are using alternative forms of transport, the more people become aware of how insane it is that we allocate so much of our scarce space in the city exclusively to the needs of car owners.
I agree. Seems like what Feynman really wants to say here is “this isn’t a question I’m personally interested in”, but frames it as “it’s dumb to be interested in this question”.
We are only experiencing the end result of what our senses sample and our brain processes. That’s clearly true. How much that end result diverges from the real thing is difficult to answer, but in a straight forward way you can look at an optical illusion to see that there is some divergence.
Something I realized recently is that I'm not addicted to social media or any apps in particular, but I am addicted to my phone. I managed to give up pretty much all social media, save for an occasional peek at reddit and this site, but still take out my phone about as often as I did before. Mostly I just check the news for the umpteenth time in a day. My current plan is to keep using my phone, but switch to using it for more productive things. For example, I started using Anki for memorization and I use a bunch of music theory/sight-reading apps.
I think what you're saying is valid, but the point I've been making is that the entire James Damore affair is interesting for pretty much the opposite reason to that which people who tend to bring it up claim.
"It doesn't seem right" is one thing, but that's not why it's still brought up 3 years after the memo was written. A lot has gone on in the world in the past 3 years that doesn't seem right that we've forgotten about or didn't hear about in the first place. Damore is used as a data point (in fact, as a central data point) in the thesis that "political correctness gone awry" or "social justice warriors run amok" are problems that rank highly in a list of society's most concerning. I think it's absurd. That this random dev's firing is doing so much work in bolstering this thesis just highlights the absurdity.
How so, I didn't say anything about the content of the memo? Or you disagree that it did obvious harm to Google's policy on gender? We know that female employees received the memo and stated that it made them feel excluded, which did harm to the intent of the policy. That's not really debatable is it?
Policy from management is not beyond all reproach, but what venue you have for expressing disagreement varies by company. Do you think the firing of James Damore warranted the attention it got?
There's been endless discussion about Damore. In particular podcasts you'd think that the firing of a random engineer at Google ranked alongside 9/11 as a defining event in modern history. If I circulated a memo to my co-workers that not only opposed a new policy from management, but did obvious harm to the expressed intent of that policy, I might be fired. It doesn't matter if the memo I circulated would have gotten a passing grade in a college class. The fact that people use that as an argument tells me that they've never worked a normal job before.
> Electron is always a point, no matter what wave function it has. Therefore, from this perspective space is all empty.
That depends on what interpretation you're going with. Even with that caveat, I'd be surprised if most physicists would agree with that statement. Electrons are in fact described by the wave function. It's not that the wave function tells us where the electron is, but that the best way of describing the reality of the electron is through its wave function. How and why measurements seem to cause that wave function to collapse to a definite location is different depending on your interpretation of QM.
What appears to have happened here was that a climate denialist group that deliberately use "NAS" to confuse people into thinking they are receiving an invitation to speak at a conference by the National Academy of Sciences, was called out by an open science advocate who himself felt mislead. Then the Wall Street Journal was snookered into publishing an editorial because they'll publish pretty much anything that claims to be about "cancel culture". And now we're here debating how some tweets mean science has been ruined by cancel culture warriors or whatever. The irony is that the person being "canceled" is exactly the person being accused of it.
The advantage of scooter and bike share over owning is spontaneity. I love being able to grab a bike on a whim without any planning. And one-way trips is a big advantage, which of course only works because people are shuttling them around.
I think the relative efficiency of the share model needs to be weighed against the inefficiency of everyone owning their own while only using it a fraction of the time.
My mother's cat used to carry live mice into the house and release them. He'd bat the stunned mouse around but not kill it. I would have to catch the mouse and bring it back outside. The exact opposite behavior you want from a cat.
Aren't you just saying that DDD wasn't proposed as a solution to the problem because the problem didn't exist? Starting to jog is a smell that you're out of shape, if you were in shape you wouldn't need to start jogging.
One of the ideas that DDD pushes is that product and dev should be closely aligned. The reason that's emphasized is that it isn't the case in a lot of organizations. Of course you could try to avoid all orgs with these kinds of problems (I haven't been able to, unfortunately), but the question is, if encountering an org that _does_ have problems, what solution would you propose?