Live data from Hacker News

Interview with Douglas Crockford

evrone.com

1–10 of 107 posts

Re: Interview with Douglas Crockford

#4

Nice one! Is it just me though, or is he becoming quite repetitive in what he says in interviews these days, e.g. retire Javascript?

Not sure the format helped. No follow-up questions, no real thread of discussion. If you are faced with an interview like that (and for people interviewed regularly I imagine there are tons of interviews like that), why deviate from your stock answers?

Re: Interview with Douglas Crockford

#6

Nice one! Is it just me though, or is he becoming quite repetitive in what he says in interviews these days, e.g. retire Javascript?

Not sure the format helped. No follow-up questions, no real thread of discussion. If you are faced with an interview like that (and for people interviewed regularly I imagine there are tons of interviews like that), why deviate from your stock answers?

One of the answers contains a link ("You can see proof [here]") and another references a previous answer in a way you would only do in writing ("See my previous answer")

Fairly sure it wasn't really an "interview", and just an emailed response to a list of questions.

Re: Interview with Douglas Crockford

#8
Retire all the things. What makes this industry so…cyberpunk, is that nothing entirely goes away.

Linux is probably the last time something was really built from scratch. Most commercial software in use today is dependent on code written in the 80’s and 90’s.

So, yes, there is a need for new software to match the new paradigms, but the task of starting from scratch is colossal.

Re: Interview with Douglas Crockford

#10
I thought this part was rather interesting:

> Evrone: You spread the idea that developers should read each other's code regularly…

> Douglas: In filmmaking, there is a time in the morning called "dailies", when the previous day's footage is examined. It looks like everyone is just sitting around watching movies and wasting time, but it is critically important in finding problems early and assuring the quality of the product. I believe that we should do the same thing in programming. We have a time every morning when the team gets together and reviews all of the code and designs that were developed the previous day.

Post reply on HN