I use it as well, and for the most part it's a good browser. But in the long run, it would serve us all best to go back to Firefox.

I use it as well, and for the most part it's a good browser. But in the long run, it would serve us all best to go back to Firefox.

Writing about already known subjects has always been around. Some people do it to show off what they know, some to learn as writing makes them ask questions they otherwise wouldn't ask. Personally, I avoid writing anything as I don't have anything to say that's not already found in one of this communities. I don't, however, find this to be good behavior, neither for me nor for community. It's just fear of failure. Shortly, you should continue writing but need to expect less from your readers, and expect criticism. You can't say anything new in IT that's not already there. You just need to try and outperform other articles and present your views in a way that will be easy to read and can hold readers attention for longer without skimming on important information. Are you up to it? :) I'm not yet :)

I guess Windows 7 thinks it's smarter to use all those remaining GBs that it displays as free, as disk cache :) Here's hoping that in 5 years storage and working memory will be in one superfast NAND device :)

If you really have a solution that causes VS to consume more than 1GB of ram after building/debugging for a day, you seriously need to rethink your solution structure and break it into parts. I have my instances of VS running for days, developing solution with >180 projects and VS never needs more than 700Mb of RAM.

PIN is more similar to usual business cases than wings falling off a plane :) Anyhow, maybe I could make up a rule that would say: Do not use exception handling if result of failed operation is displayed to end user, and end user is expected to understand it (there can be exceptions to this :) )

:D True. I didn't expect myself properly, but still. If user enters invalid PIN code, would you use exception to handle this situation? I'd argue you shouldn't.

It may seem structurally sound, but it's a mistake to use exception handling for control flow. First, exceptions are exactly that. Cases which you do not expect should happen in normal workflow, exceptional situations which are caused by a failure in the system. They should not be used to control business logic. However, I am also tempted to use them in this way when I have more than 2 layers of abstraction between business logic decision, and handling of that decision. Second, it's big hit to performance. If this is not client side code, or a single occurrence during request processing, this can be real PITA when you come to a stage you need to optimize performance.

I actually sometimes check is some condition is not fulfilled even when there is else branch. This I do in cases when one case of if/else block is expected behavior and in other one i do simple logging/recovery or similar thing. Specifically, I do this when one block is short (less than 5 lines), and put that block in front. In that case, code is more clean to my eye because else block is very near to if block. This is very helpful to me when i have several nested if/else structures. Would that make sense to anyone but me?

hehe :) I don't think any ORM solution will be good for such thing. If you find one I'd like to hear about it :)

If you don't like it, you most likely don't need it. Luckaly, there are plenty of other solutions for you to choose from. Properties must be virtual in order to allow functionality that uses AOP. Like lazy loading for example. If you ever worked on enterprise grade solutions, you probably noticed that loading an entity from database complete with entire graph of stuff connected to it, is not just a performance hit, but a complete show-stopper.