dstelow notes…

Just another Wordpress.com weblog

links for 2010-02-09

leave a comment »

Written by dstelow

February 9, 2010 at 11:01 pm

Posted in 1

links for 2010-02-06

leave a comment »

  • …I’m a big fan of giving relational systems the boot when it comes to persisting application data. The more I work with document (or OO) databases, the more I feel really, really dumb for doing it any other way.
  • …The Entity Framework is a new part of ADO.NET that allows you to build your applications against conceptual data models. It provides a greater level of abstraction and supports code that is independent of any particular relational database. It provides an Entity Data Model (EDM) for defining data at the database and conceptual level and mapping between the two. It includes a nice set of tools that can be used to generate the EDM and corresponding objects that represent the database. This eliminates much of the required boilerplate data access code, and makes it a snap to create data-centric applications.

Written by dstelow

February 6, 2010 at 11:02 pm

Posted in 1

links for 2010-02-04

leave a comment »

Written by dstelow

February 4, 2010 at 11:03 pm

Posted in 1

links for 2010-01-31

leave a comment »

Written by dstelow

January 31, 2010 at 11:01 pm

Posted in 1

links for 2010-01-30

leave a comment »

Written by dstelow

January 30, 2010 at 11:01 pm

Posted in 1

links for 2010-01-27

leave a comment »

Written by dstelow

January 27, 2010 at 11:04 pm

Posted in 1

links for 2010-01-26

leave a comment »

Written by dstelow

January 26, 2010 at 11:03 pm

Posted in 1

links for 2010-01-25

leave a comment »

Written by dstelow

January 25, 2010 at 11:01 pm

Posted in 1

links for 2010-01-20

leave a comment »

Written by dstelow

January 20, 2010 at 11:10 pm

Posted in 1

links for 2010-01-18

leave a comment »

  • As a solution to this problem, I propose a simple set of rules and requirements that dictate how version numbers are assigned and incremented. For this system to work, you first need to declare a public API. This may consist of documentation or be enforced by the code itself. Regardless, it is important that this API be clear and precise. Once you identify your public API, you communicate changes to it with specific increments to your version number. Consider a version format of X.Y.Z (Major.Minor.Patch). Bug fixes not affecting the API increment the patch version, backwards compatible API additions/changes increment the minor version, and backwards incompatible API changes increment the major version.

Written by dstelow

January 18, 2010 at 11:03 pm

Posted in 1