News for hackers. Stuff that matters.
Re:Ask HN: Coding Quickly; How? by nostrademons on Sunday May 03, 2009 @01:06AM (#590560)
Something that Google's first employee said recently stuck with me: "I would say the single most important thing an engineer can do to be effective is to pick the right problem to work on." Alas, he had no idea how to do that (or rather, he obviously had a very good idea how to do it, but was unable to put it into words), but the quote resonates a lot with my experience. I've wasted so much time on projects that in retrospect weren't really all that important - I coded them quickly, and learned quite a bit that came in handy later, but the problems themselves were basically non-problems.
Re:Ask HN: Coding Quickly; How? by ojbyrne on Sunday May 03, 2009 @01:10AM (#590565)
My stats prof used to take about "Type 3 errors." Type 1 and 2 errors are part of a basic stats course. Type 3 = "solving the wrong problem."
Re:Ask HN: Coding Quickly; How? by SapphireSun on Sunday May 03, 2009 @02:06AM (#590618)
My understanding of type III was that it was "Right for the wrong reasons." I suppose it might not be a standard term ;-)