RSS feed [root] /design /weblog



title search:


Thu Jan 25 22:38:50 GMT 2024


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

Sat May 14 18:52:07 GMT 2011 From /weblog/design/pattern


Suggest use to take a fresh look of original "pattern language" - , in his opinions, it is more about separate design to difference groups than create reusable design.

Some more...[..]007/5/17/design-patterns-are-code-smells

Some say pattern should be language feature ...

Closely related, there are no golden rules and silver bullet, Design Pattern can help us in some design problem and provide some design suggestion. However, we need to know what it good for and bad for[..]est-practice-vs-pattern-vs-standard.html[..]ndard-approach-does-not-necessarily.html

Use pattern in hello world, sample of over engineering:

(google search) (amazon search)

Sat May 14 18:40:40 GMT 2011 From /weblog/design


Arguement of overuse interface, I trend to support -[..]ramming-to-interfaces-strikes-again.html

A very long discussion related, Test-friendly, but not caller-friendly? -[..]ring-your-development--t2039307i120.html

Comparison of interface vs. abstract class -[..]ry/api_design_interfaces_versus_abstract

Some issue of marker interface, may be annotation can help. However, I don't think those so call issue are really problem, those just poor usage of marker interface -

(google search) (amazon search)

Sat May 14 18:19:55 GMT 2011 From /weblog/design


The 37signals manifesto was our original site from 1999-2001. It's a collection of 37 nuggets of online philosophy and design wisdom. It's a great introduction to the 37signals' school of thought and a fun, quick read to boot. -

(google search) (amazon search)

Sat May 14 18:11:54 GMT 2011 From /weblog/design


Deadlock detector sample -

Deadlock in J2EE, explaining deadlock in various place, e.g. DB, VM, code,... -

A blog comment about database deadlock very detail -[..]2007/04/java-wish-list-2-retry-code.html

Technique to prevent deadlock: Automatic Lock Releases, Timeout, automatic detection -

(google search) (amazon search)

Sat Apr 23 17:07:07 GMT 2011 From /weblog/design


Introduction to Saga -[..]sistence-and-event-driven-architectures/

(google search) (amazon search)

Thu Feb 10 16:48:54 GMT 2011 From /weblog/design

when api design rule conflict

2 best practices of API design confilct each other, and how to find out the solution -

What exactly simple mean?[..]s-that-pass-for-simple-i-cant-understand . In my opinions, a more concrete interpretation of simple is first define what is most important to you, then find the quickest way to get there.

Iceberg Classes, if encapsulation is good, how about having more private method? Or actually the logic should be split? -

(google search) (amazon search)

Mon Feb 07 16:38:32 GMT 2011 From /weblog/design/distribute


Implement ping-pong play between two nodes on the cloud using GridGain Distributed Actors -[..]11/01/26/distributed-actors-in-gridgain/

(google search) (amazon search)

Sat Jan 15 17:51:29 GMT 2011 From /weblog/design


Discussion on TDD algorithm -

(google search) (amazon search)

Mon Dec 13 16:57:34 GMT 2010 From /weblog/design


Issues of annotation dependence test framework, usually new language feature come out to solve some problem people get excited. However people found that the problem it bring are not less than the problem it solve, it take time to proof the value -[..]tmotion?entry=annotations_suck_a_lot_and

Compare OO feature of difference language -[..]ral/comparingObjectOrientedFeatures.html

Comparing C# and Java -

Discussion about extending standard API -

Few good suggestion when thinking of design a language, Consider using ML, Don't be afraid of being the same -[..]programming-language-design-is-hard.html

Design Principles Behind Smalltalk, see how idea of inheriance, polymorphism originated -[..]/design_principles_behind_smalltalk.html

(google search) (amazon search)

Tue Feb 02 04:03:55 GMT 2010 From /weblog/design


twelve things you should know about indexing -[..]elve-things-you-should-know/indexing.php

(google search) (amazon search)

Wed Jan 20 17:46:26 GMT 2010 From /weblog/design/IoC

Inversion of Control

When these containers talk about how they are so useful because they implement "Inversion of Control" I end up very puzzled. Inversion of control is a common characteristic of frameworks, so saying that these lightweight containers are special because they use inversion of control is like saying my car is special because it has wheels.[..]ticles/injection.html#InversionOfControl

This guy think IoC is going to use is more and more place as GC. However, I will think quit a lot of time IoC is use incorrectly, somebody even try to use it everywhere and replacing constructor... -[..]endency-injection-mirror-of-garbage.html

IMHO jetty is the first widely used program about IoC idea, even before spring -

Explain when IoC is overkill -[..]010/01/17/dependency-injection-inversion

(google search) (amazon search)

Thu Jan 14 11:13:15 GMT 2010 From /weblog/design


Article with example to show how aspect can help in most common case -[..]se-cases-of-aspect-oriented-programming/

(google search) (amazon search)

Tue Jan 05 17:47:53 GMT 2010 From /weblog/design


A Theory of Compatible Versions, and introduction of how and why difference versions are comptible or not -

XStream offers some support for refactorings (aliases can help). But very soon you will run into big troubles and will have to make some decisions. Either avoid refactorings (just a little tweak here and there, will weaken your architecture over time) or start implementing workarounds – e.g. custom converters (much work, bad code). -[..]ts-wrong-with-xstream-and-similar-tools/

(google search) (amazon search)

Wed Dec 30 16:46:40 GMT 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)

Sat Dec 12 02:43:54 GMT 2009 From /weblog/design


Batch login Authentication -[..]us-high-performance-login-for-web-farms/

(google search) (amazon search)

Wed Dec 09 16:01:54 GMT 2009 From /weblog/design/interview

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

(google search) (amazon search)

Fri Nov 27 07:56:17 GMT 2009 From /weblog/design/distribute


A short example to show how eventual-consistency work -[..]/11/eventual-consistency-by-example.html

(google search) (amazon search)

Thu Nov 12 01:57:25 GMT 2009 From /weblog/design/pattern


(google search) (amazon search)

Fri Sep 25 11:04:28 GMT 2009 From /weblog/design

Discuss issue of mutability from another aspect -

(google search) (amazon search)

Thu Sep 24 04:35:05 GMT 2009 From /weblog/design


Have read this article long time before: However, the more I work on programming the more I find that reasonable default (may be with logging) work better in some cases, but really need to beware about the cost of debugging if there is problem....

Another discussion about failfast vs. failsafe -[..]009/09/iterators-fail-fast-vs-fail-safe/

(google search) (amazon search)

Fri Sep 18 17:37:37 GMT 2009 From /weblog/design


sunday-school truth: if you don't do well in small think, you will do worse at big thing:

Wait for best solution -

(google search) (amazon search)

Sat Sep 12 16:05:27 GMT 2009 From /weblog/design


I think there's perfectly reasonable scenarios for both soft and hard deletes, with and without audit trails.

1. Soft delete:
A user signs off of your service, but you need to keep (anonymized) stats data consistent for your customers - here you cannot remove the entire user, you just blank his personal data (name, email, phone, ...) and keep the anonymized statistical data (country, birth year, profession).

2. Soft (or super-soft) delete with audit trail:
Any financial transaction data, even if entered by error, may only be corrected by adding a correction entry, not by deleting the erroneous entry, or the IRS will be all over you. So either you flag it as deleted (soft delete) or you correct it by adding another entry ("super-soft delete").

3. Hard delete with audit trail:
A user unsubscribes from your newsletter. No need to keep the info "he once was subscribed to it" in the live database, but need to keep the info somewhere accessible in case he sues you for spamming and you can prove "but back in August when you got the mail, you were still subscribed".

4. Hard delete with no audit trail:
Personal data as in #1 if your local data protection laws require. (This means *no* more storing, *anywhere*, technically speaking not even in last month's backup, but that's another issue altogether.)

And Udi think is real life, people usually never really delete something -

(google search) (amazon search)

Wed Sep 02 16:28:22 GMT 2009 From /weblog/design

composition over inheritance

Good example of composition over inheritance -

(google search) (amazon search)