Reputation
7,798
Top tag
Next privilege 10,000 Rep.
Access moderator tools
Badges
3 31 64
Impact
~443k people reached

Aug
6
awarded  Notable Question
Jun
4
awarded  Popular Question
May
24
awarded  Famous Question
Mar
3
comment Is it worth even checking to see if Guid.NewGuid() is Guid.Empty?
@Andy Because I didn't write the code myself and just copy-pasted the pattern as an example?
Feb
26
awarded  Popular Question
Feb
26
accepted Is it worth even checking to see if Guid.NewGuid() is Guid.Empty?
Feb
25
awarded  Nice Question
Feb
25
asked Is it worth even checking to see if Guid.NewGuid() is Guid.Empty?
Dec
29
comment Should the commit history be used to convey critical information to developers?
@MarkBooth I think that answer existed back when I accepted the accepted answer. I upvoted Karl's answer but wasn't a fan of having a unit test because it presupposes that a problem is easily unit testable. Plus, you would still need to have the problem documented somewhere else anyway since most people aren't going to read unit tests to find out that they shouldn't upgrade until after the test fails which wastes valuable time.
Dec
28
awarded  Booster
Dec
21
awarded  Announcer
Dec
19
reviewed Approve Should the commit history be used to convey critical information to developers?
Dec
14
awarded  Nice Answer
Nov
17
awarded  Notable Question
Sep
29
awarded  Famous Question
Sep
17
awarded  Yearling
Aug
4
awarded  Informed
Aug
3
accepted Should the commit history be used to convey critical information to developers?
Jul
31
comment Should the commit history be used to convey critical information to developers?
While the SDK upgrade, which was a minor version number as opposed to major, was what ultimately lead to this question, this line of reasoning has been popping up in the group for awhile now.
Jul
30
awarded  Good Question