More advanced stuff
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?
More in depth articles and less trivial ones (with information that can obtained directly from the web site of the product). More real scenarios and less hello world examples.
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.
Nope.. well I'm thinking of writing an article for you :)
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:
- What the article is about
- Why it matters
- What specific items will be covered that deliver on 1 and 2.
I've found this is a good exercise to help writers focus on the value they provide to the reader.
like to see some more articles on leading edge java stuff and less basics
OK. We'll try to keep working on that.
Build a lab where you can really test the stuff you write about, don't write about something you haven't tested.
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.
I still visit your site daily, as I typically set it as my homepage. However, your articles have strayed towards specific OS projects, tools, and frameworks. This has greatly reduced the number of articles that am interested in or would use professionally, and therefore has reduced the amount of time I spend browsing the site. If you would return to topics that were more java centric and discussed features of J2SE and J2EE rather than the other projects, I am sure I would be reading much more. Thanks!
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.
we want more tools! frameworks are great, but there is still too much coding, we need to take a leaf out of the RoR book
Potential authors: topic alert!
I'd love to see an article/tutorial on using XML web services with J2ME devices. See (I think) JSR #120.
And there's another topic for an article proposal!
Love the site, would like to see more than a weekly update of content, doesn't have to be full articles.
Thanks. We'll be trying some different things. Let us know what you think.
I enjoy reading articles written by developers that follow this general format: 1. this is the problem I ran into while developing xyz; 2. this is an analysis of the problem and what caused it; 3. these are the various solutions; 4. This is why I picked solution x.
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.
It's important to discuss architectural patterns - which are oftenly forgotten.
Sounds like a good topic, thanks.
You seem to be losing focus. Possibly split the website up a bit more. The front page is far too eclectic and the zones are too specific.
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?