| Sign In/My Account | View Cart |
ONJava 2005 Reader Survey Results, Part 2
Pages: 1, 2, 3, 4, 5, 6
In what sense of "advanced"? More in-depth on key things that lots of people use, or topics that are intrinsically advanced, like bytecode manipulation?
I think ONJava articles tend do to be "in-depth," with the limitation that we like to keep things around 2,000 words--longer articles just don't get read. We do like, "hello world," as a means of introducing a new technology, but of course, it's essential to move past that once the fundamentals are understood.
Send us a proposal and we'll talk. I generally ask writers for one to two paragraphs, five to 10 sentences, or five to 10 bullet points that establish:
I've found this is a good exercise to help writers focus on the value they provide to the reader.
OK. We'll try to keep working on that.
That's a tall order. We are somewhat limited in our ability to test code because we can't realistically maintain and run all the various app servers, databases, frameworks, etc., so we do expect a certain level of competence from our writers. If you see something wrong, please let us know in the article comments and we'll see what we can do.
We do try to combine J2SE/EE articles, major third-party frameworks (especially open source), and "meta" articles (design, patterns, process, etc.). Thanks for the feedback.
Potential authors: topic alert!
And there's another topic for an article proposal!
Thanks. We'll be trying some different things. Let us know what you think.
Good format. A key concern that I'll point out as an editor: how many people will run into the same problem? If it's something that effects everyone, this rocks. If the problem is confined to a small niche audience, we probably won't pursue this article.
Sounds like a good topic, thanks.
Are you referring to the O'Reilly Network home page or ONJava's? Is there another way to split it up other than by topic (e.g., by how recent items are?) that you think would work better?