Skip to content

translated #17

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sabzparto wants to merge 2 commits into
base: master
Choose a base branch
from
Open

translated #17

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2eb7e8f
Update 8_Boundaries.md
sabzparto Mar 16, 2021
6bfd05d
;)
Mar 18, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added .DS_Store
View file
Open in desktop
Binary file not shown.
10 changes: 8 additions & 2 deletions 8_Boundaries/8_Boundaries.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,8 +105,14 @@ Third-party code helps us get more functionality delivered in less time. Where d
when we want to utilize some third-party package? It’s not our job to test the third-party
code, but it may be in our best interest to write tests for the third-party code we use.
Suppose it is not clear how to use our third-party library. We might spend a day or two
(or more) reading the documentation and deciding how we are going to use it. Then we
might write our code to use the third-party code and see whether it does what we think. We
(or more) reading the documentation and deciding how we are going to use it.


وظیفه ما تست کردن کدهای اماده نیست اما ممکن است نوشتن تست کد برای کدهای اماده ای که استفاده میکنیم به نفع ما باشد.
فرض کنید نحوه استفاده از کتابخانه اماده واضح نیست و ممکن یک یا دو(یا بیشتر) روز صرف خواندن داکیومنت ها و یادگیری نحوه استفاده از کتابخانه شود.


Then we might write our code to use the third-party code and see whether it does what we think. We
would not be surprised to find ourselves bogged down in long debugging sessions trying to
figure out whether the bugs we are experiencing are in our code or theirs.
Learning the third-party code is hard. Integrating the third-party code is hard too.
Expand Down