carfield.com.hk

data.txt

2024-08-25T08:17:24Z

Interview with JOOQ founder - https://www.infoq.com/news/2017/02/data-geekery-releases-jooq-3-9

The Untold Story of SQLite - https://corecursive.com/066-sqlite-with-richard-hipp/ https://www.infoq.cn/article/Y1GrKv1JeIJAyqwG8cab

Jeff Dean.txt

2023-02-28T00:53:04Z

How Google’s Jeff Dean became the Chuck Norris of the Internet. - https://slate.com[..]me-the-chuck-norris-of-the-internet.html

谷歌最好的程序员 Jeff Dean：我用过 18 种编程语言 - https://www.infoq.cn/news/6DxKgF0KO8kgkYh3EIDT https://twitter.com/JeffDean/status/1627885526127874049

The Friendship That Made Google Huge - https://www.newyorker.com[..]/10/the-friendship-that-made-google-huge https://www.infoq.cn/article/rAJiubRpi9xSl_LEhI2N

Collections.txt

2022-01-19T13:44:27Z

http://www.javacodegeeks.com[..]7/top-97-things-every-programmer-or.html

I love the tool that Linus using - http://sztywny.titaniumhosting.com[..]23/stiff-asks-great-programmers-answers/ and here is the abstract - http://www.ultrasaurus.com/sarahblog/archives/000322.html

Ted interview with Linus - https://ideas.ted.com/the-wisdom-of-linus-torvalds/

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

Vote for most-influential-programmers - http://blog.assembleron.com[..]02/most-influential-programmers-results/

Few links about Knuth - http://www.codinghorror.com/blog/archives/001034.html

Not really an interview, just with few pointers of few articles - http://www.codinghorror.com/blog/archives/000987.html

Robin Milner, creater of ML - http://www.guardian.co.uk[..]nology/2010/apr/01/robin-milner-obituary

Things Every Programmer Should Know - http://www.javacodegeeks.com[..]things-every-programmer-should-know.html

egnyte - http://highscalability.com[..]ons-learned-in-building-and-scaling.html

Bram Moolenaar: "Vim is a very important part of my life." - https://evrone.com/bram-moolenaar-interview

Linus Torvalds.txt

2021-06-18T01:04:27Z

https://www.brynmawr.edu/cs/resources/beauty-of-programming

Java.txt

2021-01-24T12:50:28Z

http://blog.eisele.net/2011/09/heroes-of-java.html

http://www.infoq.com/interviews/doug-lea-fork-join

http://www.infoq.com/author/Martin-Thompson https://www.infoq.com/news/2016/06/programmers-write-better-code

https://freecontent.manning.com/interview-with-brian-goetz/

facebook.txt

2018-02-24T15:42:46Z

Do the simple thing first.
Do fewer things better.
Upfront work but can pay huge dividends.
Don’t reinvent the wheel.
Nothing lasts forever.

http://highscalability.com[..]-from-5-years-of-building-instagram.html

https://www.infoq.com/interviews/adams-php-facebook

wechat.txt

2018-02-02T02:19:00Z

http://www.infoq.com/cn/articles/wechat-video-call

Amazon.txt

2016-11-28T16:12:57Z

"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."

http://highscalability.com/amazon-architecture

Shel Kaphan - http://www.infoq.com/cn/articles/talk-with-amazon-shel-kaphan

yahoo.txt

2016-10-15T17:52:15Z

How yahoo use Hadoop for machine learning - https://www.infoq.com/articles/peter-cnudde-yahoo-big-data

UncleBob.txt

2015-12-03T02:33:50Z

http://www.infoq.com/news/2015/11/uncle-bob-oath-programmer

Martin Odersky.txt

2015-09-10T06:18:31Z

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.

http://www.artima.com/scalazine/articles/goals_of_scala.html

Maurice Herlihy.txt

2014-01-09T02:40:28Z

http://teachingintrotocs.blogspot.fr[..]012/05/interview-of-maurice-herlihy.html

Jim Showalter.txt

2013-02-03T03:10:31Z

Principal engineer at Intuit - http://www.javaworld.com[..]im-showalter-of-intuit.html&site=jw_core

Alan Kay.txt

2012-12-17T16:49:34Z

Not interview, but a lot of useful link - http://www.codinghorror.com/blog/archives/001213.html

http://www.drdobbs.com[..]0_h&elq=c2568ee4975f4e69b244d72a9a8e2487

K&R.txt

2011-10-19T13:04:52Z

Discuss about C and C++ - http://drdobbs.com[..]int?articleId=184408272&siteSectionName=

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

Continuous Delivery.txt

2011-10-16T15:52:23Z

Overview of CD, and some Q & A - http://www.infoq.com/articles/humble-farley-continuous-delivery

Kent Beck.txt

2011-10-16T15:51:03Z

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

Rod Johnson.txt

2009-12-30T16:46:40Z

Lessons Learned From Java EE’s Evolution, discuss about value of standard and opensource - http://www.infoq.com/presentations/Lessons-Learned-from-Java-EE

Ralph Johnson.txt

2009-12-09T16:01:54Z

http://www.infoq.com[..]h-Johnson-Parallel-Programming-Patterns#

Donald Knuth.txt

2008-05-06T06:25:04Z

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...

http://www.artima.com/forums/flat.jsp?forum=276&thread=229705

Bjarne Stroustrup.txt

2008-04-28T17:46:55Z

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

http://msdn2.microsoft.com/en-us/magazine/cc500572.aspx

Martin Fowler interview.txt

2007-11-11T15:32:58Z

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

http://www.artima.com/intv/flexplexP.html

Another interview - http://www.infoq.com/presentations/modifiability-fowler

Erich Gamma.txt

2007-08-09T17:59:30Z

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.

http://www.artima.com/lejava/articles/patterns_practice.html

Interview of Netbean developers.txt

2007-04-15T11:26:55Z

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

Ken Arnold interview.txt

2006-10-12T07:49:07Z

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

http://www.artima.com/intv/issuesP.html

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

http://www.artima.com/intv/perfect.html