i completely agree, and i'm really glad i'm not the only one with this impression... i've got the asp.net weblogs rss feed in my outlook and i'm pondering about removing it.

no disrespect to the newcomers but as the ancient saying goes, quantity != quality

i mean, i've seen a post come by today that were about the differences between abstract classes and interfaces, and another one about the different sql joins. no offense to the authors, but these are the ASP.NET weblogs after all...

i don't question the new bloggers' good intentions! But please post only quality content.

(btw, i saw some non-english posts as well, what's up with that?)

Judging code isn't always good/bad. Sometimes good/bad code is just a matter of preference. I might consider code bad because it's not how i would code something, even though it might perform fine.

If you see code you consider bad, send them a suggestion through a comment. I would rather see people post code saying "this is what i wrote, but somethings wrong... not sure what", and open it up to the community for help because a) that's the point of a community, and b) it's challenging but benneficial to me to try to figure out a solution to their problem. And that i think makes me a better developer.

As for poor code, hey, no one is perfect. We are all continually learning new things, new approaches, and learning that the way that we have done something before might not be the best way.

And for everyone that peruses weblogs.asp.net, don't consider the bloggers here gods of code. the blogs here have been superb, and i think will continue to be so. With that said, from time to time i have had issues with the way people wrote things before, and most likely will continue to, but if you don't suggest something different, things won't change, and heck, you might figure out that the "bad" way they are doing something might actually be a great way of doing something, if you were to just make x number of small modifications.

just my 2 cents, for what it's worth.

also, welcome to the community ;)

+1

Not for poor code ... but for poor posts. and my feed reader shows me more posts than before (weel it's quite normal) and the attention I give to posts is reduced in order to fullfill the feed. Well perhaps it was better when the Bloggers were few and "certified" :)

See Ya !

Gianluca

I completely agree. asp.net blogs was a collection of top notch stuff, now it become another "dzone" type blogroll with too much noise.

Agreed, whilst I applaud Joe Stagner for keeping the momentum going on this site, a total free-for-all is rapidly reducing the usefulness of this site.  I long for a return to the days when it was actually quite difficult to get on here; and the posts were generally of a far better quality as a result. Here's an idea, what about using some sort of post rating system to keep up quality?

I agree, the quality of posts has definitely declined. I also noticed that a lot of the writing has as well. Not that I am some great writer, I am not. But i've grown used to reading articles and posts that are well written, thought out, well structured, and very informative.

Why not separate the original/sponsored blogs and the community blogs? Separate RSS feeds or something.

Use the community blogger area as a way to screen for sponsored blogs?

Many of the articles references in the above comments have come from one site: weblogs.asp.net/jalpeshpvadgama

It appears the site owner is posting random code snipplets and links that can be found in a simple Google search.

I am definitely not a big fan of opening up the blogs.  

I totally agree.  I actually unsubscribed from the ASP.NET feed a few months ago because out of the hundred or so updates a day a lot of them were the same thing, i.e. "Silveright 1.0 release", "Silverligh is here" etc, majority of which simply contained  alink to download and information that had be told a thousand times before.

That's the thing that annoy's me the most, as for the code I rarely look at it unless its portraying something revolutionary which I've never really came across - I prefer to create my own solutions and test appropriatley for peace of mind.

I think Scott's idea should be employed - the ASP.NET feed should only contain posts of a certain calibre.

Its always a problem for a community when the gates are thrown open to everyone. I was surprised to it happen.

Without a barrier to define what the community is, a community usually forgets what it it.

The Hello World posts are currently annoying because there are so many of them, not because of the content.

I have noticed that there have been a lot of low quality posts since the gates came down. The post are low quality for a number of different reasons.  Some of them are just too basic, some have terrible code examples, some have horrid grammar. Dome people have decided to post storms of mediocrity; we don't need another short description of what an abstract class is.

I don't have  a problem with bad grammar or spelling, but if you are posting in order to make something clear, then you should make some effort to have readable grammar.

As a long term poster of dross on here I'd be lying if I said I wasn't concerned about the addition of 150 blogs to just anyone who asked.

It's certainly changed the main feed.

The quality has definitely taken a nose dive lately (and fills my RSS reader up with noise).  To everyone's credit though, it can take some time to acclimate to writing a blog and the quality will surely improve.  Posting constructive comments on those blogs could make a big difference.

As with any group, I think the key is to keep a slow trickle of fresh blood coming in over time, instead of large infusions.  

I have no problem with the blogs being "opened up". If the new posters can help bring some new ideas, throw up some alternatives to existing problems, or generally provide me with knowledge on a subject I am unfamilier with, then great.

If however, this doesn't happen, and from a few post's I've seen, this would certainly suggest this may occur, then I think the individual bloggers would/should be highlighted to Joe.

This site should be an invaluable resource to all ASP.NET developers, and if new bloggers threaten this with inadequate or poorly written articles/posts, then this will quickly detract the value of this site.

I'd rather read a first post of someone introducing themselves than someone pissing on the community they just chose to join.

I think you could have provide a more tactful entry.  After all, it's not like this post is providing anything more useful than a post with bad code.

That's just my opinion...

I'm afraid I'm going to beg to differ. The ASP.NET Weblogs feed is a long way from being overloaded even after the recent influx and was pretty much dead on its feet before the new influx. The new influx has given the feed a new lease of life.

And ASP.NET Weblogs is a LONG way away from the appallingly low "signal to noise" ratio of the MSDN Weblogs.

If you see bad code, comment on it so that the poster (and others reading the post) will learn. Better still give us an example of that good code you've talked about in your first post so the rest of us can get an idea of exactly what you mean,

Preferred it without opening them up - geekswithblogs.net or some other site would have been a better place for the new folks blogging.

I thougth weblogs.asp.net would consist  of very highly regarded developers who got an invite to blog here - unfortunately not so we'll just have to see how it goes but I think the great content will now be diluted.

I think Scott has hit on something...I like the idea of a scoring system....1 to 5 and you have to get a score of at least 3 with 10 votes before your post shows on the blog roll.  The numbers could be tweaked of course, but that would certainly cut down on the 'noise'.

Or the ability to supress certain authors from your own subscription.

I completely agree, just after reading this I checked a piece of code that was using hungarian notation (and not even right!), but is not just that, the main feed is being reduced to recycled pre-release tips from 2005!!

Hope it gets better since I like(d) this place.

I agree. THe floodgates have opened. I don't mind people having a blog here, but please... some guys are posting links to articles from the stone age, small posts with tips that are at page 1 of the manual etc...

People who are new: don't rehash links to articles which are stone old, and don't post lists of tips which are wrong. Thanks.

When I read Joe's announcement on opening registration on this site, I was in doubt "should I move or not" and I decided not to move on asp.net weblogs. Back in 2004 and 2005 it was almost impossible to get a blog on this site,and then was so temptating :) Now, door is completely open and it was not so temptating... On the other hand, in my posting cycle of 1-2 posts per month I cannot guarantee it is worth moving my blog. I aggree that there is now much more worthless content than before.

First of all: welcome. Now, as you all might know, this blog site, http://weblogs.asp.net , has a grouped

Drinking from the, erm, garden hose?

First of all: welcome. Now, as you all might know, this blog site, http://weblogs.asp.net , has a grouped