I really enjoyed this article regarding DI, as it’s targeted towards people who don’t have a ton of DI experience, or don’t even know what it is. https://mtaulty.com/2009/08/10/m_11554/ What’s Unity? It’s a “dependency injection container”. Now, at that point a bunch of folks reading this will say “Yes, we know and we’re already using it … Read more
Personally: for _ in range(50): print “Some thing” if you don’t need i. If you use Python < 3 and you want to repeat the loop a lot of times, use xrange as there is no need to generate the whole list beforehand.
You really should not be using RMI for any application you build today, basically for the reasons you just laid out. In some cases (diving into legacy or “enterprise” applications) you just have no choice. However, if you are starting a new project, other options are: REST + JSON over HTTP The de-facto standard for … Read more
To me, a more modern example of spaghetti code is when you have 20 dlls and every DLL references each other in one way or another. Your dependency graph looks like a huge blob, and your code hops all over the place with no real order. Everything is inter-dependent.
I am thinking of using the Visitor pattern. public class Car : Vehicle { public void Accept( IVehicleFormatter v ) { v.Visit (this); } } public class Truck : Vehicle { public void Accept( IVehicleFormatter v ) { v.Visit (this); } } public interface IVehicleFormatter { public void Visit( Car c ); public void Visit( … Read more
Spaghhetti: Spaghetti code is a pejorative term for source code Ravioli: Ravioli code is a type of computer program structure, characterized by a number of small and (ideally) loosely-coupled software components. The term is in comparison with spaghetti code, comparing program structure to pasta; It’s comparing them. It isn’t saying it’s an anti-pattern. But I … Read more
Uninitialized exception vectors (you know, for the ones that “will never be reached”) Say it with me: Global variables. Especially ones shared between ISRs and tasks (or foreground loops) without protection. Failure to use “volatile” where necessary. Having routines that DisableInterrupts() and then EnableInterrupts() paired up. Got that? Not RestoreInterrupts(), but ENABLE. Yeah, nesting. No … Read more
Normally a better approach (IMHO) would be to use interfaces instead of inheritance then it is just a matter of checking whether the object has implemented the interface or not.
I’d go for the multiple return statements. This makes the code easy to read and understand. Don’t use goto for obvious reasons. Don’t use exceptions because the check you are doing isn’t exceptional, it’s something you can expect so you should just take that into account. Programming against exceptions is also an anti-pattern.
Rethrowing the exception incorrectly. To rethrow an exception : try { // do some stuff here } catch (Exception ex) { throw ex; // INCORRECT throw; // CORRECT throw new Exception(“There was an error”); // INCORRECT throw new Exception(“There was an error”, ex); // CORRECT }