Hacker News Reader

evanspaon Weak passwords brute forced

See "Part VII" of this SO answer from Jeff Atwood describing mitigation techniques for "distributed brute force attacks"

http://stackoverflow.com/questions/549/the-definitive-guide-...

TL;DR - compute the average number of system-wide failed password attempts, and if it's over the norm, impose small delay on all users (except those that login via a persistent login cookie).

evanspaon GitHub Résumé

Maybe, maybe-not. Couple things: some of my "personal projects" are more than just learning some new things. Often the project is for scratching an itch, and is a useful thing to me. That's the type of stuff that I will "polish." This forces me to not only learn the new language, but to write code idiomatically, write unit tests, etc.

For "junk projects" that are solely to play around with some new thing, I think it's okay to make that clear in the README of the project and still put it in a public repo. If I'm an employer, I'm going to like the fact that you're actively learning new things; if it's a "play" project, made clear in the README, I wouldn't hold against you writing crappy code. Instead, I'll be more impressed that you're actually learning new things. Just my $.02.

evanspaon GitHub Résumé

But what about personal projects? For me, the best way for learning new programming languages, libraries, techniques, etc, is to build something with that language. Naturally, I put this type of work into a public repo on Github and slap an OSS license on it. It's a great way to learn, but also to showcase your work to potential employers (or fellow hackers, etc).

evanspaon Coffee shops look to oust 'laptop hobos'

So is the one by me. When I asked the barista why, she said it helps keeps the fruit-flies away from the bakery items. I just bring a sweatshirt with me when I go.

evanspaon “What part of Milner-Hindley do you not understand?”

Movie reference. The Princess Bride.

evanspaon Everything about Java 8

Getters / Setters don't automatically mean that the internal state of an object is exposed. For example, an object may internally have mutable linked-list of something, but a Getter that returns an array (immutable) of immutable members.

What is the alternative to Getters / Setters (or, properties, which is basically just syntactic sugar) in an OO language?