When should one choose IQueryable or IEnumerable?

Leonardo Aguiar — Mon, 11 Mar 2019 13:52:34 +0000

First of all: I am sorry for the lack of references in this discussion, I should have saved the links I went through.

Browsing over the WWW I found some interesting articles about those interfaces, and this subject got my atention because I realised that as a low experienced developer I tend to use only IEnumerable. But after reading through, first it seemed like only IQueryable should be used when querying on external sources of data, which makes sense as the Interface applies filters directly on the source instead of bringing all data to memory.

But then, I found this article that said IQueryable should not be used because it would break test-ability and a few other reasons. This got me lost in between both of the interfaces, not knowing which and when to use one them, of course I will research in more depth, but first I would like to hear this lovely community opnion.

So my fellow Dotnet fans, what are your thoughts on this?

what could a new developer write about?

Leonardo Aguiar — Wed, 16 Jan 2019 23:49:02 +0000

Hi, I just finished college and started a job as a fullstack developer working with .NET and AngularJS.
I have always wanted to write posts like we see around here because I think it's one of the coolest ways to express thoughts on tech and get people to discuss something and also because I have the desire to teach and give back to the community that helped me so much.

But what could I write about? One thing I think about sharing is how after 3 years of college I got a really nice internship and then a great job.

DEV Community: Leonardo Aguiar

When should one choose IQueryable or IEnumerable?

what could a new developer write about?