What goes on in that one line though? Just because something can be reduced to one line doesn't mean that we don't want to know why you are using that one line? What decisions you took in deciding that one line fits the problem domain? What are the edge cases or compromises that we have to consider?
That's what we want to know, and you can't cover that type of thing in a few lines in an article. It's not just the how, it's the what and why as well.
It doesn't, but sometimes a lack of quantity means there is very little quality. Don't forget that not everyone who reads the article is at the same knowledge level. Some people will be absolute beginners and will need all those extra words just to understand what you are trying to teach them. Those who have a better background will be able to skim read to the parts that they need.
Just wondered if there are any rules for when it's ok to change the name of an article?
My one and only article have developed out of scope of the original name, it isn't A propertymapping Extension for DataReaders[^] anymore, it's "An InstanceCreating Extension for DataReaders" nowadays