Their tagline is "A better way to learn programming"... so yeah, 101 stuff. And unfortunately, the content looks pretty poor. Example, the start of the "Design Pattern" article:
“Pattern” word suggests a series of events occurring in a definite order. Many a times, you get an easy way to tackle a recurring problem (which has been faced earlier, by people frequently).
Hmm. It actually starts listing patterns about 4 pages in... but doesn't actually *explain* them. Short example (this is the complete explanation for a "single-threaded execution" pattern):
The Single Threaded Execution pattern is the pattern most frequently used to coordinate access by multiple threads to a shared object. The Immutable object pattern can be used to avoid the need for the Single Threaded Execution pattern or any other kind of access coordination.
Got it?
I've gotten various Java magazines for free over the years. In the end, it's basically a waste of paper. The articles have *never* been very good (though generally better than these, I guess), and most of what you need to learn translates very poorly to a paper medium. You can't even copy out sample code into your IDE... unless you read it online, in which case why get the paper copy?
Comments
jcblitz replied ago:
Seems like all "101" stuff.
Affar replied ago:
Totally agree.
jtheory replied ago:
Their tagline is "A better way to learn programming"... so yeah, 101 stuff. And unfortunately, the content looks pretty poor. Example, the start of the "Design Pattern" article:
“Pattern” word suggests a series of events occurring in a definite order. Many a times, you get an easy way to tackle a recurring problem (which has been faced earlier, by people frequently).
Hmm. It actually starts listing patterns about 4 pages in... but doesn't actually *explain* them. Short example (this is the complete explanation for a "single-threaded execution" pattern):
The Single Threaded Execution pattern is the pattern most frequently used to coordinate access by multiple threads to a shared object. The Immutable object pattern can be used to avoid the need for the Single Threaded Execution pattern or any other kind of access coordination.
Got it?
I've gotten various Java magazines for free over the years. In the end, it's basically a waste of paper. The articles have *never* been very good (though generally better than these, I guess), and most of what you need to learn translates very poorly to a paper medium. You can't even copy out sample code into your IDE... unless you read it online, in which case why get the paper copy?
Voters For This Link (14)
Voters Against This Link (4)