Hacker News Reader

leklundon Is anyone playing with the combination of generative AI and OpenCyc?

Sure average humans don’t do that, but this is hackernews where it’s completely normal for commenters to confidently answer questions and opine on topics they know absolutely nothing about.

leklundon Running GitHub on Rails 6.0

“and I’ve never see a Rails app age well.”

Seems like this describes any app in any language I’ve ever worked on. Certainly Rails apps are more prone to this phenomenon because of the low barrier entry. Having worked with apps that have grown from Rails 2 through 5 (and soon 6) it’s quite possible to build Rails apps that “age well”.

Case in point for a Rails app that can age well is GitHub. When they launched in 2008 they were probably using Rails 2.0.2 (best guess based on release notes).

leklundon Creating a Computer Voice That People Like

The Talking Moose circa 1987 using the Macintalk voice of 'Fred'-- what more could we need?

leklundon Why Some Men Pretend to Work 80-Hour Weeks

What struck me the most about the article was the employee who was denied a promotion because of his 6-weeks of unpaid FMLA leave. That's not only unethical it's also against the law (as is denying FMLA). I can understand the lure of the huge salary but having to work in such a toxic culture would never make it worth it to me.

leklundon Ask HN: Who is hiring? (April 2015)

travisjgood: I'd love to see what openings you currently have but the link to jobs.lever.co on your jobs page returns a 404.

leklundon It’s Comcastic, Or: I Accidentally Bought a House Without Cable

Maude: Lord, you can imagine where it goes from here.

The Dude: He fixes the cable?

Maude: Don't be fatuous, Jeffrey.

leklundon Apple – Live – September 2014 Special Event

Seconded! I've been wanting to replace an older iMac with a mini for a some time now. The mini is in dire need of a refresh given that it's been since 2012 that the guts were updated and 2010 since the design was updated.

leklundon Interviewing in Silicon Valley

This is the same approach we've taken with candidates. We start with a phone screen and then a simple coding problem submitted via email. When we bring them in for an interview they spend time with with a few developers working collaboratively on a problem. If possible, it's a bit of work from the current iteration. Working together on real-world code has been surprisingly effective. I was skeptical at first, but it has been very helpful in weeding out candidates who had good cv's and probably could have coded a really great algorithm to traverse a binary tree but weren't great with solving real world problems.