Even if you find the right tool for your job, do you know how to use the tool correctly?
This is exactly what this article is going to focus on; you need to know your tools in order for you to know it’s the right tool for this job!
All too often I see developers using amazing new tools but in many cases not knowing the limits or how to use it correctly. It’s very important to understand how to use a tool and what the implications of using a tool in a certain way has. When I find a new tool or a new library that I want to use, I try to research it and understand it before I recommend it for production use.
To me a tool is not only a software that I run or a hammer that I use, but I also consider a third party library a tool. A tool for me is something that I use to solve a certain problem and smaller parts can build a larger tool.
If you don’t know what your tool does behind the scenes you can get very big problems in the end. If you try to use a hammer to screw something into the wall there might be an easy work around just to hammer the screw into the wall. But what if it was the other way around?
var persons = from person
in
db.Persons
where person.Name.Contains(
"Filip"
)
select person;
var persons = db.Persons.Where(person => person.Name.Contains(
);
SELECT
*
FROM
Persons
WHERE
Name
LIKE
'%Filip%'
;
db.Persons.ToList().
Where
(person => person.
.StartsWith(
).ToList();