A note on the blog format
Based on the e-mails, people seem to like the idea of me posting updates on the same post as the lineups.
Somebody suggested I post my most recent updates at the top of the post instead of at the bottom. That way when you refresh, you won’t have to scroll down to see the latest info, opinion or pack of nonsense that I wrote.
Does that make sense? Seems to.
This is your blog as much as mine, so keep the ideas and feedback coming.
Thanks again.





Great job Pete. Most recent at the top makes sense. That Waldman-Russo story was classic. Any update?
It’s fine to post comments within the same post as the line-ups, but if you do it that way it definetely pays to put the latest comments at the top rather than the bottom. Saves the scrolling…
No No No! I read the blog via RSS so updating the lineup post does nothing for me. Why not make a new post and put a link on the lineup post? RSS is a huge part of blogging and you will be losing that if you just update the original post.
i like the new format during the game, but a new post after the game seems good to make a break with the game action.
it seems more natural to have your updates added at the bottom because that’s how most of us read (top to bottom).
but why not try it both ways. see what works best.
Great Job with the blog Pete!!! I like the new format a lot. I agree with Randy that it would be even better if you could have your input separated from, but closest to the most recent comments from the peanut gallery.
Now, if you could just pitch long relief . . .
Pete,
I agree with the new format, plus the most recent suggestion.
I do apologize for not writing much of late: I’ve been so ticked off with the Yanks and how they’ve played that it’s just too much to write (here or on my blog).
I like the new format. Personally I like the top to bottom / oldest to newest (like today’s) better just because if I do miss a game it’s nice to read in order (or go back and reread).
Great job!!
Either way, new updates on the top or bottom is ok.
Pete when do you think we’ll find out if Clippard or DeSalvo gets the starts on the 25th and probably the 30th? I’m anticipating Clemens for the 29th but I guess Torre will have to keep both on the team until Clemens gets here.
I like that idea.
i think posting most recent on top is the best way to do it
Good idea post at the top
I mentioned this via email but if you could work with your tech folks to have the software push your updates out via the RSS feed that would really make the folks who read that way a lot happier. The way it is right now, we only see the original post.
the media gossip is hilarious i remember listening to mike and the mad dog when they were joking suzan waldman about the clemens call and its hilarious picturing russo getting chewed out by waldman
Peter –
I just got back home from a night out with my wife. We left right after the game ended – just as well, I can’t take the post-mortems anymore.
The way they came back to make a game of it, even though they didn’t win, made quite a statement to me. They didn’t quit, despite many of the posts here in the past that suggested that they didn’t care. Maybe I’m too naive or innocent, but I believe in them trying, in contrast to my feelings about the Knicks, for instance. It gives me renewed hope about tomorrow.
I feel so bad for Rasner. He seems like a decent guy, finally getting a chance, and this happens.
Finally, your work here has helped me get through the slump. I’ve been a Yankee fan since the 1964 World Series (great timing on my part, no?). Your blog has taken my interest and understanding of the team to a new level. Keep it up. And I like the top-to-bottom updates.
Putting update on the lineup post itself is great. However, I would strongly recommend that you put newer updates at the bottom, rather than the top. That way, if you read the post late you won’t get confused by the updates, especially when updates contradict an earlier (“he’s injured!” to “Err, never mind!”, if the latter was first that would be bad).
Also, as long as the post is properly updated in WordPress or whatever you’re using, the RSS feed will update the entry so us RSS readers won’t miss anything.
Phil Oye-0
what rss feeder/reader do you use/recommend??
Pete,
I love the updates posted on the front page. I prefer not having to wade through 95% of idiotic comments to get to the meat of what I’m looking for.
Also, I like the newer updates at the bottom. It just reads better.
Thanks for all your updates. I’m down in Texas, so getting news like this can only come from a few sources. You have proven to be the most accurate and the quickest to update. Thanks for adopting the blogging feature!!!
I am going to go with the updates on the bottom. That way I can miss one and follow along going down and not hit a “spoiler” if you post the updates at the top of the post…
Keep up the great work! Thanks!
The person with the comment about RSS feeds has a valid point. Feedreaders won’t pick up an “updated” post, so if that’s the only way you read a blog, you’ll miss the updates (and more and more people are now reading via RSS readers).
Secondly, the updates always go at the TOP of a post (take a look around the blogosphere), which is how someone knows that there actually IS an update to a post. If the update is at the bottom, they’re more likely to miss the fact that an update has been posted.
test
Ghost of Yankees Past, I use NetNewsWire on the Mac.
12to6, I couldn’t disagree with you more. Updates at the top is fine, if you saw every iteration of the post, but what happens when you come late? It is IMPOSSIBLE to follow along. For example, if you check out today’s (Sunday’s) game 42 link. There are NINE updates. I didn’t bring up the page until just now. To read that page is impossible. You need to start in the MIDDLE, read down, then scroll up to the FIRST update, read down a few lines, then scroll up, remember where you were to find the SECOND update, etc. Maddening. Too hard. Not everyone reads these entries in real-time.
12to6, one more thing.
I do agree that updates at top are useful when you’re about to say “Hmm, I was totally wrong with this post” or something. That alerts the user to read the post with the update in mind. But for multiple chronological updates that merely ADD information? No way.
Interesting article. I found some more information here