Ask HN: Does anyone dream of code?
111–120 of 146 posts
Re: Ask HN: Does anyone dream of code?
#112Other then that I never dream of code, but sometimes when I am half asleep in bed I start thinking about issues and playing out scenarios I could try to fix something, or implement a new feature.
Re: Ask HN: Does anyone dream of code?
#113Re: Ask HN: Does anyone dream of code?
#114Yes, but not in the literal sense for me. I never see any text or code but rather some abstract version of the problem I'm trying to solve. I dislike it to be honest, it makes me feel like I'm not getting any rest, especially when I wake up in the middle of the night from a code dream only to continue in that loop while I'm half awake. One time I went to sleep after starting a take home code test for a job interview;…
Would you mind sharing why they (said they) ultimately chose not to extend an offer? Just curious about an anecdote from a hiring/recruiting perspective.
Re: Ask HN: Does anyone dream of code?
#115Earlier quoted context omitted.
This reminded me of a dream I used to have of getting into the car, opening up the Chrome developer tools, and using Javascript to drive.
> This reminded me of a dream I used to have of getting into the car, opening up the Chrome developer tools, and using Javascript to drive. An aside. Reading some of the hilarious comments here I am inclined to think they could be compiled into a bestselling nerd comic
Re: Ask HN: Does anyone dream of code?
#116Actually terrifying thinking about it again. Made me very wary of live programming XD
Re: Ask HN: Does anyone dream of code?
#117Re: Ask HN: Does anyone dream of code?
#118The ST had a notoriously slow text output system. The display was a bitmap and there was no hardware acceleration. Somebody called Darek Mihocka came out with 'Quick ST' which made the text display quicker than stock. As a newbie I wanted to beat this, so I learned 68000 assembly and did the usual optimisation - unrolling loops, precomputing bitmaps etc. I got faster than Quick ST but then he had an update which nearly doubled my speed.
I did everything I could to work out what he'd done, including looking at the Motorola reference manuals, nothing came up. I was going crazy. Bear in mind these were the days when there was no middleware, it was you versus the hardware, and if they did it better it's because their code was better.
So I went to bed one night and the 'move.p' opcode came to mind. I woke up and read about it - turns out this opcode took a 16 bit number and split it into 2 8bit codes and placed them 2 bytes apart. This matched the ST interleaved bitmap perfectly - I doubled my speed and beat Darek.
So, yeah, a dream did actually improve my code. I do miss those days where decent code beat driver, middleware and other issues.