On Thu, Mar 27, 2014 at 11:28:06PM -0700, Chris de Morsella wrote: > > > > > From: [email protected] > [mailto:[email protected]] On Behalf Of LizR > Sent: Thursday, March 27, 2014 5:24 PM > To: [email protected] > Subject: Re: [foar] Amoeba's Secret now available in paperback > > > > On 28 March 2014 05:28, Chris de Morsella <[email protected]> wrote: > > In some ways it can be compared to a recipe. the right ingredients AND the > right timing & sequence is key.. And makes the difference in outcome between > some sad lump of something and the brilliant cake. > > > > Yes, although I think you get (easier) second chances with programming. > > LOL that you do. though in many big environments if you break the build once > you get to eat raw broccoli; you break it twice you're fired. So then again > perhaps not, in some cases. >
That's tough love! In my last team, you had to buy the wine for the next team lunch if you broke the build. That way: a) discourages you from being too cavalier with your submits, b) mollifies your team-mates who might have had to have dealt with consequences of the broken build and c) doesn't scare you shitless about having to commit something that might break the build and possibly lose your job. If you've ever had to deal with a screwed subversion system after trying to upgrade your boost libraries, or after trying to upgrade you Visual Studio version, you'll know there are times when breaking the build is inevitable. Also, if the build times are on the order of 3 hours (as it was in one place), then the "no break the build" policy means that you cannot do a commit after 11am, otherwise you potentially will be staying back after work to fix the build. In that job I used to get everything to the commit stage, then go home. There was an automatic script that synced the repository to my local copy and built as much as possible. When I got in next morning, I did another sync, and build, and usually I was lucky that that finishes by 11am, so that I can commit that day. If not, I'd spend the rest of the day trying to fix my local build, and once that was done, catch up on code reviews, as I couldn't actually do any new coding until I had successfully committed the previous stuff the following day. I much preferred the situation where I could bribe my colleagues with a few glasses of wine if I needed to. Also, I have done my share of remote login to check and fix builds after hours, but that's not always feasible when you've got family depending on your being home. -- ---------------------------------------------------------------------------- Prof Russell Standish Phone 0425 253119 (mobile) Principal, High Performance Coders Visiting Professor of Mathematics [email protected] University of New South Wales http://www.hpcoders.com.au Latest project: The Amoeba's Secret (http://www.hpcoders.com.au/AmoebasSecret.html) ---------------------------------------------------------------------------- -- You received this message because you are subscribed to the Google Groups "Everything List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/everything-list. For more options, visit https://groups.google.com/d/optout.
