www.carfield.com.hk: misc

1 2 3

Tue Jan 31 00:23:00 HKT 2012

misc

(google search) (amazon search)
second

Tue Jan 31 00:22:59 HKT 2012 From /weblog/misc

number

A nice overview (with detailed reference) about how computer operate on floating point number - http://www.regdeveloper.co.uk[..]2006/08/12/floating_point_approximation/

Why we should never use float / double for money - http://binkley.blogspot.com/2012/01/major-code-irritants.html http://www.odi.ch/prog/design/newbies.php#43

(google search) (amazon search)

Sat Oct 22 23:35:20 HKT 2011 From /weblog/misc

support

Some tips help you to build effective support - http://www.goodproductmanager.com[..]7/03/29/streamline-your-product-support/

Tips for arranging support tasks for agile tasks, look like a separate supporting team is still required - http://www.elilopian.com[..]7/12/12/handling-support-in-agile-teams/

Downtime handling - http://www.kalzumeus.com[..]time-today-heres-what-im-doing-about-it/

DevOps movement - http://www.enterprisecioforum.com[..]lad-dressing-sometimes-you-need-shake-it

(google search) (amazon search)

Thu Oct 20 23:24:23 HKT 2011 From /weblog/misc

performance-engineer

http://programmers.stackexchange.com[..]think-a-performance-engineer-should-have

(google search) (amazon search)

Sun Oct 16 23:42:53 HKT 2011 From /weblog/misc

theory or practice

Should we work more or should we think more? http://www.shoesobjects.com/blog/2005/03/31/1112293377709.html

Data beats Math, result beats theory? - http://jeffjonas.typepad.com[..]/jeff_jonas/2011/04/data-beats-math.html

(google search) (amazon search)

Mon Aug 15 00:58:02 HKT 2011 From /weblog/misc

patent

http://martinfowler.com/bliki/SoftwarePatent.html

Patent of using internet to support learning - http://www.blackboard.com/company/patentFAQ.htm

Patent issue of microsoft and bluej - http://cld.blog-city.com/microsoft_kills_off_its_bluej_patent.htm

(google search) (amazon search)

Sat Jun 04 01:00:40 HKT 2011 From /weblog/misc

think

Collabrative wise coming from independence thinking - http://cn.wsj.com/big5/20110531/col075430.asp?source=rss http://cn.wsj.com/big5/20110531/col075430_ENversion.shtml

(google search) (amazon search)

Sat Jun 04 00:55:23 HKT 2011 From /weblog/misc

http://blog.objectmentor.com[..]articles/2008/03/20/musing-over-mutation

Will experience hurt innovation? - http://manincentral.blogspot.com/2008/01/out.html

You Are Solving The Wrong Problem, what is the right problem? it is how to retry very quick - http://www.azarask.in/blog/post/the-wrong-problem/#

Most real innovation is done by crazy people doing crazy things. The keys are:

* Learn all you can before you go adventuring.
* Don't be afraid to make mistakes.
* Only make new mistakes.
* Keep your eyes open.
* Don't just look straight ahead: develop your peripheral vision.
* It's the things that go in unexpected directions are the most important.

One of the classic stories of serendipity and invention is the color mauve.

http://weblogs.java.net/jag/page7.html#63

(google search) (amazon search)

Sat May 28 01:10:14 HKT 2011 From /weblog/misc

mistakes

common mistake at software house - http://jroller.com/page/rolsen?entry=the_same_mistakes_over_and

1.- The all code is crap, except mine, attitude.
How to fix it: Don’t criticise others people code

2.- The “I fix that in a second” catastrophe.
How to fix it: Don’t trust yourself when carrying delicate activities.

3.- The “That will only take a second” misconception.
How to fix it: remember that is very likely that you will find so many things which you didn’t foresee when you start developing that is worth multiplying the estimate to cover for those

4.- The ego spiral.
How to fix it: Leave your ego at home. Big egos are one of the biggest non technical issues for any programmer. Keep in mind some basic considerations when making decisions.

5.- “It wasn’t me!”
How to fix it: No need to cry, or to perform seppuku, (aka harakiri), when we make a mistake.

6.- The demotivated genius.
How to fix it: Discipline. Unfortunately, there isn’t any other remedy I can think of.

7.- The premature programmer.
How to fix it: Probably the two easiest ways to help a programmer understand if some code is done are peer reviews and demos.

http://www.makinggoodsoftware.com[..]2011/05/23/top-7-programmers-bad-habits/

(google search) (amazon search)

Sun May 15 02:34:24 HKT 2011 From /weblog/misc

Set up a customer advisory program

Conduct regular surveys

Encourage responses to your email newsletters instead of having the reply-to address go to an unmonitored or nonworking email address

Publicize email addresses and phone numbers– customer service, technical support, and even your own personal email address

Better yet, make those phone numbers toll free

Hand out business cards at trade shows

Start a blog and allow comments

Add a feedback link on every page on your web site

Monitor and post to relevant discussion lists and message boards

Encourage your sales staff to provide your contact information directly to customers who want to provide more input

Contact people who are talking about your product already — in blogs and on mailing lists — and follow up to get more feedback

Every time you talk to a customer, ask them to refer you to someone else who can give you additional feedback, and encourage them to pass your contact information along

- http://www.goodproductmanager.com[..]007/03/15/make-it-easy-to-give-feedback/

Other related blog - http://headrush.typepad.com[..]onate_users/2007/03/user_community_.html http://www.taylor.se/blog/2007/06/13/my-rules-of-feedback/

Some will think non-feedback, uncall feedback are more important - http://www.infoq.com/news/2011/04/non-feedback-uncalled-feedback

(google search) (amazon search)

Wed Mar 02 01:04:12 HKT 2011 From /weblog/misc

Short tips of regex - http://immike.net[..]know-to-become-a-regular-expression-pro/

Let regex more readable - http://martinfowler.com/bliki/ComposedRegex.html

Useful Regular regression

Match username - /^[a-zA-Z0-9_]{3,16}$/
Matching an XHTML/XML tag - {]*>(.*?)}
Matching an XHTML/XML tag with a certain attribute value (e.g. class or tag) - {]*attribute\\s*=\\s*(["'])value\\\\1[^>]*>(.*?)}
Matching a URL - (a very long one... refer to article...)

http://immike.net[..]ssions-every-web-programmer-should-know/

(google search) (amazon search)

Mon Dec 20 02:12:19 HKT 2010 From /weblog/misc

tools

http://en.wikipedia.org[..]i/List_of_tools_for_static_code_analysis

(google search) (amazon search)

Wed Nov 24 23:44:19 HKT 2010 From /weblog/misc

Random unique integer number

Another notice about shuffling collection with random order - http://www.codinghorror.com/blog/archives/001008.html with detailed analysis- http://www.codinghorror.com/blog/archives/001015.html

C simple implementation of random - http://groups.google.com[..]wse_thread/thread/407497c8cae78303?hl=en

(google search) (amazon search)

Fri Apr 30 01:40:27 HKT 2010 From /weblog/misc

email

A detailed overview of POP, IMAP and GMAIL - http://www.macdevcenter.com/lpt/a/6702

The 12 steps to cure e-mail addiction

Admit that e-mail is managing you. Let go of your need to check e-mail every ten minutes.
Commit to keeping your inbox empty.
Create files where you can put inbox material that needs to be acted on.
Make broad headings for your filing system so that you have to spend less time looking for filed material.
Deal immediately with any e-mail that can be handled in two minutes or less but create a file for mails that will take longer.
Set a target date to empty your in box. Don't spend more than an hour at a time doing it.
Turn off automatic send/receive.
Establish regular times to review your e-mail.
Involve others in conquering your addiction.
Reduce the amount of e-mail you receive.
Save time by using only one subject per e-mail; delete extra comments from forwarded e-mail, and make the subject line detailed.
Celebrate taking a new approach to e-mail.