The problem A lot of software engineers get into the industry and often end up starting to write code soon after they read the requirements specification. Sounds familiar? You might have done it too. Hard to admit? Can be. We are humans, after all. Jumping right into the coding process might be a great idea for a simple coding challenge, where the objective is to solve a problem in as little time as possible, with potentially very few lines of code....
LINQ stands for Language Integrated Query Language. It was a feature introduced along with Visual Studio 2008 that extends the querying capabilities of C# for any sort of data source. Generally LINQ is used to query data sources like SQL Server Databases and XML files. I use it to query databases. I’m not going to explain everything about LINQ here. I’m going to just talk about some very basic details....
As you might have noticed from my recent posts, I’ve just recently jumped from one platform to another. And my current project is a bit of a legacy thing. A lot of people worked on it previously and those who did weren’t necessarily experts in the technology that they used when they initially developed it. They did a lot of hacky things, to get things going. But such hacks are good for getting a product moving, but not really good for maintaining them....
I think as programmers you should read and understand this: http://martinfowler.com/ieeeSoftware/explicit.pdf From the expert in OOAD and related stuff - Martin Fowler.