Binary Artist

The Jason Marshall Experience

Binary Artist

Jason Marshall
E-mail me Send mail

Recent comments

Authors

Disclaimer

The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

© Copyright 2010

Book Review: Domain-Driven Design: Tackling Complexity in the Heart of Software

Great book by Eric Evens discussing the domain driven approach to software design.

Finishing up this book...a book review will be comming soon...

 

"There are many things that make software development complex. But the heart of this complexity
is the essential intricacy of the problem domain itself. If you're trying to add automation to
complicated human enterprise, then your software cannot dodge this complexity—all it can do is
control it."

"The key to controlling complexity is a good domain model, a model that goes beyond a surface
vision of a domain by introducing an underlying structure, which gives the software developers the
leverage they need. A good domain model can be incredibly valuable, but it's not something that's
easy to make. Few people can do it well, and it's very hard to teach."


Tags: , ,
Categories: C# | LINQ | SQL Server | XNA | Domain Driven
Posted by Admin on Wednesday, May 14, 2008 8:00 AM
Permalink | Comments (0) | Post RSSRSS comment feed

Who wrote this piece of code ?

Don't complain about BAD code you come across, Just fix it. Usually you are not privy to the exact situation surrounding the code you see before you.

It's easy to criticize older code someone else has written, but we have all written code that could be better. 

Ever come across a section of code, and say to your self... "Whoa! This sucks!” I wonder what the developer was thinking here.
Then you look further down and realize you wrote it 2 years ago late at night when you had the flu.
 
  

    + =

You can almost always refactor your code to make it more streamlined, readable and efficient.  But not everyone has the time, or makes time to do so.
The important message here is to "Just fix it " but be carefull there could be good reasons for the decisions made to code this solutiuon in a particular way.

More to come...


Categories: C# | LINQ | SQL Server | XNA
Posted by Admin on Tuesday, April 29, 2008 3:10 AM
Permalink | Comments (0) | Post RSSRSS comment feed

Over Engineering Software Design

Need more cow bells ?

 Over engineering your software application is when you attempt to make it so flexible or scalable that you lose focus on returning business value. Often you can get swept up in programming and designing just for the sake of doing so.  It’s so tempting to use that “New” technology to tackle any problem that comes your way with a cool design pattern or “the tool of the month”.  Some programmers attempt to make their software very flexible and sophisticated because they believe they know their system’s future requirements.  In there programmer minds they reason that it's best to make a design more flexible or sophisticated, so it can accommodate the needs of tomorrow. This is perfect if you have a crystal ball or are psychic.  Ok you may be saying…”Yeah but based on my experience, I believe I have a handle on this business domain enough to predict the future of this software development.”


Ok, but what if you're wrong ?... If your predictions are wrong, you waste precious time, resources and money.  Then you and your team will spend days or even weeks tweaking an overly complex “flexible” piece of code.  This is time you could have spent writing the new logic exactly the way it should be to provide business value.

 

Except for the guys that work at a R&D software think-tank most of us have a business need that drives our software development, which in turn drives our paychecks.

To turn your back on business value is to bite the hand that feeds you.

 

 


Tags:
Categories: C# | LINQ
Posted by Admin on Monday, April 28, 2008 9:25 AM
Permalink | Comments (0) | Post RSSRSS comment feed

LINQ with Transactions

 This is a simple example of how to wrap your LINQ db.DataContext SubmitChanges() in a Transaction.

This is much like using transaction in SQL Server.

I used a simple add function to outline the pattern to use when wrapping your LINQ commits in transactions.

*Add a ref to System.Transactions;

 

 

  
  
New LINQ the home verion. now you and your friends can play "Map that Relational Object" on a Friday Night !!!

* Some assembily required.

   (database not included)

 

 

  using System.Transactions;


Categories: C# | LINQ
Posted by Admin on Thursday, April 17, 2008 9:30 AM
Permalink | Comments (0) | Post RSSRSS comment feed
Free Hit Counters
page counter