|
What, no second hint?
"I had the right to remain silent, but I didn't have the ability!"
Ron White, Comedian
|
|
|
|
|
The rules say four hours!
(There's a copy at the bottom of my profile page)
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
|
Pure coincidence, I assure you: I have no idea even with your second hint!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Great video on keeping your solutions simple and NOT using anything with the word "Repository" in it. I also found some of his illustrations, both verbal and visual, quite funny.
https://www.youtube.com/watch?v=0tlMTJDKiug[^]
|
|
|
|
|
I'm writing repositories right now, but they are simple facades that define the interface of our data access layer, nothing more.
Often enough the real horrors begin when a class name contains 'Manager' or 'Helper', but I guess 'Repository' is often enough in this fashion as well.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
You should watch the video. I have always been against most use of patterns and abstraction, so I like what I hear. You may not agree, I don't know. 
|
|
|
|
|
Sorry, no time right now. The boss wants me to do some work.
I have nothing against having layers. Separation of concerns (as way as strengthening the single responsibility principle) in each layer has proven to be very helpful to keep things tidy.
In the past I have seen bad examples of overdesign (using every pattern known to man at least twice and adding every available framework for and against everything) or total anarchy (the usual spaghetti mess).
I don't know which of the two I dislike more. Why can so many people not go the straightest way towards their goal?
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
Now imagine a 2013Helper, a 2014Helper and a 2015Helper class.
Static classes ofcourse, no inheritance 
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
|
I read his blog from time to time. I see he has been a member for over 10 years with little activity though.
|
|
|
|
|
The man is busy...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
I'm busy working on a WPF MVVM project now where the developer liked to use patterns, lots of abstraction and base classes etc. A few too many layers in some cases. Like an onion that makes you want to cry.
|
|
|
|
|
Summarize the video...
What's wrong with repositories?
If it's not broken, fix it until it is
|
|
|
|
|
Kevin Marois wrote: What's wrong with repositories?
You don't really need them. They really serve no purpose unless you want to complicate your application at some level. There are engineers who love to abstract upon abstract, and then there are those of us, who don't.
I have been to both worlds, and have worked in both worlds, and care for the world with "less" abstraction.
Watch the video when you get a chance. I already summarized the video in my original post.
|
|
|
|
|
Sounds like you're confusing 'repositories' with 'factories'... When I hear repository, I think Data Access.
If it's not broken, fix it until it is
|
|
|
|
|
Entity Framework implements the repository pattern behind the scenes, and DbContext is its UoW. So why are you writing another layer of abstraction on top of it? BTW, I was talking about repositories and not facades. 
You can always add a simple layer on top of Entity Framework, if needed.
|
|
|
|
|
Emilio Largo wrote: You can always add a simple layer on top of Entity Framework, if needed.
Yes, stick in your DAL.
|
|
|
|
|
I agree. Repository definition: a place, building, or receptacle where things are or may be stored.
|
|
|
|
|
I believe the best way to do it is the way you are most comfortable doing!
New version: WinHeist Version 2.1.1 new web site.
I know the voices in my head are not real but damn they come up with some good ideas!
|
|
|
|
|
We got a "weird and wonderfull" section devoted to that idea 
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
I ought to go there more often as I'm both "weird and wonderful"? 
New version: WinHeist Version 2.1.1 new web site.
I know the voices in my head are not real but damn they come up with some good ideas!
|
|
|
|
|
Mike Hankey wrote: I ought to go there more often as I'm both "weird and wonderful".. and humble
FTFY
If it's not broken, fix it until it is
|
|
|
|
|
|
He didn't really have a concise or proper conclusion, I agree.
My take away was to keep your solutions simple (maintainable) and one key way to doing that is by implementing less abstraction, starting with this Repository Elephant-sh*t.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
