---
title: "Comment by Saby on \"A Practical Guide to Higher Order Functions in C#\" | Hashnode"
description: "Nice article Sam! What i'd like to point out, in your repo pattern is that, for me at least, having different methods conveys the intention of the code bett"
url: "https://hashnode.com/posts/a-practical-guide-to-higher-order-functions-in-c/60e03e704f8e376422a7725e/comment/60e33ec5b1f6172d201b5338"
---

[Discussion](https://hashnode.com/posts/a-practical-guide-to-higher-order-functions-in-c/60e03e704f8e376422a7725e)

Comment [A Practical Guide to Higher Order Functions in C#](https://hashnode.com/posts/a-practical-guide-to-higher-order-functions-in-c/60e03e704f8e376422a7725e)

[Saby](https://hashnode.com/@Saby)

[Jul 5, 2021](https://hashnode.com/posts/a-practical-guide-to-higher-order-functions-in-c/60e03e704f8e376422a7725e/comment/60e33ec5b1f6172d201b5338)

Nice article Sam! What i'd like to point out, in your repo pattern is that, for me at least, having different methods conveys the intention of the code better than a generic filter. For example, with GetById, you just look for references of the method or search it to see where exactly is used. With a generic filter I think it would be harder to find, especially in big code bases, where it tries to bring a Product by Id and follow the logic of the code.