Deep Insights in Microsoft .NET

I know that the MS rules say this is not a good idea. However, I disagree, for example if a method takes a parameter which is an object, and this is not for an API., it is ok to create a class within a class when this class is meant to be used to pass stuff to this particular class only. Better than putting it out in the open namespace, when it is tightly bound to this class only. Sometimes, this is useful for an Enum also. Because then you can have enums with the same name, but within different classes. This often happens when writing code.

Programmers can be categorized into the below: 1. Those who have no idea about what they are doing. 2. Those who just manage to do the job. 3. Those who can do the job if you tell them how exactly to do something. 4. Those who write code for years and learn by experience doing things differently each time. 5. Those who write code for years and gain experience but always do stuff the same way. 6. Those who have a degree in CS but who have little hands on coding experience. 7. Those who have a degree in CS who can get around decently. 8. Those who have a degree in CS and can talk very well, but do little in the real world. During interviews, choosing a candidate can be a big problem because sometimes we select the guy who can talk really well, but who cannot do any practical work on a day to day basis. The guys who can code really well, may not do well in the interview at all. Sometimes the candidate with the worst feel in the interview, might be the exact fit for the...

I am not interested in a job, where you want to hire the most intelligent person you can find, then expect this person to work like a robot exactly like the manager wants him to.  I don’t care about positions myself but because everyone else does , I am only interested if the role is that of a senior manager, chief software architect, etc. I am not a robot, and never will be.  I will never work in North Korea, Saudi Arabia or any environment where these regimes are recreated. Consulting companies are the scum of the earth. Hence, I will never work for a consulting company, period. I will not keep quiet if someone accuses me of something I had no control over. I am not interested in a job, where the previous person left because it was a pressure cooker environment.  I am not interested in a job where the manager could never work with anyone they have hired before, so they are looking for a new person.  I am not interested in a job, where the person who I will...

Unity Framework, shortly followed by Sync Framework. If you use either, then you have low self esteem, and try to boost it, by using something someone else has built. 99% of the people who use these should not be working in software development, because they don't have aptitude for software engineering. Try something else like cooking, or hiking, etc. Just because someone else wrote it does not mean, you can shut your eyes and pretend it will solve all the problems. Microsoft please stop creating these ugly, massive frameworks full of defects, with bombastic names which ignorant people use everywhere in their code, making it a nightmare to maintain or to reuse. Calling a simple thing a complicated name, does not make it great. If you do release stuff like this, put the source code in the open so someone can fix this mess, because you don't support it anymore. I can see now how Steve Jobs saw the ugliness in Windows.