News for hackers. Stuff that matters.
Re:Programmer problem solving sequence: should it be like this? by fogus on Monday February 28, 2011 @09:15AM (#2271243)

     11. Profit!
What defines profit in this case? I realize that this post was likely tongue-in-cheek, but I think my question is still valid. I'm trying to explore the answer to that question myself: http://blog.fogus.me/2011/02/28/the-keepers-of-answers/

But I'm not sure if I've hit on it yet. Maybe I should try Quora. ;-)

Re:Programmer problem solving sequence: should it be like this? by praptak on Monday February 28, 2011 @09:35AM (#2271297)
Valid question. The result in this case was getting a patch that was already committed into the development branch, just not yet released.

I actually did debug it (i.e. I found the cause of the bug, just didn't know whether fixing it in the most obvious place wouldn't break anything elsewhere - it occurs it might) but my fix would probably be suboptimal and I'd probably waste the developers' time with a superfluous bug report (and maybe the suboptimal patch too).

Re:Programmer problem solving sequence: should it be like this? by shaggyfrog on Monday February 28, 2011 @07:20PM (#2273617)
profit: From Middle English profit < Old French profit (French: profit). < Latin profectus (“advance, progress, growth, increase, profit”) < proficere (“to go forward, advance, make progress, be profitable or useful”); see proficient. http://en.wiktionary.org/wiki/profit

Similar use in French means something like "I took advantage [of it]".

...or it could just be a reference to the Underpants Gnomes...