211 reputation
16
bio website
location
age
visits member for 3 years, 3 months
seen Apr 7 at 16:57

Jul
3
awarded  Yearling
Jun
12
comment Mercurial release management. Rejecting changes that fail testing
This seems ok if you know the feature is going away completely. If that's not true though, you may have problems: the backout looks like "i don't want this anymore" -- so if you go back to the original feature branch and fix the problems and then re-merge, you run a high risk of a bad merge because the backout looks like a "delete" that occurred after the original "add" in the feature.
May
3
answered switch statement - handling default case when it can't be reached
Apr
3
answered How do you name sprints in your projects?
Feb
2
awarded  Critic
Dec
22
awarded  Citizen Patrol
Dec
7
answered Patterns for Continuous Integration and DVCS
Dec
2
comment Patterns for Continuous Integration and DVCS
If you haven't been there already, I suggest you head on over to the Kiln stack exchange site (kiln.stackexchange.com). They have quite a bit of content about how to set this up (here's one: kiln.stackexchange.com/questions/29/…. Personally, we use a branch per feature, and point the build server at our "master" branch.)
Sep
8
awarded  Teacher
Sep
7
answered How do you refrain from doing too much when maintaining code?
Sep
7
comment Can the language make us stupid?
@ThomasX - I wish I had the rep on this site to add my -1 here. You obviously don't understand what dynamic typing means yet you have the audacity to insult anyone who uses it?
Apr
22
comment Why would you want to look at IL code?
Also, just to help understand how some poorly documented code works. We do this all the time when consuming a third-party DLL. Using .Net Reflector, we even do this for built in .Net DLLS from time to time.
Mar
18
awarded  Supporter
Mar
17
awarded  Student
Mar
17
awarded  Editor