kylewpppd
Joined 15 years ago
Joined 15 years ago
http://cva.stanford.edu/classes/cs99s/papers/moore-crammingm...
But to further needle, the law is
Should it be a $750k house at 3% is a $500k house at 6%?
I am tired of the "sticking out" feeling, real or imaginary. So, I started a Meetup group for black engineers. Sometimes, it's really nice to just relax and feel comfortable. No worries about someone attributing my behavior to being black, or judging all black people by something that I've said or done.
Right now, I am hoping to rally folks to come to Philadelphia in 2 weeks for a black hackathon. It's a great way to network and teach. Check out http://www.mbkhack.com/ for more info. If you're in NYC and interested, we will have a pre-meeting before we go. The link is in my profile.
Though this was a small part of the post, I believe this is one of the most flawed concepts he has. Having founded a group for black programmers in NYC, I can tell you, we're not asking for special things, nor have any of the women I've encountered from the other groups.
My group, the Black Techies, was founded so that we could have a place free of crap like cultural biases, or people asking "why are the black people sitting together at lunch", or sexist and racist posts that devalue our worth.
The author's version of "true diversity" is one where anyone who is not a white male assimilates into a white male culture of software development.
His vision is one where white males don't have to change; where acceptable groups are blessed; where we can't do anything about the adults in the field, we need to focus on the children and in 20 years, __maybe__ we will look up and see that it worked.
This vision is one that perpetuates the status quo.
For myself, and I would posit the other founders of similar groups, the status quo is unacceptable. And we actively fight, on our own terms, for our own interests about the best way forward. Who knows best about how to hire more "diverse" programmers than those same "diverse" programmers?
Is a "1:1" speaker ratio the right thing? Is it going to produce results? Is it sustainable?
Who knows.
But, it is an active and bold idea. It's taking a stand. It's does a hell of a lot more for the conversation than silently removing a "no girls allowed" sign from the boys club.
It implies that police are able to discern the difference between "good people" and "bad people", and that "stopping the bad ones" doesn't harm society at large because "the good ones" don't get stopped.
This is hurtful to those who have experienced it first hand, and to those who are seeking equality of all people under the law.
Isn't this the same thing as the Cyanogen mod?
Coming from apt-get or yum makes brew, port, and fink look like a joke.
The distribution centers mean they can purchase huge levels of inventory at discounted terms. Running their own logistics means that they can break up pallets into smaller shipments appropriate for each store. So stores need less space to carry inventory, and they can purchase and store huge amounts at lower cost per sq. ft.
The other thing the logistics does is gives them an advantage in transportation cost. Although (I've heard) the margins in ground transport are slim, running your own ground transport saves money, allowing for lower prices to the consumer.
Walmart's size also contributes to their "efficiency". They can buy in larger quantities than their competitors and try to exert downward pressure on suppliers' prices. They can also nab exclusives and put them on the shelves for less than competitors.
And that with all identical pairs, I assert the solution is O(n), since there is a chance that you will have to iterate through all of your socks to find one with no holes/is clean. However, I think the latter case is Omega(1). Not quite so sure about the first one.
Part of hacker culture is judging someone by ideas, which is why we're known for the t-shirt and shorts attire. But I don't think it's fair nor helpful to judge someone by their attire at a post-work event.
We know gobs and gobs of NYC's tech talent works in the financial services industry. I'm happy to see the diversity, even if I got a few pitches from folks looking for a l33t technical co-founder.
* Outages where Valkey had no memory policy, ate all the memory, and then caused write errors to its append-only file. Bonus points for another one where the disk itself was full, and AOF writes failed.
* 500s where Redis was fully expected to be live, running, and populated with data for every user, and no fallback to a slower path.
* Creative uses of sorted sets and other data structures which depended on the sets never being evicted.
Despite the observations from the field, I think it's still hard to recommend memcache ahead of Redis. It can be difficult to architect an app to have a memcache-friendly cache layout.
I'd almost guarantee a large enough team using memcache will find a way to need Redis. And then we're maintaining 2 cache technologies.