Reputation
7,098
Top tag
Next privilege 10,000 Rep.
Access moderator tools
Badges
3 23 30
Newest
 Guru
Impact
~212k people reached

Aug
2
comment Can someone explain to me C#'s coding convention?
C# and Delphi (whose creator is the same) both are case-INsensitive and thus can never have collisions with stuff that only differs in casing. Both therefore also have conventions for naming private member variables. In Delphi they start with F, in C# with an underscore. Camel cased method names therefore never conflict with (private) member variable names. Plus there is never any ambiguity about whether you are dealing with a var or a method.
Aug
2
comment REST API Library Conventions
If getUserInfo just passes its parameters through to the apiCall, then there is little sense in having it. As soon as getUserInfo is part of a larger class that hides away setting up memory structures, handling state, or other such awkwardness, then it is very much wanted. It would then be analogous of any IDE's library that deals with the OS's widgets for the GUI. I know that using Delphi I certainly do use the Windows API frequently without reading its documentation because the Delphi VCL and RTL hide it nicely for me. I only delve into the API when I need to code an API call my self.
Aug
1
comment Add complex customization to form or create two forms?
Assuming that your choice is purely one of implementation, that is the user experience would be the same regardless of your choice, always go for the more maintainable option. Complexity kills (speed of) future enhancements...
Jul
28
comment Pros and Cons of holding all the business logic in stored procedures in web application
+1, for the first bit, -1 for multiple applications advice. There is no need to put everything in the database when multiple apps are involved. Just make all applications go through the same business layer. Three tier development wasn't invented just for the fun of it.
Jul
27
comment Should architect or dev lead tell teammate where to add their code before coding a new feature?
Ah! :-) thanks.
Jul
27
comment Should architect or dev lead tell teammate where to add their code before coding a new feature?
CYA?............
Jul
27
answered Is my mediator layer a sensible way to manage this scenario using the Single Responsibility Principle?
Jul
26
comment Is there any design pattern except MVC for web?
+1 but MVP, MVVM and MVC are all variations of the same theme: separating (g)ui from model logic and having some third party (controller, presenter) mediate between them.
Jul
18
comment In a web application, is it ok to group multiple pages in one view class or one class per page?
@RobertHarvey: yes, models are the M in MVC, but not necessarily the business model with all the business logic which should indeed be somewhere in a middle tier between the front-end MVC and the back-end database. As such the M in a front-end MVC can be very anemic...
Jul
9
comment Should I expose IObservable<T> on my interfaces?
@haylem: While the question is about .Net reflection, it is more a general design/concept question than one asking for a solution to a specific problem. And it is applicable not just to .Net, but to any language supporting run-time investigation of instances etc.
Jul
9
comment Am I too young to burn out?
+1, especially for the "Market yourself". That's something we geeks often forget. We sort of think that everybody should recognize what we are doing without us telling them. Well, sorry, most people just take for granted that we are doing our jobs and many bosses simply need gentle reminders about our achievements.
Jul
1
answered Overwhelmed by complex C#/ASP.NET project in Visual Studio 2008
Jun
27
comment How do employers measure “strong or solid knowledge of programming language”?
"If you have to ask..." ... Or, (s)he's over qualified. The more you know, the more you know what you don't know...
Jun
24
comment How does team development work?
Yes, I have been in such shops as well. Not nice to be the one stuck with the xxx part of the code base, but aside from that, it is also a very bad policy from a business risk perspective. If something happens to the sole code owner, you are definitely in a pickle. And unfortunately when something does happen, it usually is at the very worst moment it could ... And even if everybody stays healthy and with you, it doesn't scale very well when you have to switch gears in order to get a release out the door.
Jun
24
comment How does team development work?
+1, though ownership should last as short as possible. With us it is until shipped (or one release extra). After that everybody is expected to be able to work on it.
Jun
22
comment Non-blocking ORM issues
@RobertHarvey: asynchronous retrieval sounds pretty good actually. The ORM would be supplied with a callback or some such to "activate" when data has been received. Otherwise your ORM needs to be split of in a separate thread to guarantee UI responsiveness.
Jun
21
comment For an ORM supporting data validation, should constraints be enforced in the database as well?
If data in your database can routinely be modified without using your ORM (other apps without your ORM, or, worse, direct db access by users), the validation really needs to be in the database.
Jun
8
awarded  Constituent
Jun
8
awarded  Caucus
Jun
4
comment What are best practices when switching between projects/coming back to projects frequently?
Neat use of VM's