Coder, writer, nonconformist 🤘
Ex-SWE @ Facebook 🤩
Sharing experience and notes on building a career, sharpening coding skills and creating great things 🏆
Thanks for your response and a perfect example Jakob!
I'm not familiar with C#/LINQ but as far as I understand it's a tool that hides the complexity of DB/XML searching behind a slick interface. As we can see from your example, there's another point to be considered especially when it comes to junior developers. Declarative tools can unintentionally hide computational complexity - and provide small to no signs of that something goes wrong.
It is true that there are LINQ providers for databases and for XML. But LINQ also provides a funtional interface for any type of collections, in the same way as you see reduce, map, and filter in other languages.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for your response and a perfect example Jakob!
I'm not familiar with C#/LINQ but as far as I understand it's a tool that hides the complexity of DB/XML searching behind a slick interface. As we can see from your example, there's another point to be considered especially when it comes to junior developers. Declarative tools can unintentionally hide computational complexity - and provide small to no signs of that something goes wrong.
Thank you for your reply, Oleg.
It is true that there are LINQ providers for databases and for XML. But LINQ also provides a funtional interface for any type of collections, in the same way as you see reduce, map, and filter in other languages.