Comments on: Post-Mortem on This Term’s Work http://third-bit.com/blog/archives/1850.html Data is ones and zeroes | Software is ones and zeroes and hard work. Tue, 22 May 2012 16:23:22 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Steve Eddins http://third-bit.com/blog/archives/1850.html#comment-2401 Steve Eddins Mon, 29 Dec 2008 13:52:54 +0000 http://pyre.third-bit.com/blog/archives/1850.html#comment-2401 Regarding code freezes ... before we started releasing on a fixed, semi-annual schedule a few years ago, we often had a hard time getting our releases to converge. After the code freeze was widely and blatantly ignored during one release, I decided to appropriate the term for a different purpose. Now, whenever I send a calendar invite to our team for a "code freeze," it means we are going out to Ben & Jerry's for an afternoon ice cream. Regarding code freezes … before we started releasing on a fixed, semi-annual schedule a few years ago, we often had a hard time getting our releases to converge. After the code freeze was widely and blatantly ignored during one release, I decided to appropriate the term for a different purpose. Now, whenever I send a calendar invite to our team for a “code freeze,” it means we are going out to Ben & Jerry’s for an afternoon ice cream.

]]> By: Greg Wilson http://third-bit.com/blog/archives/1850.html#comment-2400 Greg Wilson Wed, 24 Dec 2008 18:08:02 +0000 http://pyre.third-bit.com/blog/archives/1850.html#comment-2400 I should have written the point out in full: there's nothing wrong with distributed version control systems per se; trying to use SVN *as if* it was Git, Mercurial, or something like that was the mistake. But on that note: if anyone has any empirical data of any kind showing that DVCS's make any task faster or less error prone, I'd like to see it. (I'd also like to see any that indicates DVCSs are slower or more error prone, too...) I should have written the point out in full: there’s nothing wrong with distributed version control systems per se; trying to use SVN *as if* it was Git, Mercurial, or something like that was the mistake.

But on that note: if anyone has any empirical data of any kind showing that DVCS’s make any task faster or less error prone, I’d like to see it. (I’d also like to see any that indicates DVCSs are slower or more error prone, too…)

]]> By: dv http://third-bit.com/blog/archives/1850.html#comment-2399 dv Wed, 24 Dec 2008 17:51:43 +0000 http://pyre.third-bit.com/blog/archives/1850.html#comment-2399 Roger, then there would have been another point in the "Bad" : "Students needed a lot of time to wrap their heads around DVCSs and use them effectively". Roger, then there would have been another point in the “Bad” : “Students needed a lot of time to wrap their heads around DVCSs and use them effectively”.

]]> By: Roger http://third-bit.com/blog/archives/1850.html#comment-2398 Roger Wed, 24 Dec 2008 03:19:05 +0000 http://pyre.third-bit.com/blog/archives/1850.html#comment-2398 You said merging was a pain, but should have resisted DVCS more. The one thing the DVCSs are very good at is merging so your statement appears contradictory. You said merging was a pain, but should have resisted DVCS more. The one thing the DVCSs are very good at is merging so your statement appears contradictory.

]]>