News for hackers. Stuff that matters.

clark

Re:TurboGears joins the Pylons Project on Wednesday December 29, 2010 @04:47PM (#2050285)
glad you expected the response -- you're a classic troll; complete with creating a dummy account, the opening line stating a stupidly absurd negative comment, and the closing line with the insinuation that the devs go through all the pain of running a project for their own edification
Re:TurboGears joins the Pylons Project on Tuesday December 28, 2010 @01:47PM (#2046309)
Nice trolling.
Re:LinkedIn forcing password resets due to Gawker hack on Tuesday December 14, 2010 @10:58AM (#2004533)
LinkedIn is one of the sites that limit the length of your password and what it can maintain. I've emailed their staff many times, and they simply respond that those are the password restrictions.
Re:Ask HN: How do I crawl out of the "Senior Engineer" hole? on Monday November 15, 2010 @04:51PM (#1908017)
The alternative track is 'research scientist'. That's the title where you get to play on the company's dime. Unfortunately, it usually requires a PhD and have a strong publication history.
Re:HTTP cookies, or how not to design protocols on Friday October 29, 2010 @12:50PM (#1847915)
In my opinion, session cookies are primarily used as a work around since HTTP Authentication is incredibly ugly. Perhaps if that core problem was addressed, the need for cookies would be dramatically reduced.
Re:Ask HN: Where to have your honeymoon? on Wednesday August 25, 2010 @08:46AM (#1632659)
http://en.wikipedia.org/wiki/Cusco

The mountains and Inca ruins are absolutely stunning; even in July it should be quite temperate there (it doesn't really freeze), but, since it's winter, it won't be hot so you'll need a modestly warm jacket.

Re:Criminal Overengineering on Wednesday June 23, 2010 @09:49AM (#1454900)
I think frameworks have to be engineered carefully; the use of the strategy pattern in the example is a typical and is very soundly used in a framework. I think the problem is that developers write far too many frameworks than they should. Interestingly enough, it's code that isn't extensible that ends up being a framework -- mostly because the authors have time to focus on documentation, support, user interface and the like.