Remember, Microspeak is not necessarily jargon exclusive to Microsoft, but it’s jargon that you need to know if you work at Microsoft.<\/p>\n
When something has gone horribly wrong and requires immediate attention, one way to describe it is to say that it is on fire<\/i>. The obvious metaphor here is that the situation is so severe that it is as if the office building or computer system was literally on fire.<\/p>\n
Here are some citations I found.<\/p>\n
I’ll be back in Redmond on Monday. Is anything on fire?<\/p><\/blockquote>\n
This person is just checking in to see if there are any emergencies.<\/p>\n
I think the Nosebleed branch is still on fire.<\/p><\/blockquote>\n
This person is saying that they think that the Nosebleed branch is still in very bad shape. My sense that being on fire<\/i> is worse than being on the floor<\/i>. If a branch is on the floor, then that probably means that there’s a problem with the build or release process. But if the branch is on fire, it suggests that they have identified some critical issue in the branch, and everybody is scrambling to figure it out and fix it.<\/p>\n
While looking for citations, I found the minutes for a meeting titled “What’s on Fire Meetings”, which I guess is a regular meeting to report on whatever disaster is currently unfolding this time<\/i>.<\/p>\n
I even found some citations from my own inbox.<\/p>\n
That’s my top item once I can wrap up the work I’m doing for the Nosebleed feature, but Nosebleed is always on fire.<\/p><\/blockquote>\n
Even the fires are on fire.<\/p><\/blockquote>\n
There is a channel on our team called “Fires” which is where people report on anything on fire and collaborate on putting out<\/i> that fire. Putting out fires<\/i> is the preferred way to say that someone is trying to fix whatever is on fire.<\/p>\n
Bonus chatter<\/b>: Note that this is not the same as saying that a person<\/i> is “on fire”, which is slang for saying that they are doing exceptionally well.<\/p>\n","protected":false},"excerpt":{"rendered":"
Dealing with emergencies.<\/p>\n","protected":false},"author":1069,"featured_media":111744,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[105,26],"class_list":["post-111998","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-microspeak","tag-other"],"acf":[],"blog_post_summary":"
Dealing with emergencies.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/111998","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/users\/1069"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/comments?post=111998"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/111998\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media\/111744"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media?parent=111998"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=111998"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=111998"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}