Timeline for How to apologize when you have broken the nightly build [closed]
Current License: CC BY-SA 3.0
58 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 25, 2016 at 13:42 | history | edited | gnat | CC BY-SA 3.0 | removed irrelevant tag |
| Mar 8, 2016 at 22:08 | history | edited | Lightness Races in Orbit | Removed obviously irrelevant tag. | |
| Mar 8, 2016 at 20:42 | history | edited | Jimmy Hoffa | edited tags | |
| Apr 10, 2015 at 1:45 | review | Reopen votes | |||
| Apr 11, 2015 at 13:29 | |||||
| Apr 10, 2015 at 1:41 | history | closed | CommunityBot ratchet freak Robert Harvey Eric King | Opinion-based | |
| Apr 9, 2015 at 14:52 | review | Close votes | |||
| Apr 10, 2015 at 1:41 | |||||
| Jul 6, 2014 at 2:53 | history | edited | Aaron Hall | CC BY-SA 3.0 | words. |
| May 14, 2013 at 13:52 | comment | added | John R. Strohm | As the old meme goes, there are exactly two kinds of programmers, those who HAVE broken the build, and those who WILL. Say "OOPS! I'm sorry!" and don't worry about it. | |
| May 14, 2013 at 3:36 | answer | added | linquize | timeline score: -2 | |
| May 7, 2012 at 14:50 | answer | added | JeffO | timeline score: 1 | |
| May 7, 2012 at 14:44 | comment | added | JeffO | How about, "Sorry, you didn't catch these errors during the code review." | |
| May 7, 2012 at 14:08 | comment | added | Jaydee | "people are all over me as we are nearing the release". Haven't they read the Mythical man month en.wikipedia.org/wiki/Brooks%27s_law "Adding people to a late project makes it later.". Your project may not be late yet, but if you are nearing release, I'd think hard about bringing new people on board. | |
| May 7, 2012 at 10:47 | answer | added | Pieter B | timeline score: -2 | |
| May 7, 2012 at 0:04 | comment | added | mjfgates | Entrails. Entrails is always good. | |
| May 6, 2012 at 23:50 | answer | added | S.Robins | timeline score: 0 | |
| May 6, 2012 at 23:02 | answer | added | CodeART | timeline score: -2 | |
| Mar 18, 2012 at 13:39 | comment | added | dukeofgaming | Where I work, you have to wear a pink hat until you fix it. Takes the stress away from the error and everyone has a good laugh (even the responsible one) and no one has to apologize verbally. | |
| May 27, 2011 at 15:03 | comment | added | Ramhound | I agree you should not have to aplogize. Of course the solution do not commit anything unless it works. | |
| May 27, 2011 at 2:48 | answer | added | Issa Fram | timeline score: -1 | |
| May 26, 2011 at 23:34 | comment | added | Mateen Ulhaq | CRACK! whizzz... WHAM! ClonK. Cling, Clang, Doink. Wonk. RiNg rInG... BAM! BOOM! KABOOM! | |
| May 26, 2011 at 15:43 | comment | added | Web | Nobody ever apologized to me for breaking the build. | |
| May 26, 2011 at 10:50 | answer | added | Robert Heine | timeline score: -2 | |
| May 26, 2011 at 10:44 | comment | added | kizzx2 | Why are they so mad? They must using some ancient source control like CVS with people never tagging or even writing commit message at all (my company). | |
| May 26, 2011 at 5:17 | answer | added | M. Tibbits | timeline score: 2 | |
| May 26, 2011 at 4:41 | comment | added | WOPR | I broke the build, but I didn't break the deputy | |
| May 25, 2011 at 19:37 | comment | added | Joe Phillips | Tell them you were just testing to make sure the build process worked properly. | |
| May 25, 2011 at 19:26 | comment | added | mikerobi | It could be worse, when we deployed my first project, it took out all of our web services (in production). | |
| S May 25, 2011 at 19:01 | answer | added | user3792 | timeline score: 1 | |
| S May 25, 2011 at 19:01 | history | made wiki | Post Made Community Wiki by user3792 | ||
| May 25, 2011 at 18:34 | answer | added | rajah9 | timeline score: 5 | |
| May 25, 2011 at 16:22 | answer | added | Eric Lippert | timeline score: 44 | |
| May 25, 2011 at 15:53 | comment | added | Max | I just wish i had a nightly build to break.. | |
| May 25, 2011 at 15:37 | answer | added | JaredPar | timeline score: 6 | |
| May 25, 2011 at 15:28 | comment | added | Matthieu M. | @rajachan: in my team, people who "block" the rest of the team (breaking the build, the non-regs, the dev env) are expecting to fix it, perhaps with help if necessary, and to bring croissants on the next morning :) | |
| May 25, 2011 at 15:07 | comment | added | Travis | @rmx I broke the build on my very first commit with the company! Now, we each have a "Get out of one broken build FREE" card :) | |
| May 25, 2011 at 14:32 | comment | added | MVCylon | Buy me a pizza for lunch. I'll forgive you. | |
| May 25, 2011 at 14:26 | comment | added | Chris_O | DO NOT APOLOGIZE! you did nothing wrong. A good working team would make light of the situation. The WordPress project blames Nacin every-time the nightlies get broken. One time he knocked out the dashboard for 10 million users so don't feel bad. | |
| May 25, 2011 at 14:07 | answer | added | Christoffer Hammarström | timeline score: 0 | |
| May 25, 2011 at 14:05 | answer | added | rerun | timeline score: 2 | |
| May 25, 2011 at 13:47 | answer | added | temptar | timeline score: 2 | |
| May 25, 2011 at 13:26 | comment | added | Dyppl | I try really hard not to break server builds with my commits. But if one day I do and somebody tells me to apologize for it I'll probably just tell them to go to hell. It happens, it's not a tragedy unless the configuration of your build system is particularly moronic | |
| May 25, 2011 at 13:07 | comment | added | Homde | If one breaks the build because of excessive slopiness then an sincere (but not seppu-level) apology might be in order. If not, shit happens. It's really bad when corporations adopt a culture of "check-in fear" where everyone's afraid to make mistakes and the check-in police roam the corridors. I've seen it many times and always lead to so much fear and check-in policies that it's impossible to get anything done. Make mistakes quickly, fix them quickly, repeat. | |
| May 25, 2011 at 13:02 | comment | added | Nobody | I broke the build on my first 10 commits! Dont worry about it | |
| May 25, 2011 at 13:00 | answer | added | Mike Dunlavey | timeline score: 11 | |
| May 25, 2011 at 12:54 | comment | added | Paul R | Just make it clear that you have learned your lesson and that in future you will always do a test build before checking in changes. | |
| May 25, 2011 at 12:44 | comment | added | Jas | How about : "I am very sorry for breaking the night build. If you want to withold my salary as a form of punishment, I will not take the company to employment tribunal". Nah, just kidding - do not apologize, this sort of stuff happens all the time. People who are "all over you" are f.king psychos who don't know how to properly restore the system to previous state. | |
| May 25, 2011 at 12:42 | answer | added | guillaume31 | timeline score: 16 | |
| May 25, 2011 at 12:36 | answer | added | Dan Ray | timeline score: 184 | |
| May 25, 2011 at 12:27 | vote | accept | rajachan | ||
| May 25, 2011 at 12:25 | answer | added | Corv1nus | timeline score: 2 | |
| May 25, 2011 at 12:12 | history | tweeted | twitter.com/#!/StackProgrammer/status/73360858683674624 | ||
| May 25, 2011 at 12:10 | answer | added | Sub S | timeline score: 0 | |
| May 25, 2011 at 12:01 | comment | added | user1249 | How were you to know that the build was broken? | |
| May 25, 2011 at 11:54 | comment | added | Lazarus | If the build never broke I'd begin to suspect a broken build process ;) | |
| May 25, 2011 at 11:54 | answer | added | Lazarus | timeline score: 80 | |
| May 25, 2011 at 11:51 | answer | added | maple_shaft♦ | timeline score: 54 | |
| May 25, 2011 at 11:47 | answer | added | Jim G. | timeline score: 307 | |
| May 25, 2011 at 11:43 | history | asked | rajachan | CC BY-SA 3.0 |