HN user

kylewpppd

132 karma
Posts1
Comments23
View on HN

I think I've seen all of the Redis/Valkey issues the author mentioned in production.

* 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.

I wonder how much of the "sticking out" is self-imposed. At times, I have felt the same way as you and the author have expressed. At others, I think I am making it up. It's stressful to feel like every move is scrutinized because of something I have no control over.

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.

[dead] 12 years ago

By creating anti-diverse groups like [Women Who Code, PyLadies, Girls Who Code, Black Girls Code], people are literally saying “This group of people are different than the majority, so we need to do special things for them. Treat them differently. They’re special.”

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.

I don't like anecdotes like this because they back the assertion Stop and Frisk does societal good.

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.

Cars to computers always seems to be a poor analogy. But you can replace the ECU with one of your choice. In fact, there is an industry designed specifically for getting better performance from your car by customizing the ECU.

Isn't this the same thing as the Cyanogen mod?

This is anecdotal evidence from them coming to speak at my college, but... Walmart controls almost all of it's logistics. Whereas its competitors use other shipping companies, and have inventory sit in 3rd party warehouses, Walmart builds huge distribution centers that service multiple Walmart stores.

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.

So I would argue that the matching problem with many different styles of socks is O(n^2), since we first must select one sock appropriate for the occasion, then rummage through all the other socks to select its match. This does have the problem that your algorithm may never finish if your laundry eats socks like mine does.

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.

This is the second comment I've come across in this thread. At first I would tend to agree, but let's consider that the "suits" probably have jobs. And if they were at YCNYC they obviously have more interest in startup culture than the million or so suits who did not come.

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.

This is exactly what PHP does. Yes, it issues you a notice, not a warning, not an exception. And it does not break execution. Just set your error_reporting variable to a lower level, and you won't get the Notice at all.

I'd go for sheer package numbers, and also MacPorts traditionally has had much better support for Python packages, and the rudimentary python_select.

Macports says they have 8199 packages. Brew has 1626 by my unscientific count (hint: $('table.tree-browser tr').length ).

A major difference is in how packages are installed. Brew by default will use native OS X packages. Macports installs all dependencies to /opt/local. So a trivial install for Brew could lead to a long install in Macports. I've had Macports build GCC.

But this new version is supposed to allow for pre-compiled binaries. So maybe a lot of that beef will disappear?

How to beat Apple 15 years ago

iPhone passed Nokia in terms of smartphone sales in dollar terms. Apple does not ship more units than Nokia.

It's quite amazing really, that Apple comes in as a late entrant and shaves all the massive profits off the top, leaving the rest of the market to fight over less profitable items.

This article was ok, but the title is pure sensationalism. The author even concedes that he doesn't want Drupal to fork PHP. Maybe I missed the point of the article then. Seems to me the point was another article that talks about how bad PHP is.

Personally, while high oil prices hurt in the short to medium term, hopefully it sends the US economy towards less dependence on oil. To me, this is a good thing. I just hope the US is smart enough to invest in reducing demand rather than increasing supply.

Also, if this type of story is interesting to you, I highly recommend Paul Krugman's blog at http://krugman.blogs.nytimes.com/ . Also NPR's planet money (blog & podcast) has great information and is much less slanted than Krugman's. http://www.npr.org/blogs/money/ .

I am somewhat biased to view that as an opinion rather than as fact. Symbian has always had a much lower overhead than iOS, and Symbian has also been very good about offloading processing tasks to specialized hardware rather than relying on a fast main processor. One of the beautiful things about this approach is that Symbian is much better with battery life than iOS.

Nokia's focus on high end devices is different from the iPhone, and the "technical capabilities" is all in the checkboxes you choose to include.

Physical keyboards, removable storage, removable batteries, 5-band UTMS (the iPhone 4 may have this?), HDMI out, Xenon Flash, FM transmitters, DUN & FTP bluetooth profiles, Adobe Flash, video calling w/o WiFi, and true multi-tasking are all checkboxes that I can use to make the iPhone look like it lacks technical capabilities.

So I think we need to be careful about what we define as lack of technical capabilities. While Symbian may seem less responsive than the iPhone, my opinion is that the iPhone does lots of caching and transitions to make it look smooth while processing. Symbian traditionally has been more baked in functionality than the iPhone, but Symbian certainly is less beautiful.