Architecting LINQ To SQL Applications
Tuesday, July 01 2008 - programming, c, linq, sql - 0 comments
Ian Cooper has written a blog series on Architecting LINQ to SQL applications. I thought I would create an index to each part.
- Architecting LINQ To SQL Applications, Part 1 - Introduction
- Architecting LINQ To SQL Applications, Part 2 - Layered Architectures
- Architecting LINQ To SQL Applications, Part 3 - DAOs and Repositories
- Architecting LINQ To SQL Applications, Part 4 - Dynamic Queries
- Architecting LINQ To SQL Applications, Part 5 - Recap
- Architecting LINQ To SQL Applications, Part 6 - Mapping with XML files instead of Attributes
- Architecting LINQ To SQL Applications, Part 7 - Managing Entity Lifetimes
- Architecting LINQ To SQL Applications, Part 8 - Tiers
- Architecting LINQ To SQL Applications, Part 9 - LINQ To SQL with N-Tier: Why is there pain?
- Architecting LINQ To SQL Applications, Part 10 - End of the line
Tiny Projects - Two Thumbs Up
Wednesday, March 19 2008 - programming, software, agile, project-management - 0 comments
I really couldn't say this any better myself.
When do we do our best work? When we’re excited about something. Excitement morphs into motivation. We do our best work when we’re motivated. A great way to stay motivated is to work on something new. No one likes being stuck on a project that never seems to end.
Tiny projects keep it new - (37signals).
You should break large projects up into smaller projects/milestones. Each of these milestones should then breakdown into a certain set of functions/features. The programmer assigned to develop the feature then creates a tasks requiered to complete the implementation of the feature.
This process seems to be one of the building blocks of agile development. You have a sprint, which includes a certain feature set to be implemented. During a sprint, refactoring can/will take place to modify existing-features to support/streamline newer feature in the code-base.
