January 29th, 2011历年 JOLT 获奖书籍

1991

Annotated C++ Reference Manual. by Margaret Ellis, Bjarne Stroustrup

1.

The Art of Human-Computer Interface Design. by Brenda Laurel
2.

Programming Windows, 2nd Edition by Charles Petzold
3.

Turbo C++ DiskTutor, by Greg Voss, Paul Chui

1992

Object-Oriented Design with Applications. by Grady Booch

1.

Advanced C++: Programming Styles and Idioms. by James Coplien
2.

Object-Oriented Modeling and Design. by James rumbaugh, Michael Blaha, William Premerlani, Frederick Eddy, William Lorensen
3.

Object Lifecycles: Modeling the World in States. by Sally Shlaer, Steve Mellor

1993

Undocumented Windows. by Andrew Schulman, David Maxey, Matt Pietrek

Decline and Fall of the American Programmer. by Ed Yourdon

1.

Object-Oriented Software Engineering: A Use-Case Driven Approach. by Ivar Jacobson, Magnus Christerson, Patrik Jonsson, Gunnar Overgaard
2.

Literate Programming. by Donald Knuth
3.

Effective C++ by Scott Meyers

1994

Code Complete by Steve McConnell

Object-Oriented Design and Analysis with Applications, 2nd Edition. by Grady Booch

1.

Applied Cryptography. by Bruce Schneier
2.

Programming on Purpose, Vols. I and II. by P.J. Plauger
3.

Writing Solid Code. by Steve Maguire

1995

Essential Client/Server Survival Guide. by Robert Orfali, Dan Harkey, Jeri Edwards

1.

Debugging the Development Process. by Steve Maguire
2.

Design Patterns by Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides
3.

The Design and Evolution of C++. by Bjarne Stroustrup

1996

Thinking in C++, by Bruce Eckel

1.

About Face: The Essentials of User Interface Design. by Alan Cooper
2.

A Discipline for Software Engineering. by Watts Humphrey

1997

Rapid Development by Steve McConnell

1.

Creating a Software Engineering Culture. by Karl Weigers
2.

Pattern-Oriented Software Architecture by Frank Buschmann, Regine Meunier, Hans Rohnert, Peter Sommerlad, Michael Stal
3.

The Essential Distributed Objects Survival Guide. by Robert Orfali, Dan Harkey, and Jeri Edwards

1998

Object-oriented Software Construction. by Bertrand Meyer

1.

The Deadline: A Novel about Project Management. by Tom DeMarco
2.

UML Distilled: Applying the Standard Object Modeling Language by Martin Fowler, Scott Kendall
3.

Building Object Applications That Work, by Scott Ambler

1999

Component Software—Beyond Object-Oriented Programming. by Clemens Szyperski

1.

Anti-Patterns: Refactoring Software, Architectures, and Projects in Crisis. by William J. Brown, Raphael C. Malveau, Hays W. McCormick, Thomas Mowbray
2.

Software Architecture in Practice by Len Bass, Paul Clements, Rick Kazman
3.

Thinking in Java by Bruce Eckel

2000

Software for Use: A Practical Guide to the Models and Methods of Usage Centered Design. by Larry Constantine, Lucy Lockwood

1.

Extreme Programming Explained: Embrace Change by Kent Beck
2.

Software Requirements. by Karl E. Wiegers
3.

After the Gold Rush: Creating a True Profession of Software Engineering. by Steve M. McConnell

2001

Adaptive Software Development. by James A. Highsmith III

1.

Don't Make Me Think! A Common Sense Approach to Web Usability by Steve Krug
2.

Writing Effective Use Cases by Alistair Cockburn
3.

Secrets and Lies: Digital Security in a Networked World. by Bruce Schneier

2002

Effective Java by Joshua Bloch

1.

Agile Software Development. by Alistair Cockburn
2.

Software Craftsmanship by Pete McBreen
3.

Under Pressure and On Time. by Ed Sullivan

2003

Agile Software Development: Principles, Patterns and Practices by Robert C. Martin

1.

Documenting Software Architectures by Paul Clements, Felix Bachmann
2.

Test Driven Development: By Example by Kent Beck
3.

Patterns of Enterprise Application Architecture by Martin Fowler

Thinking in Java, 3rd Edition by Bruce Eckel

1.

Understanding Web Services: XML, WSDL, SOAP, and UDDI. by Eric Newcomer
2.

Core Java 2, Volume 1: Fundamentals by Cay Horstmann, Gary Cornell
3.

PHP and MySQL Web Development, 2nd Edition by Luke Welling, Laura Thomson

2004

Waltzing with Bears. by Tom DeMarco, Timothy Lister

1.

The Art of Unix Programming by Eric S. Raymond
2.

Lean Software Development: An Agile Toolkit by Mary Poppendieck, Tom Poppendieck
3.

The Pragmatic Starter Kit, by Dave Thomas, Andy Hunt

Test-Driven Development: A Practical Guide. by David Astels

1.

About Face 2.0: The Essentials of Interaction Design by Alan Cooper, Robert Reimann
2.

Agile Database Techniques: Effective Strategies for the Agile Software Developer. by Scott W. Ambler
3.

Code Reading: The Open Source Perspective by Diomidis Spinellis

2005

Head First Design Patterns by Elisabeth Freeman, Eric Freeman, Bert Bates, Kathy

1.

Joel on Software by Joel Spolsky
2.

Refactoring to Patterns by Joshua Kerievsky
3.

Software Factories: Assembling Applications with Patterns, Models, Frameworks, and Tools. by Jack Greenfield, Keith Short, Steve Cook, Stuart Kent, John Crupi

Better, Faster, Lighter Java. by Bruce A. Tate, Justin Gehtland

1.

C++ Coding Standards: 101 Rules, Guidelines, and Best Practices by Herb Sutter, Andrei Alexandrescu
2.

Hibernate: A Developer's Notebook. by James Elliott
3.

Java Developer's Guide to Eclipse, 2nd Edition. by Jim D'Anjou, Scott Fairbrother, Dan Kehn, John Kellerman, Pat McCarthy

2006

Prefactoring by Ken Pugh

1.

The Art of Project Management. by Scott Berkun
2.

Innovation Happens Elsewhere: Open Source as Business Strategy. by Ron Goldman, Richard P. Gabriel
3.

Producing Open Source Software: How to Run a Successful Free Software Project. by Karl Fogel

Agile Web Development with Rails by Dave Thomas, David Hansson, Leon Breedt, Mike Clark

1.

Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .NET Libraries by Krzysztof Cwalina, Brad Abrams
2.

Practical Common Lisp by Peter Seibel
3.

Why Programs Fail: A Guide to Systematic Debugging by Andreas Zeller

2007

Agile Software Development: The Cooperative Game by Alistair Cockburn

1.

Catastrophe Disentanglement. by E. M. Bennatan
2.

Practices of an Agile Developer by Venkat Subramaniam, Andy Hunt
3.

Software Estimation: Demystifying the Black Art. by Steve McConnell

Head First Object-Oriented Analysis and Design by B. McLaughlin, G. Pollice, D. West

1.

Code Quality by Diomidis Spinellis
2.

Refactoring Databases by Scott W. Ambler, P.J. Sadalage
3.

CSS: The Missing Manual by David Sawyer McFarland

2008

Beautiful Code by Andy Oram, Greg Wilson

1.

Manage It!: Your Guide to Modern Pragmatic Project Management by Johanna Rothman
2.

The Myths of Innovation by Scott Berkun
3.

Release It: Design and Deploy Production-Ready Software. by Michael T. Nygard

Continuous Integration: Improving Software Quality and Reducing Risk by Paul Duvall, Steve Matyas, Andrew Glover

1.

Head First SQL Your Brain on SQL: A Learner's Guide by Lynn Beighley
2.

The Rails Way by Obie Fernandez
3.

xUnit Test Patterns: Refactoring Test Code by Gerard Meszaros

2009

Adrenaline Junkies and Template Zombies: Understanding Patterns of Project Behavior. by Tom Demarco, Peter Hruschka, Tim Lister, Suzanne Robertson, James Robertson, Steve McMenamin

1.

Emergent Design: The Evolutionary Nature of Professional Software Development by Scott L. Bain
2.

Intellectual Property and Open Source: A Practical Guide to Protecting Code. by Van Lindberg

Real World Haskell by Bryan O'Sullivan, John Goerzen, Don Stewart

1.

High Performance MySQL: Optimization, Backups, Replication, and More by Baron Schwartz, Peter Zaitsev, Vadim Tkachenko, Jeremy Zawodny, Arjen Lentz, Derek J. Balling
2.

Programming in Scala by Martin Odersky, Lex Spoon, Bill Venners

2010

Masterminds of Programming: Conversations with the Creators of Major Programming Languages by Federico Biancuzzi, Shane Warden

1.

SDLC 3.0: Beyond a Tacit Understanding of Agile. by Mark Kennaley
2.

Hello World! Computer Programming for Kids and Other Beginners by Carter Sande



I'v read some articles of javascript guru Douglas Crockford. His article is always brief and short, it won't take you much time to finish one article and they are easy to be understood. I enjoy his economical style.

one article is about javascript code convention. those conventions are very common practice. there is one convention which has a great resonance for me.

this convention is :

"When a function is to be invoked immediately, the entire invocation expression should be wrapped in parens so that it is clear that the value being produced is the result of the function and not the function itself."

var collection = (function () {
var keys = [], values = [];

return {
get: function (key) {
var at = keys.indexOf(key);
if (at >= 0) {
return values[at];
}
},
set: function (key, value) {
var at = keys.indexOf(key);
if (at = 0) {
keys.splice(at, 1);
values.splice(at, 1);
}
}
};
}());

see the bracket which embrace the anonymous function

var collection = ( function(){}() );
function has been called immediately , so we hug it with bracket to make the code more clear.

this is a very good practice and need to be follow.





December 29th, 2010strongly recommend wiz

used evernote for more than 2 years, but the first time I saw wiz, I know It's a time to make some change.

there is a lot of advantages of wiz to the evernote.

1. 88m monthly usage of wiz vs 40m of evernote
2. wiz has calendar, todo, desktop note module , evernote doesn't have.
3. wiz can export all notes to a e-book. evernote doesn't have
4. wiz has a powerful html editor, evernote doesn' have
5. wiz support more formats of attachment, evernote only support pdf for free users.
6. wiz support publish note to blog, evernote doesn't have
7. wiz is more open, support third party plugins.

in addition, wiz is from Chinese software, need more care from Chinese.



冰箱里有一个塑料盖,上面用螺丝拧着,我螺丝拧开,费了一番周折,把那个塑料盖子给打开了。发现那个盖子不是塑料的,只是上面不知道刷了一层什么涂料,所以手感很像塑料。粘在手上还有一层白白的粉末。打开这个盖子,立刻就有了拔云见日,水落石出的感觉。

看见了一排冷凝管,上面结着厚厚的霜。现在可以确定制冷良好。那为什么冷气没有循环了? 于是再顺藤摸瓜,在冷凝管上面正中,有一个小风扇,风扇没有转,用手摸了一下,在发热。又看了一看配件图,把风扇从轴上拔掉,把两边的塑料搭扣掰开,把一个小电机给取了出来。

一切在真相大白,就是这个小电机的问题。通电的时候,它会发热,但是不转,所以冷气沉积在下面,不能循环,冰箱无法制冷。终于找到原因了,看来修好有望。

接下来的事情就简单了, 找到配件的型号, 然后跑去local店, 结果被告知店里只卖整机,不买配件,乘兴而来, 败兴而归.

只好去网上买了, 到searsparts网站上去看, 输入item model #, 很快就找到了. 倒是不便宜,60多. 不过和买一台新的比,还是省很多钱.

其实好多东西,像家电,汽车什么的, 出故障都是小故障, 稍微懂一些,自己就能fix好,也会省很多钱. 如果我去sears找人过来看,来一次就要75,只是帮你看, 修起来还要按小时算钱,自己轻松搞定,还是很有成就感. 关键是要多动手,有diy的精神.

努力向handy man的方向继续前进.



after more than one year's hard work. Actaute 11 would be released soon. Now it is in final stage. Today is the last day of final milestone. After 'final', every check in need to get approve after discussion. I will record a demo to show some features of this product. This is a first complete Journey to me - from design, implementation, integration and test. hope it will sell well.



September 4th, 2010js array map function

The map method will call the provided function for each value of the array and it will return an array containing the results of those function calls.

The callback function is called with three arguments: the value, the index, and a pointer to the array being used respectively.

In the following example each element of the array is tested to see if it is numeric, if it is, it's passed into the new array, otherwise a zero is inserted.

for ex,

var isNumeric = function(x) {
// returns true if x is numeric and false if it is not.
var RegExp = /^(-)?(\d*)(\.?)(\d*)$/;
return String(x).match(RegExp);
}
var testElement = function(x) {
if (isNumeric(x)) {
return x;
} else {
return 0;
}
}

var myArray = [1,'two',3,'four',5,'six',7,'eight',9,'ten'];
var newArray= myArray.map(testElement);
document.writeln(newArray); // outputs: 1,0,3,0,5,0,7,0,9,0



又有很久没来了。接着写。

我在冰箱的外壳上找到了冰箱的品牌和型号,brand name is Kenmore, model # is 10659582990.
然后我就在网上开始搜,感谢党,感谢人民, 感谢bing(排名分先后), 我搜到了这个链接:

http://www.searspartsdirect.com/partsdirect/getModel!retrieve.pd?modelNumber=10659582990&pathTaken=partSearch

kenmore是sears专门的品牌,也很有名, 所以比较容易就搜到了,然后开始看上面的图。前面说道我怀疑air flow有问题,所以我第一个就找到了air flow的配件图。 为什么怀疑air flow 有问题,我看了一篇7页长的冰箱故障快速入门,大概清楚了冰箱的制冷,除霜循环, 蒸发装置等等, 所以决不是拍拍脑地就做的判断。

拿到这个配件图,还是不懂啊,先不管,把冰箱拆了再说。拆哪? 怎么拆? 这个问题是根本性的和方向性的问题。我第一直觉是拆冰箱后背的大盖子。 看了半天没见有螺丝,踟蹰良久,还是不敢轻举妄动。都说窥一斑而知全豹, 我看着air flow的配件图,硬是不知道这东西是在哪里。

没辙,只好问高人。我打电话问罗叔,然后跟他描述了一下冰箱的症状,我的分析判断等等。然后问他我是不是该拆后面。前面的分析他很赞同,但是却断然阻止我拆冰箱后背。后面是制冷的冷凝管, 如果要拆后面的,估计也一般很难在家里修好了。这让我想起一个故事,说一个大牛去厂里帮人修机器,在机器上画了根线,说故障就在这里,然后charge 了一万刀。 其他人很不忿, 认为不值。他说,画根线1刀,知道在哪儿画, 9999刀。 罗叔这番话给我省了800刀估计,买台新的估计就是这个价。 所以其实这个冰箱不是我修好,是罗叔修好的。

他告诉我说把冰箱门打开,看看有没有什么玄机。因为我的冰箱是side by side, 也就是左右两扇门,这种都比较大,罗叔对这种不太熟。 他让我找有没有看到一排铝管子什么的。然后我左看右看,看见在冰箱的下部有一块塑料板,螺丝拧着,好像可以下下来。

继续未完待续......




家里的冰箱有点问题。下面制冷良好,但是上面却是室温。制冷良好说明基本的部件, 比如压缩机和制冷机没坏,但是上面温度不够低,我猜想是air flow的问题。
所以自己试图修理一下。

我在网上download了kenmore的manual和它的parts diagram. 看了一下,很确定是air flow 有问题,所以导致下方的冷气无法循环到上方。

未完待续.....



谈不上好, 和旁边的peer比, 也谈不上坏。问我有什么意见, 我也没什么意见。问我感觉load大不大, 我说不大。问我感觉是不是有push, 我说还好。像我这种small potato好像没什么意见可发表的。混饭吃,等绿卡呗。

不过有一句中肯, 提高水平是王道。这是唯一我能控制的。所以有时多干活, 其实也是为自己。



July 28th, 2010where to find this book

web content mining with java

sounds like a good book.



July 28th, 2010a good website

http://www.giveawayoftheday.com/

you can download some business software for free. mark it.



July 27th, 2010我的第一篇 blog

我的小家。好久没写了。以后会常来看看看。




© 2008 - 2012 道阻且长 | iKon Wordpress Theme | Powered by Wordpress 3.3.2