aturek

Here's an optimization that one of the maintainers of rails is doing (has already done?) on #find

http://tenderlovemaking.com/2014/02/19/adequaterecord-pro-li...

Does this increase the stack by 2 in every call?

If you use a CDN (or use the public CDNs that many of these libraries have) it's not 130 kb, it's a network request + 304

Topical and recent: https://www.nilas.com/blog/splitting-the-atom (some more talk about people using Flux)

In the past, I've done practice interviews (phone or in-person) for my friends prior to them doing a standard Amazon/Google/Microsoft interview. Do you have any friends that would be able to do that for you?

If anyone, like me, didn't know about 'track by' as a way to optimize ng-repeats, here's a couple of articles that explain what it is and why it's beneficial:

http://www.codelord.net/2014/04/15/improving-ng-repeat-perfo...

http://www.bennadel.com/blog/2556-using-track-by-with-ngrepe...

Curious, do you have some anecdotes about that? I've generally heard from coworkers who were at Netflix that they have pretty high attrition at the lower levels, with the "fire the bottom 10% every X months" rules.

London's mostly awful when the drivers are doing it, but I believe they've been automating more and more lines with stop announcements

On Google Maps

https://www.google.com/maps/@47.662205,-122.375384,3a,75y,6....

I'm sorry if this is a dumb question, but what countries currently do some sort of basic income? A quick search on Google/Wikipedia turns up no actual implementations

I don't understand Python exceptions that well. But it's great to have the pattern of maintaining the stack trace when re-raising an exception. Thanks OP!

(In case anyone missed it)

    except foo.FooException as e:
        raise BarException, BarException(e), sys.exc_info()[2]

That bullet point surprised me. It comes right after "110K lines of code. A small number given what it does"; to me this reads like they didn't write tests because that would add complexity.

Can any SO devs give us more details on "not many tests"? Or how many bug reports get filed vs rate of change of software?

I've been trying to learn the best practices on password "storage" and verification lately. I thought this was a really good step-by-step technical breakdown of the right way to hash passwords (I have no opinion/knowledge of the hashing algorithms in the article, but I've found a lot of other positive mentions of PBKDF2, bcrypt, and scrypt)

http://nakedsecurity.sophos.com/2013/11/20/serious-security-...

There's a great quote from a Terry Pratchett Discworld novel:

"The reason that the rich were so rich, Vimes reasoned, was because they managed to spend less money.

Take boots, for example. He earned thirty-eight dollars a month plus allowances. A really good pair of leather boots cost fifty dollars. But an affordable pair of boots, which were sort of OK for a season or two and then leaked like hell when the cardboard gave out, cost about ten dollars. Those were the kind of boots Vimes always bought, and wore until the soles were so thin that he could tell where he was in Ankh-Morpork on a foggy night by the feel of the cobbles.

But the thing was that good boots lasted for years and years. A man who could afford fifty dollars had a pair of boots that'd still be keeping his feet dry in ten years' time, while the poor man who could only afford cheap boots would have spent a hundred dollars on boots in the same time and would still have wet feet.

This was the Captain Samuel Vimes 'Boots' theory of socioeconomic unfairness."

This sounds really interesting, but can you elaborate on how Go scales better with maintenance?

(disclosure: I haven't fiddled with Go at all yet, so I know nothing about the language itself)

tl;dr: Superclasses make your code brittle. https://en.wikipedia.org/wiki/Fragile_base_class

How many people still try to fit their software design into the class hierarchy model? I've been on the composition-not-inheritance side for so long I can't do "traditional OO" justice, but I'd love to hear the counter-arguments in case I'm wrong.

I see the job of a dev manager (i.e. his direct reports are mostly engineers) as the following:

(1) Filter requests for work to his team to avoid them having to constantly task-switch, with the associated loss of productivity and job satisfaction.

(2) Provide his team with the business context for the work he asks them to do, and trust them to handle details.

(3) Get his team the support they need to do their jobs.

These all involve tradeoffs. If you constantly tell your team every part of every business discussion that takes place as part of (2), you can fail at (1) and distract them from their long term goals and work.

I've worked with managers that didn't protect their team at all, and who constantly forwarded emails and repeated conversations to us until we could barely get anything done before having to switch to a new task. I've also worked with managers who didn't tell anyone anything, and let their reports toil in the dark for months before letting them know that most of their work was wasted.

A good manager will sometimes fall on either side of the line; a bad manager will consistently err to one side. Managers are just like engineers - there are a lot of bad ones, and some good ones, and size of the company is pretty orthogonal.

Democracy mode is great! But a couple of players (and I) figured out that multiple key presses by a user are counted, so we have more of an oligarchy determined by whoever can spam keystrokes...

Noticed a minor bug: clicking "sign up and write" and then the "X" on the popup still has the spinner going on the signup button

Downvotes can be used to stifle dissent, but are generally valuable.

I feel like 60-70% of the heavily downvoted comments I see are already trolling or flaming (or in some cases something dumb, like a 3-word reference to an internet meme). With the grayed out text, I think this is a fantastic visual cue about how not to act on HN.

(I could have just written this comment as "/disagree", and then watched it get appropriately downvoted, and learned my lesson)

Edit: I should also add that as a barely-contributing user, I don't have the ability to downvote. But I'd still like other people to be able to do it, to enforce the community's standards.