summaryrefslogtreecommitdiff
path: root/tutorials/module_2/problem_solving_strategies.md
diff options
context:
space:
mode:
authorChristian Kolset <christian.kolset@gmail.com>2025-08-29 12:41:42 -0600
committerChristian Kolset <christian.kolset@gmail.com>2025-08-29 12:41:42 -0600
commit29870f542da6f1ec4dd028a4255143b638f48ba8 (patch)
treed9d904adcbc9c43f14c73102d126aab0ca1a6c70 /tutorials/module_2/problem_solving_strategies.md
parent187d17f16c90a4e2dfc49e280445e027b53ec86c (diff)
Updated canvas to actually refer to the notes in the vault.
This results in the label creation at the top header to reference when showing the block.
Diffstat (limited to 'tutorials/module_2/problem_solving_strategies.md')
-rw-r--r--tutorials/module_2/problem_solving_strategies.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/tutorials/module_2/problem_solving_strategies.md b/tutorials/module_2/problem_solving_strategies.md
index 0767c73..4fa20e9 100644
--- a/tutorials/module_2/problem_solving_strategies.md
+++ b/tutorials/module_2/problem_solving_strategies.md
@@ -1,5 +1,7 @@
# Algorithmic thinking
+^da584e
+
In engineering, solving a problem begins long before we start coding or building models. Like any other engineering challenge, computational problems must first be clearly framed and understood. In this section, you will learn to **apply algorithmic thinking** to systematically approach engineering problems, **translate real-world situations into structured programming logic**, and **use computational tools to implement, test, and refine solutions**.
Before diving into code, it's crucial to define the problem carefully, frame the problem so that logically so that a computer can understand then execute so that