We’ve got a great team. We’re trying to show it off, as is probably evident from the significant uptick in posts since August. If it seems like we’re bragging, we are. Rally is a great place to work (still bragging) and we want to show it off, to the tune of around one post per day.
You’ll soon notice we’ve toned down the Phys-Ed posts. Those started from updates we’d post to an internal mailing list. It seemed like a good idea to share those with the world at the time, but we’ve received some feedback that having those as the last post of the day 40% of the time drowns out more valuable content. They’re not gone – they’re just going to be a bit lest frequent.
We have a saying in engineering that engineering is a free speech zone.
It is.
The Engineering Blog is us telling anyone willing to listen how we see it while exercising the common sense some public figures seem to lack. (Hank Williams Jr. anyone?) We say things around engineering that are simply not a good idea to print, regardless of the first amendment. Hank Williams had every right to say what he said, but that doesn’t mean it was a good idea to do so in a public forum. Telling the world about my mom’s foosball shot is fine. Some of the other things we say about each other’s mothers are not.
The whole point of the free speech rant is that without asking anyone for permission, I’m going to publicly expose the motivation behind the uptick in posts here. Normally, I’d send this for proofreading to Steve or Adam. Not this time. Steve is not from this country, so I don’t trust him. Adam’s from “The South”, so he can’t spell.
Before anyone lumps me with Hank, I’m kidding.
Here’s the big secret: We want the engineering blog to be a resource to the community and our customers, a way for us as rally engineers to educate each other, and a recruiting tool. Those are in no particular order, although some posts are clearly pandering to one objective or another.
What we want now is feedback. We know which posts are the most popular. We want to know why. Please respond in the comments. Which posts are your favorite? Why? Which posts can you do without?
Do you care about scalability? OO programming? Automated testing? Foosball? Phys-Ed?
Why?
Are there particular post titles that influenced you read the post?
Whatever your reason for reading, please let us know in the comments. If you have a reason for not reading, you’re either lying or you’ve clearly read this far because you’re hypnotized by my skills as a wordsmith.

Thanks for asking your readers about what types of content they are most interested in. I am a program manager that is always looking how to implement best practices and love hearing about how “others” in the agile space are structuring their teams and the practices they use to create great software. I love the idea of using a engineering blog as a recruiting tool. Looking forward to more posts from your team.
Love the posts on scalability and testing. We are a Microsoft shop for now, but most of your posts are either platform independent, or help give me good ideas on how things could be done. Keep up the good work. Cutting down on the PhysEd stuff without removing it entirely is a good thing.
I like the posts about software issues you encounter and how you attack them. I also like more general advice posts for agile from an engineering perspective (that’s mostly what I posted about when I was there).
I also enjoy posts about JavaScript and particularly JavaScript testing, which is notoriously difficult.
I definitely don’t care about foosball or PhysEd. Hell, I didn’t care about that stuff when I was on the team.
Thanks for the feedback — it is invaluable and very much appreciated.
We want to produce posts that are useful and interesting to the community so keep telling us what works and doesn’t.
Blog retro!