Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
2 9
Impact
~880 people reached

Jun
19
answered specification regarding a text file
Jun
15
revised SDK/DB isDeleted vs Integration Testing
Mention explicit TestUsers and a delete method.
Jun
15
comment SDK/DB isDeleted vs Integration Testing
Right, that is a harder scenario. My first thought is a conditional build that only includes the endpoint for testing purposes. It could be that the WSDL, etc. only includes the endpoint when retrieved by the testing machine's IP address.
Jun
15
revised SDK/DB isDeleted vs Integration Testing
Answer the question...; typo
Jun
15
answered SDK/DB isDeleted vs Integration Testing
Jun
15
comment Has variable width types been replaced by fixed types in modern C?
Anyone happening to want to manually implement pow, remember this code is just an example and does not cater for exponent=0!
Jun
10
comment Project a piece of image cut by N-vertex shape to a different N-vertex shape
So you'd prefer an interpolation that is not linear, but rather "skewed" to keep the internal as similar as possible and have bigger adjustments near the edges, I presume.
Jun
10
comment specification regarding a text file
If you don't have access to a Win8.1 64-bit machine without Visual Studio installed to test on it will be hard to ensure it works, but as long as you use a .NET Framework version not later than the one installed with Win8.1 you should be OK (as later .NET Frameworks will be used if the one used to build your program is not available, and as long as you don't use a feature broken by an update you'll be fine).
Jun
3
answered Testing strategy for wrapper class
May
13
comment Why would Square inheriting from Rectangle be problematic if we override the SetWidth and SetHeight methods?
I effectively disagree with Eric here (not enough for a -1 though!). All those relationships are (possibly) relevant, as @supercat mentions; it's just a YAGNI issue: you don't implement it until you need it.
May
13
revised Is a 1 < 10 comparison less expensive than 1 < 1000000?
Explicitly mention the intention of the optimisation is to tokenise once.
May
13
comment When asynchronous tasks make a bad UX
I agree with this approach, except that I would still keep a ParseStarted event, in case you do want to allow the UI (or other component) to sometimes warn the user a reparse is occurring. Of course, you may want to document callers should attempt to not stop the user from using the (about to be) stale current parse results.
May
6
comment Should we define types for everything?
+1 although if you haven't yet refactored all the code of doFancyOtherstuff() into a subroutine, you might think the job.do(id) reference is not local enough to keep as a simple string.
Apr
8
comment How much work should I place inside a lock statement?
Note that given the answers, the title of this question is now effectively wrong.
Feb
18
answered How much physical memory is consumed by the stack of a .NET thread?
Feb
4
comment Are there any benefits of using this extra variable in the for loop annotation?
Note that in certain languages this code will be less performant because of compiler optimisations that are designed for the direct length retrieval only.
Feb
4
answered Is a 1 < 10 comparison less expensive than 1 < 1000000?
Jan
21
comment Is address 0000000C a special address?
Perhaps that System.Runtime.CompilerServices.RuntimeHelpers.OffsetToStringData is 12=0x0C is a reason why this offset is more common.
Jan
15
comment When should a private method take the public route to access private data?
Even for this "small" example, getA() * getB() is better in the medium and long term.
Jan
15
comment When should a private method take the public route to access private data?
I can't give you a +1 because your example to use private fields is not one IMHO, mainly because you have declare the const: I assume that means the compiler will inline a getId call anyway and it allows you to make changes in either direction. (Otherwise I fully agree with your reasons to use getters.) And in languages that do provide property syntax, there's even fewer reasons to not use the property rather than the backing field directly.