RSS feed [root] /interview /design /weblog



title search:


Sat Feb 24 23:42:33 HKT 2018


(google search) (amazon search)
download zip of files only

Mon Mar 19 22:28:19 HKT 2018 From /weblog/design/interview


I love the tool that Linus using -[..]23/stiff-asks-great-programmers-answers/ and here is the abstract -

Ted interview with Linus -

Not really interview, just a discuss of what programmer difference from other -[..]in-on-codewhat-makes-you-able-to-program

Vote for most-influential-programmers -[..]02/most-influential-programmers-results/

Few links about Knuth -

Not really an interview, just with few pointers of few articles -

Robin Milner, creater of ML -[..]nology/2010/apr/01/robin-milner-obituary

Things Every Programmer Should Know -[..]things-every-programmer-should-know.html

egnyte -[..]ons-learned-in-building-and-scaling.html

(google search) (amazon search)

Sat Feb 24 23:42:46 HKT 2018 From /weblog/design/interview


Do the simple thing first.
Do fewer things better.
Upfront work but can pay huge dividends.
Don’t reinvent the wheel.
Nothing lasts forever.[..]-from-5-years-of-building-instagram.html

(google search) (amazon search)

Fri Feb 02 10:19:00 HKT 2018 From /weblog/design/interview


(google search) (amazon search)

Thu Feb 23 16:14:03 HKT 2017 From /weblog/design/interview


Interview with JOOQ founder -

(google search) (amazon search)

Tue Nov 29 00:12:57 HKT 2016 From /weblog/design/interview


"They build their own infrastructure for performance, reliability, and cost control reasons. By building it themselves they never have to say Amazon went down because it was company X's fault. Their software may not be more reliable than others, but they can fix, debug, and deployment much quicker than when working with a 3rd party."

Shel Kaphan -

(google search) (amazon search)

Sun Oct 16 01:52:15 HKT 2016 From /weblog/design/interview


How yahoo use Hadoop for machine learning -

(google search) (amazon search)

Thu Dec 03 10:33:50 HKT 2015 From /weblog/design/interview


(google search) (amazon search)

Thu Sep 10 14:18:31 HKT 2015 From /weblog/design/interview

Martin Odersky

One of the challenges we were facing is we wanted to be both functional and object-oriented. We had very early on the notion that immutable objects would become very, very important. Nowadays everybody talks about immutable objects, because people think they are a key part of the solution to the concurrency problems caused by multi-core computers. Everybody says, no matter what you do, you need to try to have as much of your code using immutable objects as possible. In Scala, we did that very early on. Five or six years ago, we started to think very hard about immutable objects. It actually turns out that a lot of the object-oriented field up to then identified objects with mutability. For them, mutable state and objects were one and the same: mutable state was an essential ingredient of objects. We had to, in essence, ween objects off of that notion, and there were some things we had to do to make that happen.

(google search) (amazon search)

Thu Jan 09 10:40:28 HKT 2014 From /weblog/design/interview

Maurice Herlihy[..]012/05/interview-of-maurice-herlihy.html

(google search) (amazon search)

Sun Feb 03 11:10:31 HKT 2013 From /weblog/design/interview

Jim Showalter

Principal engineer at Intuit -[..]im-showalter-of-intuit.html&site=jw_core

(google search) (amazon search)

Tue Dec 18 00:49:34 HKT 2012 From /weblog/design/interview

Alan Kay

Not interview, but a lot of useful link -[..]0_h&elq=c2568ee4975f4e69b244d72a9a8e2487

(google search) (amazon search)

Wed Oct 19 21:04:52 HKT 2011 From /weblog/design/interview


Discuss about C and C++ -[..]int?articleId=184408272&siteSectionName=

Discuss about history of C, UNIX and GO -[..]rint?articleId=229502480&siteSectionName

(google search) (amazon search)

Sun Oct 16 23:52:23 HKT 2011 From /weblog/design/interview

Continuous Delivery

Overview of CD, and some Q & A -

(google search) (amazon search)

Sun Oct 16 23:51:03 HKT 2011 From /weblog/design/interview

Kent Beck

Passion of coding make a lot of difference -[..]/07/interview-with-kent-beck-circa-2001/

(google search) (amazon search)

Thu Dec 31 00:46:40 HKT 2009 From /weblog/design/interview

Rod Johnson

Lessons Learned From Java EE’s Evolution, discuss about value of standard and opensource -

(google search) (amazon search)

Thu Dec 10 00:01:54 HKT 2009 From /weblog/design/interview

Ralph Johnson[..]h-Johnson-Parallel-Programming-Patterns#

(google search) (amazon search)

Tue May 06 14:25:04 HKT 2008 From /weblog/design/interview

Donald Knuth

Donald Knuth on Multi-Core, Unit Testing, Literate Programming, and XP:

I also must confess to a strong bias against the fashion for reusable code. To me, "re-editable code" is much, much better than an untouchable black box or toolkit. I could go on and on about this. If you’re totally convinced that reusable code is wonderful, I probably won’t be able to sway you anyway, but you’ll never convince me that reusable code isn’t mostly a menace...

(google search) (amazon search)

Tue Apr 29 01:46:55 HKT 2008 From /weblog/design/interview

Bjarne Stroustrup

Nice message cover DSL, IDE, multiple dispatch, message passing, and more

(google search) (amazon search)

Sun Nov 11 23:32:58 HKT 2007 From /weblog/design/interview

Martin Fowler interview

The discussion of "Flexibility and Complexity" and "Flexible versus Reusable" answer my long question of how to have flexibility code with simple design.

Another interview -

(google search) (amazon search)

Fri Aug 10 01:59:30 HKT 2007 From /weblog/design/interview

Erich Gamma

Erich Gamma: A pattern is always a problem-solution pair that can be applied in a particular context. Although the solutions might look similar in different patterns, the problems they are solving are different. In fact from ten thousand meters most patterns solve a problem by adding a level of indirection. What is interesting is how this indirection comes about and in particular why it needs to happen.
Therefore if you just look at the solution to the problem, it isn't that enlightening and everything starts to look the same. When we wrote design patterns we often had this feeling??hey all started to look like the Strategy pattern.

(google search) (amazon search)

Sun Apr 15 19:26:55 HKT 2007 From /weblog/design/interview

Interview of Netbean developers

Interview of netbean developers, I feel this is a lot more promotion than sharing of technology. However, these still valuable -[..]ree_interviews_with_language_programmers

(google search) (amazon search)

Thu Oct 12 15:49:07 HKT 2006 From /weblog/design/interview

Ken Arnold interview

Have anyone read "Effective Java"? Compare the "item 10: Override clone judiciously" with this interview is fun

No perfect design because we need difference design trade off for difference task, like performance, time, resource, ....
No perfect design because difference user have difference expectation of API ....
No perfect design because requirement change by time

(google search) (amazon search)

Thu Oct 12 15:48:27 HKT 2006 From /weblog/design/interview

Pragmatic Programmer

*Dave Thomas*: You have to accept the fact that you're not going to get it right the first time. And you're not going to get it perfectly right the second or third time. You'll never get it perfectly right, but along the way you can get better and better . To do that, you have to discipline yourself to apply a reflective process to what you do.
*Bill Venners*: What do you mean by reflective process?
*Dave Thomas*: You always have to look back at what you did and ask, "How did I do that? Could I have done it better? Did I have to do it at all?" Get into the habit of doing that with everything you do. That way, you're consciously forcing yourself to reevaluate the way you do things.

Full message:

(google search) (amazon search)

Thu Oct 12 15:47:11 HKT 2006 From /weblog/design/interview

Scott Meyers interview

I think a schism existed between the C++ community, which was still focused on language issues, and the other prominent development communities, which pretty much left the language alone. Java already had exceptions, but didn't have templates and had nothing like the STL. Yet the Java community focused on writing a whole bunch of libraries that everybody can assume will exist everywhere, libraries that will let you write applications really quickly. The end result is, we have templates in C++, but there's no way to write user interfaces or talk to databases. Java has no templates, but you can write user interfaces up the wazoo and you can talk to databases with no trouble at all.

(google search) (amazon search)