Here goes a small article on the essence of DDD. Being short - dive into the domain, be a part of it. Do not mess with implementation details, think higher. Understand the domain as much as you can.
Subscribe to:
Post Comments (Atom)
skip to main |
skip to sidebar
Twitter
About Me
Blog Archive
-
▼
2008
(158)
-
▼
December
(30)
- NAnt HowTo #2: How To Split Your Build File
- NAnt HowTo #1: How To Compile A Project?
- NAnt HowTos
- Things to complete
- How to become a better specialist?
- Sharp Architecture
- ASP.NET Form Autocompletion
- Two wonderful articles on using NHibernate with AS...
- Google Backstabs Microsoft
- Internet Explorer 8 Release Candidate 1
- Leaves Bugs System
- Web Developer Wish List
- IE 8 coming soon!
- New Live Writer
- Chrome vs IE 8 Beta
- Ruby-based barmen DSL
- Some interesting links
- Best text editor for Windows I've ever seen
- Ruby is FAST!
- The power of shell
- Calling .NET libraries from IronRuby
- John Lam Talk on PDC
- Python 3 released
- Running IRake
- IRake works!!!
- Upcoming Add-on-Con at Mountain View
- Fowler on Rake
- Python 3.0 rc3
- Microsoft Natural Ergonomic Keyboard 4000
- Domain Driven Design in the essence
-
▼
December
(30)
1 comment:
Included files become a piece of main build file and share all properties with it. This means that properties from included file are visible in main file and vise-versa. I usually place commonly used properties to separate .include files, for example, I have projects.include file with all properties that point to project names and folders.
gta 5 apk
Post a Comment