hammerdr

This.

# Before abolishing time zones

  I want to call my Uncle Steve in Melbourne. What time is it there?
  Google tells me it is currently 4:25am there.
  It's probably best not to call right now.

# After abolishing time zones

  I want to call my Uncle Steve in Melbourne. What time is it there?
  Google shows me a daylight map (First result https://www.timeanddate.com/worldclock/sunearth.html)
  It's probably best not to call right now.

We are just used to the insanity that is timezones. Of course, I say this because I have to deal with time and timezones every day at work and bugs are always prevalent. Each DST switch there are new bugs we find; every time we change our core date and time code there are bugs. Just painful.

In the end, we'd build new tools and intuitions around time. People would adapt and my life would be measurably better (though not completely solved; scheduling anything across a date boundary is odd. No one thinks of 1am as "tomorrow" but instead as "later tonight").

Oh, for sure. I picked a source that had a lot of opinions that differed from mine as to consciously oppose my bias :) Thanks for the other links!

Warning: very little knowledge of Rust and Iron

Can someone explain why there is an extra Ok(...) in this? (I want to call it a function, but I'm not even familiar enough with Rust to be sure that it is a function).

Is it something that could be removed? Right now it just looks like boilerplate.

Edit: Thanks everyone! Ok is similar to a Right or Success of a Either/Result type of object.

Just as an opposite anecdote, I find that I run into it all the time. Sometimes, its from people that are outside of the tech industry itself. Sometimes, it is from people that don't realize that they are saying such a thing. Sometimes, its from people of different cultural background (e.g. Chinese developers). I see this in SF, saw it in Chicago, Dallas, Atlanta and in the various countries I've worked in.

I also recognized that it has took me a lot of time and a lot of effort to get to a point where I recognize it. 10 years ago, many of the things that would set off the "Hey; that does seem right" alarm bell would be unconsciously ignored and taken at face value.

If I may presume, I'm going to suggest that your experience may be because you're more 'attuned' to racism than you are to sexism. For me, at least, it takes effort and willful learning to come to better grips with sexism, racism, ageism, etc. It's hard work!

I don't disagree with the premise that double clicks are a broken thing on the web. There's too much of a cognitive shift between "the web" and "everything else" where double clicks are either a bad thing to do or a required action to complete tasks. Like the author said, even tech savvy people will double click things that they wouldn't need to.

But, saying that idempotency is hard and thus we should build features to get around it.. that seems wrong to me. The web is inherently a distributed system and you're going to have concurrent requests and weird edge cases that arise in those situations. The right way to handle that isn't to bandaid it with disabling client side behavior. That just hides to problem. Your server is the place to handle it.[1]

And, it really isn't that hard either. It's just a couple extra validations on your input before you do a write. There are places where it is more difficult but still not overly complicated to implement.

[1] Dogmatism alert. Of course, there are exceptions to everything that's a 'best practice'. Here, I'm just talking about disabling double-click as a general solution for the web to a concurrency problem.

The Knowledge is the book that every library and "End of the World" kit should have in it.

Not entirely sure what you're asking, but you should probably look into "schedulers" and other tools built on top of such ecosystems. Here are a few to get you started:

Docker ecosystem: swarm and/or compose

Mesos ecosystem: Chronos, Aurora, Marathon

CoreOS ecosystem: fleet

Hashicorp: Terraform

Amazon Container Service: works with the above, will likely build their own simple one in the near future

This is less about embedding images and about managing/"scheduling" them

Edit: Zikes mentioned Kubernetes, as well.

Your functional test was a test that allowed you to experiment. You designed the parameters and then altered the variables involved under the conditions of those tests.

You probably even "called your shot" and make guesses about what would be successful before you even approached the problem.

Then you wrote a test and saw whether your guess was right or not. If not, then you misunderstood something and you dug deeper.

Software, in some ways, in simulated science.

Writing the test is the experiment, in your example. You're playing with how it is going to be used and interacted without worrying about the details/implementation. You'll take care of that later.

Thanks for the story. It's something to consider when being conscientious about these things.

I think a possible difference is that asking someone to share their experience directly invokes some kind of entitlement on the part of the asker.

But, I don't think that there is anything wrong with amplifying the messages of those underrepresented [1]. Many people with true experience are talking, but have trouble getting that message heard.

[1] With their permission. Don't shuttle around someone's personal story without permission. It can be damaging in ways that you're not aware.

I agree with everything you said.

I was specifically speaking about people that pontificate about things they have no legitimate claim to have experienced. Being a Latin@ in the United States doesn't legitimize your claim to speak about rural peasants of Mexico (though, if your family has roots there you may have lingering first hand accounts that can color the discussion more than those without).

In fact, historians are one of the people I would consider a source, especially if their words are born from the interactions and studies done from interacting with real people. They make it their life's work to understanding the situation in which people live.

Also, everyone makes mistakes and/or embellishments. I make mistakes. People in their own experiences get caught up in those experiences instead of the truth. Historians get caught up in their own narrative of truthiness instead of truth. Skepticism and an open mind are great tools toward enlightenment.

So, yeah, sometimes white men can be more legitimate than others in their viewpoints. But far too often the voices of the privileged and uninformed drown out the voices of experience and truth. That's the tragedy.

This is easy to beat: just go to the source. If there's a howling white man going on about injustice and how he's going to tell you about the struggles of women of color, First Nations and Imperialism.. ignore that person. Go talk to a (well.. several, actually) woman of color, member of a First Nation or a nation ravaged by European and/or American imperialism.

"But what can I do as a white man/white women/generally privileged person?" - Amplify. Your voice unjustly carries more weight than that of other people. If you can be the "Retweeters" of Social Justice, you'll be doing a lot of good. Just be sure to retweet the people with firsthand knowledge.