Seriously use Animals, it works great. And that’s what nailed the concept for me years ago. Just found this C# code. It seems good // Assembly: Common Classes // Namespace: CommonClasses public interface IAnimal { string Name { get; } string Talk(); } // Assembly: Animals // Namespace: Animals public class AnimalBase { private string … Read more
Global data is bad. However many issues can be avoided by working with static methods. I’m going to take the position of Rich Hickey on this one and explain it like this: To build the most reliable systems in C# use static methods and classes, but not global data. For instance if you hand in … Read more
I once wrote this function to perform that exact task: public static string Column(int column) { column–; if (column >= 0 && column < 26) return ((char)(‘A’ + column)).ToString(); else if (column > 25) return Column(column / 26) + Column(column % 26 + 1); else throw new Exception(“Invalid Column #” + (column + 1).ToString()); }
There’s nothing wrong with direct, “ad-hoc” solution. It can be clean enough too. Just notice that spiral is built from segments. And you can get next segment from current one rotating it by 90 degrees. And each two rotations, length of segment grows by 1. edit Illustration, those segments numbered … 11 10 7 7 … Read more
Tongue-in-cheek O(NlogN) solution Perform an FFT on your string (treating characters as numeric values). Every peak in the resulting graph corresponds to a substring periodicity.
TDD — write the tests first, forces you to think about testability and helps write the code that is actually needed, not what you think you may need Refactoring to interfaces — makes mocking easier Public methods virtual if not using interfaces — makes mocking easier Dependency injection — makes mocking easier Smaller, more targeted … Read more
Reasons NOT to use short-circuit evaluation: Because it will behave differently and produce different results if your functions, property Gets or operator methods have side-effects. And this may conflict with: A) Language Standards, B) previous versions of your language, or C) the default assumptions of your languages typical users. These are the reasons that VB … Read more
where P is the point, C is the center, and R is the radius, in a suitable “mathy” language: V = (P – C); Answer = C + V / |V| * R; where |V| is length of V. OK, OK double vX = pX – cX; double vY = pY – cY; double magV … Read more
For exactly three terms, you can use this expression: (a ^ b ^ c) && !(a && b && c) The first part is true iff one or three of the terms are true. The second part of the expression ensures that not all three are true. Note that the above expression does NOT generalize … Read more
I follow the same syntax as you, it’s less verbose. People (more beginner) prefer to use == true just to be sure that it’s what they want. They are used to use operator in their conditional… they found it more readable. But once you got more advanced, you found it irritating because it’s too verbose.