HNHacker News
TopNewBestAskShowJobs

joshsegall

143 karma · joined February 13, 2011

submissionscomments
joshsegall··on Don't write on the whiteboard
The title doesn't do the article justice. As an interviewer myself I think it's terrible advice. Certainly if you think it'll make or break your interview go ahead and ask to write on paper, but thinking through problems and expressing them on a whiteboard is an important skill at a lot of companies.

Many of his other points are good, although a lot of it boils down to being a top notch developer and letting it show in the interview. Being a top notch developer is the hard part, and good interviewers (at places a top notch dev would want to work at) will typically identify your skills even if you don't follow this specific advice.

+1 for using python--it's great for getting through coding questions quickly and efficiently, allowing exploration of various twists the interviewer may throw at you.

joshsegall··on Effects on the deficit in one graph
Well it certainly seems you have a bias as well. Let me share mine: all this "debate" is irrelevant and only serves as a distraction from our real problem, which is prosperity not deficits. In no sense is America broke. We easily find trillions of dollars to spend on wars and bailouts but whine incessantly about a few million or a couple billion on initiatives that would actually spur growth and contribute to lasting well-being of our country's citizens. It's all about priorities and debating how to cut ourselves to success is worse than useless. It's preventing us from having the conversation we really need to have about how to move our economy into the 21st century.
joshsegall··on Vibrations Invisible to the Human Eye Shot at 1,000 Frames Per Second
I was surprised how much some of those shots resemble the effects you see in video games physics simulations and online "toy" physics sandboxes. I figured the real world would be more noisy but these results are quite uniform and beautiful. I'll have to give our physics modeling more credit from now on!
joshsegall··on One day, we'll all be programmers
This post is rife with bad assumptions. Here are some big ones:

1. Dexterity is NOT the "last mile" gap to having robots in minimum wage jobs. I don't care if the robot can flip a burger, can it recognize a grease fire (and put it out, and clean up afterwards?) Can it recognize a moldy bun or if the special sauce is spoiled? While low wage retail jobs don't require years of specialized training, they do take advantage of a lot of innate human skills. Most of the mechanical aspects of these jobs are already automated.

2. Good software is not created by people sitting in cube farms programming. In projects of any size it's more about communication among developers and between developers and other business functions than writing code in isolation.

3. Not everyone can be a programmer, and most that could be won't want to (and I predict won't have to). I'm sure you can invent trivial examples that anyone can do, but then you're not saying much. There are large classes of people that can't program a VCR or do long division, let a alone construct a slightly involved program. As someone who's been involved in research that attempts to teach average people how to "program", I feel confident that we will never see a large portion of people become programmers.

joshsegall··on Orthogonality is Pretentious
This is a silly argument and a misinterpretation of the purpose of orthogonality. Orthogonality is not a goal in itself, nor is it's purpose to eliminate redundancy. It's a tool to reduce entanglement of features. It helps simplify designs by ensuring that changes to one feature do not affect other features. This reduces the chance of unintended or inconvenient side effects when making changes. This is helpful for software architecture in general, not just programming language design.
joshsegall··on Oracle Introduces New JSR to Evolve Java Community Process
What are the odds that the new process comes out before Java 7?
joshsegall··on Java.next() - Scala: The Revenge of the Static Typing
I agree that both static and dynamic type systems have their place, but I think this article misses the biggest con of Scala to me: the push towards stronger typing, such as that of Haskell.

I estimate fewer than 5% of programmers I've worked with truly understood type theory deeply enough to program a complex system with them properly. In addition, 0% of the systems I've worked on required such strong typing to achieve success.

Typing in Java is comparatively weak, which I view as a feature because it allows you to make more practical trades between expressiveness and simplicity.

joshsegall··on What are some startup ideas that persistently fail?
Semantic understanding (including the Semantic Web) will always be alluring, but it's just not going to happen. We can't agree on semantics in real life except in small groups or in very shallow ways. Computers just aren't going to be any better at it until we create something smarter than ourselves.

I'm not saying some of the automated semantic extraction technologies are useless. Some of them are very cool, and it is absolutely the way we should be heading (waiting for humans to tag everything is a waste of time). However, we need to recognize while this path is taking us somewhere good it will ultimately fall short of the vision--much in the same way that the AI field has given us some great improvements without approaching a true artificial general intelligence.

joshsegall··on Simple, Effective Password Management with Keepass and Dropbox
I've never heard of KeePass before. I use Password Safe, which is very effective and has been around for almost a decade as open source.

http://passwordsafe.sourceforge.net/

joshsegall··on Hiring Developers: You're Doing It Wrong
It seems fairly obvious that a pure tech interview doesn't screen for cultural fit, and that you need to have some form of behavioral/cultural assessment as part of the interview process.

Depending on how much time you have to interview (and I suggest you take the time if you're going to hire someone!) the "standard" dev interview can do pretty well at weeding out candidates who clearly lack basic skills. Joel Spolsky is a proponent of this and I agree.

I've found that passion is a great indicator of future success, and you can usually get a good quick read on whether they are serious about software development by asking people about their favorite projects, what they spend their time working on, and what interesting things they see happening in the field.

joshsegall··on Math Becomes Music: What Pi Sounds Like
If you're looking for songs about pi, I love this one by Hard n Phirm: http://www.youtube.com/watch?v=mDu351QNoZE

The video (by Keith Schofield) is also awesome.

joshsegall··on Google Details Chrome's Background Feature
Well this needs a better title. I almost didn't read it because I thought it was about the background image feature on the google homepage.
joshsegall··on A word about résumés.
With electronic resumes the number of pages is less relevant, but I agree that you should limit the content to what's relevant and can be read quickly. I review a lot of resumes and two is about my limit before I give up. If I can't tell by then if you're qualified for a phone screen then it's not usually worth reading pages 3-6 (yes I've seen those, even up to 12!)

Honestly, you shouldn't really need a second page unless all your Nobel Prizes don't fit on the first.

joshsegall··on An Intro To The Semantic Web: Why You Need To Know About It Sooner Than Later
I'm with henrikschroder and call bullshit on semantic web being a big thing, let alone the next big thing. It's an attractive idea, but flawed. There are some niches where structured semantic data will flourish (see examples in other comments), but it will be a vast subset of the web.

A better idea is extracting latent semantic information from the existing messy web. However, "meaning" is extremely difficult to characterize, and attempting to encode it in an interoperable manner inevitably leads to a lowest common denominator approach. That will probably still provide tons of value and be much more ubiquitous than structured data, but will ultimately be shallow and fall far short of the vision most semantic web proponents evangelize.

joshsegall··on 10 Awesome Theorems & Result
My favorite was always Fubini's theorem in 3D calculus the result of which is basically "meh, it doesn't matter which order you integrate"
← PreviousPage 2 of 2