I somehow decided I needed to cheat to pass a certain exam because I was basically crap at memorizing stuff. So I used an analogue wireless headphone, an induction loop around my neck and a mobile phone. Since I lacked an accomplice to dictate, I read aloud the hundreds of pages and recorded myself, careful to preserve and properly serialize things like complex formulas. This was before the era of iPods and SDCard pl…
I would 100% talk about this in interviews depending on the interviewer. I can think of a couple interviews I had in SF that would probably be appreciative of this level of effort because you principally reject memorization.
Ask HN: What's the hardest problem you've ever solved?
121–130 of 441 posts
Re: Ask HN: What's the hardest problem you've ever solved?
#122I solved a performance bug that was probably going to cost my company the majority of our customers if we didn't sort it out as it made the app unusable. It had been going on for months. None of the dev team had any idea. APM was throwing out a bunch of red herrings. I haven't written a line of code in the app or a line of production Java (the codebase language) in my life. In the end I tracked it down to a single li…
Sometimes selectively commenting stuff out really is the best way to figure out what is wrong.
Re: Ask HN: What's the hardest problem you've ever solved?
#123Re: Ask HN: What's the hardest problem you've ever solved?
#124Editing a Minecraft save with sh and dd to resurrect my girlfriend's wolf.
Re: Ask HN: What's the hardest problem you've ever solved?
#125Oh, and debugging a DOS TSR (Terminate and Stay Resident) API for realtime communications to mainframes and other information sources (async and X.25) while running under Windows 386 - Windows 3.11. Every different network stack (IPX, Netbeui, LanMan, etc.) presented a new brainfucker of a problem.
Re: Ask HN: What's the hardest problem you've ever solved?
#126Re: Ask HN: What's the hardest problem you've ever solved?
#127Building a hardware product from scratch, getting it manufactured, and selling it.
Re: Ask HN: What's the hardest problem you've ever solved?
#128Earlier quoted context omitted.
One thing universities should teach is efficient problem solving. If it was more work to cheat than to memorize, I'd say you might want to re-evaluate whether "not memorizing things" is a principle you should cling so dogmatically to.
I'm sure he learned much more useful stuff by coding up that monstrosity, and in the real world he can just google to look up those formulas he didn't memorize. The fully elaborated version of the underlying principle is probably something like: "I have much better ways to spend my time than on memorizing formulas that I could easily look up later".
Re: Ask HN: What's the hardest problem you've ever solved?
#129Earlier quoted context omitted.
I would 100% talk about this in interviews depending on the interviewer. I can think of a couple interviews I had in SF that would probably be appreciative of this level of effort because you principally reject memorization.
Admitting to significant academic fraud during a job interview is a very, very bad idea. Furthermore, I would question the ethics and morality of any company that said "Wow, you solved an incredibly tough problem in order to commit fraud. Boy, are we the place for you!"
Re: Ask HN: What's the hardest problem you've ever solved?
#130Armed with a PCI analyzer, I figured out that it was a race condition where the firmware on the chip would raise an interrupt to the PC. And they would clear the interrupt right at the moment where the firmware wanted to issue a new interrupt.
If performed in the wrong order, the PCI interrupt stayed high even after the PC thought it was already serviced.
The solution was to just switch around 2 lines of code in the firmware, but it took two weeks to figure that out.
Not that long, but it was an insidiously subtle mistake.