Put the knife down and take a green herb, dude.
One feller's views on the state of everyday computer science & its application (and now, OTHER STUFF) who isn't rich enough to shell out for www.myfreakinfirst-andlast-name.com
Using 89% of the same design the blog had in 2001.
FOR ENTERTAINMENT PURPOSES ONLY!!!
Back-up your data and, when you bike, always wear white.
MarkUpDown is the best Markdown editor for professionals on Windows 10.
It includes two-pane live preview, in-app uploads to imgur for image hosting, and MultiMarkdown table support.
Features you won't find anywhere else include...
You've wasted more than $15 of your time looking for a great Markdown editor.
Stop looking. MarkUpDown is the app you're looking for.
|Tuesday, January 28, 2014|
When to use NHibernate | Jimmy Bogard's Blog:
But, if you draw your DDD bounded contexts well, you’ll find you need a lot less Big Bad Frameworks to get things done.
+1 This man's got it.
I'm adding a field to an insanely overly nested page in our .NET MVC system right now, and I'm having to edit, sheesh, I don't even know yet, maybe 8 files to expose it to our View? I've got five levels of ascx files, about the same level of DTOs on the data pull side, and another set of nested files to access the ViewModels based on those DTOs. So I'm bucket brigading the field through the DTOs and AutoMappers until it hits the equally well nested ViewModel hierarchy, then traveling down our only slightly less layered ascx/View model to support it.
Or I could have added one extra field in a SQL statement (which could easily be a sproc) returning a DataTable, and I'd've been done. I understand ORMs can be useful when preserving relationships programmatically, but is it worth the
Hyper-monolithic [sic] pulls to modular puts makes myfreakinname something something.
Don't mind if I do.
Edit: I'm not alone.
You give the ORM a query, it builds SQL out of it, then it constructs a DynamicMethod to materialize data coming back from SQL into your business objects. I am not privy to the exact implementation, it may be including more or less work in these dynamic methods.
Or this "article" from CodeProject, which also later talks about Saffron's Dapper.NET, which the above link eventually gets back around to.
Over the years, I've seen several object-relational-mappers (ORMs) come along for .NET and always ultimately end up being somewhat disappointed with the end result. I remember seeing a preview of LINQ-to-SQL being absolutely blown away by the speed and ease with which you could generate code which would manage the movement of data between your relational database and your business object model. And all without having to hand-roll any SQL! A little later, it was Entity Framework which, at the time at least, seemed to be like LINQ-to-SQL but even better!
I think I do this lamenting every three or four months. I'm sure I've blogged about it before. AAtF (Apologies After the Fact, natch).
posted by ruffin at 1/28/2014 06:10:00 PM
All posts can be accessed here:
Just the last year o' posts: