Skip to Content

Back …

Wow, these were some interesting I would even say emotional two weeks since I am back, not counting the short trip to Walldorf in between.

Discussion in the Weblog comments as well as in the Where is the original content in the weblogs and in the email backchannel were flying high about quality and quantity of Weblog posts. Many a Weblogs have been rewritten, even recalled. Probably even more were not written at all and for some posts that was a good thing.

Talks in the backchannel even lead to brand new rules that one company has put into place for their employees. They allowed me to share them with everyone in SDN Land:

Sample rules laid down internally:

Rule #1: I have stated this before & I’ll state this again – You need to be DOUBLY sure in terms of  formatting, what to say, what to publish. Here are some more tips on how to write Weblogs: Weblog formatting Tips and Tricks , The 1-2-3 Steps To Producing a Weblog .

Rule #2: If you do not have anything new to say – just shut up !!

Rule #3: I know you all have a lot of ideas, but it has to be presented well. Look at the blogs by Eddy De Clercq or Craig Cmehil or Mark Finnern. Use those as a yardstick to write yours. No lousy English here – just pure original content. (See headlines on SDN today)
[Insert: Exchange Mark Finnern with Thomas Jung in that listing, you can only learn bad spelling from my posts :-)]

Rule #4: Blogging is a more powerful tool than you can imagine. Some of you may have practically NO IDEA as to how many people you are reaching out to. Figure this one out yourself.

Rule #5: Expect support from SDN community when someone steps out of the line. You would have seen since yesterday, SDN is policing the blogs more closely than ever. Get your blogs checked, previewed by someone senior before you publish it & make an *** of yourself on SDN.

Quite some frank words here. Actually the SDN Community is policing the blog content more closely because we had this great thing where real nuggets of information or even wisdom were common on an almost daily bases. The rush for points and position in top contributor or top company lists watered this down and brought quantity which drowned the quality posts. My feeling is that in the last two days it got better again. The quantity of posts is down and the quality of these is good, at least in my opinion. Back to quality. My hope is that we can keep it up.

The model of automatic 40 points and then adjustment up or even down in a timely fashion will turn out to be beneficial I am convinced.

Igor Barbaric commented that he wanted to write a post to thank the people that have voted for him in the TechEd call for papers contest. Now he can’t because he doesn’t want to get 40 points for a thank you post. How about adding the thank you at the end of your next Weblog post with good content? That way it would be icing on the cake of good content and SDNers will appreciate it even more.

German proverb: First it takes longer, second then one thinks. I finally caught up with giving points. If I missed one or you strongly feel that I was too stingy let me know and I look into it, after all there were a lot of things going on lately.

What influences the giving of points will probably remain a bit of a mystery. One element is time. If I have to contact you to take out word formatting or change add a target=”_blank” to your outside links I will deduct some points because you caused extra effort that I could have spend answering forum questions.

Thanks Craig for his excellent: SDN Weblogs: Making it easier… post read it and may be it helps you in writing your next post.

The last two weeks have shown that we the SDN community really value good, well written content. The opinion of what good content is differ. Some would like to read only pure solutions for tough SAP development problems. If you are one of these, I recommend to use an RSS reader and only subscribe to the topics in your area of interest, or bookmark these topics. There is also DevToday as well as myWeblogs where you can tweak which content SDN is serving you.

Personally I like the mixture of good SAP content with some personal background or story sprinkled in. I loved the SAP xApps is just like a Fried Chicken. Yes, there could have been more meat, but man how much I would love to be at the SDN meets Labs in Bangalore on July 4! next week and may be experience such a food festival myself.

Eddy de Clercq is a master of great accessible SAP content with some of his quirky personality and background stories added into the mix.

There is also the rumor that only SAP applicable content is allowed on SDN. I would like us to also look beyond the rim of our SAP saucer. If there are developments out there that an SAP developer should know about, post and a link and let’s have a discussion about it right here.

All for now. Happy 4th of July. Looking forward to your next posts.

You must be Logged on to comment or reply to a post.
  • Hullo Mark,

    I(We) wish you were here for this event. We do really miss you. Any chance of you making it for the TechEd '05 in Bangalore ?

    Anand Mandalika.

  • Mark,
    I've just reviewed quickly CSS file automatically attached to weblog posts and would like to express my opinion:
    1. It has heavy relation on classes & ids, almost no style rules applied to default elements (h2..6, code, var, em, etc...). Believe me, this is a bad approach: are you sure that most authors are aware of these classes? Why not to define rules applied to (X)HTML elements directly? This would provide consistency among all weblogs almost automatically.
    2. Some class names express styling rather then semantic (compare for example ".sapOrange" and ".sdnRed" to ".sdnAuthor" and ".sdnHdr2" [later ones are correct])
    3. You are underuse "cascading" in cascading style sheets: most declarations reproduce settings that could be inherited
    4. Either I missunderstand something, or you are completely missusing css ids: does "#methods" identifier should be used once per document? If not (and, according to logic, definitely not) then it should be classes. If your designers try to give higher priority (id definition has higher priority then class) then it is not the best approach.