From effb536aa69a2fe01eaf6d559c6e2e88a4b1bd1c Mon Sep 17 00:00:00 2001
From: cprutean <cip.pruteanu@ed.ac.uk>
Date: Wed, 11 Sep 2024 10:17:25 +0100
Subject: [PATCH] Update file HowtoWriteaComputerProgramfromScratch.ipynb

---
 CourseNotes/HowtoWriteaComputerProgramfromScratch.ipynb | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/CourseNotes/HowtoWriteaComputerProgramfromScratch.ipynb b/CourseNotes/HowtoWriteaComputerProgramfromScratch.ipynb
index 36de0f2..766b0ec 100644
--- a/CourseNotes/HowtoWriteaComputerProgramfromScratch.ipynb
+++ b/CourseNotes/HowtoWriteaComputerProgramfromScratch.ipynb
@@ -399,7 +399,10 @@
     "\n",
     "In the final code example above, we made use of the fact that the program has a very rigid structure. This begins from the limited user choice, and the fact that each choice is independent of others, which can allow us to produce matching arrays that make use of anonymous functions to calculate the desired function and its derivative and plot the result. You will see more detailed examples of all the concepts used in this section as you advance through the course.\n",
     "\n",
-    "> Please note that the final code is significantly less human-friendly than the very first iteration we tried, and this is to be expected. **Programming is generally not a linear process**, and one never aims to write the final version of a code on the first try. It is best practice to adopt a trial and error approach (which most programmers do), where you interatively improve on the code, rather then hope to produce the final version from the first attempt. This practice also turns out to be significantly faster and more efficient than the alternatives."
+    "> Please note that the final code is significantly less human-friendly than the very first iteration we tried, and this is to be expected. **Programming is generally not a linear process**, and one never aims to write the final version of a code on the first try. It is best practice to adopt a trial and error approach (which most programmers do), where you interatively improve on the code, rather then hope to produce the final version from the first attempt. This practice also turns out to be significantly faster and more efficient than the alternatives.\n",
+    "\n",
+    "### Next steps\n",
+    "Once you have completed this checkpoint, please continue with the [Week4](../WeeklyTasks/Week4.ipynb) tasklist."
    ]
   },
   {
-- 
GitLab