On 2016-01-21 11:01, deadalnix wrote:
> On Thursday, 21 January 2016 at 05:14:03 UTC, thedeemon wrote:
>> On Wednesday, 20 January 2016 at 11:07:16 UTC, Rikki Cattermole wrote:
>>> From what Walter said, they all knew c. So not really too low level
>>> for them.
>>
>> To me it looked like:
>> Walter: "You all write in C, right?"
>> Audience silent with expression on their faces "What is C? We've only
>> heard about JavaScript".
>> ;)
>
> Isn't C that language that compiles to javascript ?

No, it compiles to CoffeeScript which then compiles to JavaScript.

-- 
/Jacob Carlborg

On Wednesday, 20 January 2016 at 03:13:38 UTC, deadalnix wrote:
> https://www.reddit.com/r/programming/comments/41sdzj/walter_bright_on_being_a_developer_running_an/

I also prefer to work at night, mainly because of silence. A simple test: listen to a song in your headphones at day, then listen to it on the same volume level at night. Recently I almost stopped listening to music (even ambient) while I write code, because it turns out I do less mistakes and overlook things not so often, when I code in silence. It makes coding less entertaining, but more productive.

On 1/21/2016 5:06 AM, burjui wrote:
> Recently I almost stopped listening to music (even ambient) while I
> write code, because it turns out I do less mistakes and overlook things not so
> often, when I code in silence. It makes coding less entertaining, but more
> productive.

The trick is to turn the volume down so the music is barely perceptible.

On Wednesday, 20 January 2016 at 03:13:38 UTC, deadalnix wrote:
> https://www.reddit.com/r/programming/comments/41sdzj/walter_bright_on_being_a_developer_running_an/

I really enjoyed this talk, it's very interesting to see how Walter works and to compare it with our own personal preferences.

Walter talks about how to manage the ebb and flow of motivation when working on a long term project. His suggestion of always doing some small bit of work on it on a daily basis was new to me and seems like a great idea. Personally I also like to rotate what I work on within the project, and will switch to something new and interesting when the everyday parts get boring. I'm pretty sure Walter also does this to maintain his own motivation, and this explains why he doesn't always work on what seems most important in the D world, but instead whatever is required to keep his own excitement for the project alive. A recent example is when he worked on optimising DMD instead of various other more mundane but arguably important tasks. The fact is, as developers we sometimes have to nourish our motivation even at the expense of delaying some of the more important but less rewarding work.