From 2eb7e8f5a96bf217344de88ccc7b587892820fa3 Mon Sep 17 00:00:00 2001
From: sabzparto <79199073+sabzparto@users.noreply.github.com>
Date: Tue, 16 Mar 2021 21:59:39 +0330
Subject: [PATCH 1/2] Update 8_Boundaries.md

---
 8_Boundaries/8_Boundaries.md | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/8_Boundaries/8_Boundaries.md b/8_Boundaries/8_Boundaries.md
index 3fb1558..207636a 100644
--- a/8_Boundaries/8_Boundaries.md
+++ b/8_Boundaries/8_Boundaries.md
@@ -105,8 +105,12 @@ 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.

From 6bfd05d54034a89b25d55978972c7e1399fc2aa9 Mon Sep 17 00:00:00 2001
From: MacBook <macbook@MacBooks-MacBook.local>
Date: Thu, 18 Mar 2021 14:28:23 +0330
Subject: [PATCH 2/2] ;)

---
 .DS_Store                    | Bin 0 -> 6148 bytes
 8_Boundaries/8_Boundaries.md |   4 +++-
 2 files changed, 3 insertions(+), 1 deletion(-)
 create mode 100644 .DS_Store

diff --git a/.DS_Store b/.DS_Store
new file mode 100644
index 0000000000000000000000000000000000000000..21872fdc3494e4544c4f829d04ceed0dda0be9ff
GIT binary patch
literal 6148
zcmeHKQBK1!47FiMmEdC%KYZp2``aH`RZg%209_Fvb!6JK|6YkRa03p&9k>C{u|X@8
zN&Fy$Y$<t;W4p<dn#4rJ<+hm+jftp06J${aM9hOz2j+YP<eXzm57f{#t?7Os(O)#l
z+D~XomsC=s-Sywlrr9joI;9qy``)R&oy-?$xzgQDpZEDLQ&rV%s^L?-oSwfv^3!a;
zfAb^%)!pt|B2v3J1I~am;0!nepBa#A4N@E{dhZN41J1w)19CnDG{I=tDdwXCT`mED
zBbc*5ms&z%f?+i56fpx~4Fzf_TZzFM4tp@aXxJ%gII$HUY+rsaUO0ap`9pRmj*8wp
z1I|F7fkPdR<^I3GFEd!=_d|T-3^)V-i~$~1^Qy$A>~8(CJ-KTG+7+6J_;sQ{p!XgD
i7|1ztmM3*Shz`GK*eOaDvFC80KLj!%-Z=xmz`z^Aggn{+

literal 0
HcmV?d00001

diff --git a/8_Boundaries/8_Boundaries.md b/8_Boundaries/8_Boundaries.md
index 207636a..60dd845 100644
--- a/8_Boundaries/8_Boundaries.md
+++ b/8_Boundaries/8_Boundaries.md
@@ -107,8 +107,10 @@ code, but it may be in our best interest to write tests for the third-party code
 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
 would not be surprised to find ourselves bogged down in long debugging sessions trying to