Subscribe: Comments for Lazycoder
http://www.lazycoder.com/weblog/index.php/comments/feed/
Preview: Comments for Lazycoder

Comments for Lazycoder



May cause drowsiness



Last Build Date: Fri, 27 Feb 2015 10:34:00 +0000

 



Comment on ORMs are not just about replacing SQL by ptutt

Fri, 27 Feb 2015 10:34:00 +0000

I think the key issues are around rapid to build, easy to maintain, and performance. ORM's help with rapid build time and can both help and hinder maintenance. Stored procs can help optimise performance, giving more control over data access. I use both, EF for basic CRUD and a bit more, but when things get a bit more complicated at the SQL level I use SP's and views. There is no doubt, where multiple db actions are required as part of one process, an SP will improve performance by reducing the round trips to the database.



Comment on ORMs are not just about replacing SQL by Stuart Roberts

Tue, 24 Feb 2015 10:27:00 +0000

My reading of Robs post was that the middle path should be taken, where over reliance on the ORM is bad, but too much logic in the sp is also bad. I may be showing my bias though as I spend a lot of time in 2 different systems trying to get to that happy medium from both extremes right now.



Comment on GIFs from a developers life by Wing

Thu, 03 Oct 2013 09:18:00 +0000

haha, briljant



Comment on GIFs from a developers life by Peter Shaw

Wed, 14 Aug 2013 17:25:00 +0000

Erm yea.... we've all been there :-)



Comment on GIFs from a developers life by ReidEv275

Wed, 14 Aug 2013 17:05:35 +0000

@lazycoder too close to reality for me



Comment on GIFs from a developers life by bwahacker

Wed, 14 Aug 2013 16:59:13 +0000

@lazycoder that happens to me with very very new code, too :-)



Comment on Methods should include the state needed to execute them as parameters by Steve

Tue, 23 Jul 2013 16:43:00 +0000

If those properties need setting for the object methods to work, then what you should really be doing is ensuring that the _constructor_ includes the state needed. The object should not be in an inconsistent state after construction (or when it's been returned from the factory method that knows it has to invoke an initialization that can't be called at construction time e.g. involving virtual method calls, or has the potential to fail messily leaving a broken construct). Alternatively, if the state is all pushed in from the outside for every method, then make those methods static -- there's no meaningful private state left on the object for them to be looking at or writing to at that point, after all.



Comment on Methods should include the state needed to execute them as parameters by Dew Drop – July 23, 2013 (#1,590) | Alvin Ashcraft's Morning Dew

Tue, 23 Jul 2013 12:33:30 +0000

[...] Methods should include the state needed to execute them as parameters (Scott Koon) [...]



Comment on Methods should include the state needed to execute them as parameters by velvetflair

Tue, 23 Jul 2013 04:04:25 +0000

Methods should include the state needed to execute them as parameters http://t.co/7mvMTUOMzd



Comment on Methods should include the state needed to execute them as parameters by t0bit0bsen

Mon, 22 Jul 2013 17:13:04 +0000

@lazycoder the next one reading your post will adopt it, but make it all static :-/