Something for the .net programmers out there. I guess this is a top level question... As you maybe some of you have read, I am going through an issue with quality of code etc.
My boss has delivered some code today / this morning which I cannot understand his logic. I'm a C# developer since PDC 2001 and he's from a from a C / C++ background. Everything to him he has to box as an Object, I'm still standing my ground and yes... there has to be a certain amount of encapsulation but not to the degree where code is unmanageable and you have to 'Go To Definition' in VS on several layers to understand what its doing. Surely we have an object but its Component Design now, albeit it's based on a Base Class. Finding it frustrating now. Segregate objects !
My boss has delivered some code today / this morning which I cannot understand his logic. I'm a C# developer since PDC 2001 and he's from a from a C / C++ background. Everything to him he has to box as an Object, I'm still standing my ground and yes... there has to be a certain amount of encapsulation but not to the degree where code is unmanageable and you have to 'Go To Definition' in VS on several layers to understand what its doing. Surely we have an object but its Component Design now, albeit it's based on a Base Class. Finding it frustrating now. Segregate objects !
Comment