Why project structure matters in Arduino - Performance Analysis

Time Complexity: Why project structure matters

O(n)

Understanding Time Complexity

When working on Arduino projects, how you organize your code affects how quickly you can find and change things.

We want to see how the structure of a project impacts the time it takes to work with the code as it grows.

Scenario Under Consideration

Analyze the time complexity of accessing functions in different project structures.

// Example: Two ways to organize code

// Single file approach
void loop() {
  for (int i = 0; i < 100; i++) {
    doTask(i);
  }
}

void doTask(int x) {
  // Some task
}

// Multi-file approach (simplified)
// main.ino calls functions from other files
    

This shows a simple loop calling a function, either all in one file or split across files.

Identify Repeating Operations

Look at what repeats when the project grows.

• Primary operation: Calling functions inside a loop.
• How many times: The loop runs 100 times, calling the function each time.

How Execution Grows With Input

As the project grows, finding and using functions can take more time if the structure is messy.

Input Size (n)	Approx. Operations
10	10 function calls
100	100 function calls
1000	1000 function calls

Pattern observation: The number of function calls grows linearly with input size, but project structure affects how fast you can manage these calls.

Final Time Complexity

Time Complexity: O(n)

This means the time to run the loop grows directly with the number of iterations, but a good project structure helps keep your work efficient as code grows.

Common Mistake

[X] Wrong: "Project structure does not affect how fast the code runs."

[OK] Correct: While the processor runs code at the same speed, a poor structure makes it harder and slower for you to find, fix, or add code, which affects your overall speed working on the project.

Interview Connect

Understanding how project structure impacts your work speed shows you think about code beyond just running it. This skill helps you write clear, maintainable projects that others can easily understand and build on.

Self-Check

"What if we split the project into many small files instead of one big file? How would that affect the time it takes to manage the code?"

Practice

1. Why is it important to organize your Arduino project files into folders?

easy

A. It helps you find and fix code faster.

B. It makes the code run faster on the Arduino board.

C. It reduces the size of the Arduino program.

D. It automatically fixes errors in the code.

Solution

1. Step 1: Understand project organization benefits

   Organizing files into folders groups related code parts, making them easier to find.

2. Step 2: Connect organization to faster fixing

   When code is easy to find, you can fix bugs or add features faster.

3. Final Answer:

   It helps you find and fix code faster. -> Option A

4. Quick Check:

   Good structure = faster work [OK]

Hint: Folders group code logically to speed up work [OK]

Common Mistakes:

• Thinking organization speeds up code execution
• Believing folders reduce program size
• Assuming folders fix code errors automatically

2. Which of the following is the correct way to include a separate file in an Arduino project?

easy

A. import myFunctions.h

B. #include "myFunctions.h"

C. use myFunctions.h

D. require myFunctions.h

Solution

1. Step 1: Recall Arduino file inclusion syntax

   Arduino uses C/C++ style includes with #include and quotes for local files.

2. Step 2: Match correct syntax

   #include "myFunctions.h" is the correct way to include a header file in Arduino.

3. Final Answer:

   #include "myFunctions.h" -> Option B

4. Quick Check:

   #include "file" = correct Arduino include [OK]

Hint: Use #include "filename" for Arduino files [OK]

Common Mistakes:

• Using import instead of #include
• Using require or use which are not Arduino syntax
• Forgetting quotes around the filename

3. Given this Arduino project structure:

Project/
  main.ino
  sensors/
    tempSensor.h
    tempSensor.cpp
  utils/
    helpers.h
    helpers.cpp

Which file should you include in main.ino to use temperature sensor functions?

medium

A. #include "main.ino"

B. #include "tempSensor.cpp"

C. #include "utils/helpers.h"

D. #include "sensors/tempSensor.h"

Solution

1. Step 1: Identify header file for temperature sensor

   Header files (.h) declare functions; tempSensor.h is in sensors/ folder.

2. Step 2: Include correct relative path

   Use #include "sensors/tempSensor.h" to access sensor functions in main.ino.

3. Final Answer:

   #include "sensors/tempSensor.h" -> Option D

4. Quick Check:

   Include header file with correct folder path [OK]

Hint: Include header (.h) files with folder path [OK]

Common Mistakes:

• Including .cpp files directly
• Including unrelated helper files
• Including the main .ino file itself

4. You have this folder structure:

Project/
  main.ino
  motor/
    motorControl.h
    motorControl.cpp

But your code in main.ino gives an error: undefined reference to 'startMotor()'. What is the likely cause?

medium

A. You forgot to include motorControl.h in main.ino.

B. You included motorControl.cpp instead of motorControl.h.

C. You did not add motorControl.cpp to the project files to compile.

D. You named the folder motor instead of motors.

Solution

1. Step 1: Understand undefined reference error

   This error means the function is declared but its code is missing during linking.

2. Step 2: Check project compilation files

   Including header only declares functions; the .cpp file must be compiled and linked.

3. Final Answer:

   You did not add motorControl.cpp to the project files to compile. -> Option C

4. Quick Check:

   Missing .cpp in compile = undefined reference [OK]

Hint: Add all .cpp files to compile to avoid undefined errors [OK]

Common Mistakes:

• Only including header but not compiling .cpp
• Including .cpp file instead of header
• Thinking folder name causes linking errors

5. You want to share your Arduino project with a friend. Which project structure practice helps your friend understand and improve your code easily?

hard

A. Organize code into folders by function and include clear comments.

B. Use random file names and place files in different folders without order.

C. Put all code in one large .ino file without folders.

D. Only share compiled binary files, not source code.

Solution

1. Step 1: Identify good sharing practices

   Organizing code by function and adding comments makes it easier to read and improve.

2. Step 2: Compare options

   One large file or random names confuse readers; compiled files hide code.

3. Final Answer:

   Organize code into folders by function and include clear comments. -> Option A

4. Quick Check:

   Good structure + comments = easy sharing [OK]

Hint: Use folders and comments for easy sharing [OK]

Common Mistakes:

• Thinking one big file is easier to share
• Ignoring file naming and folder order
• Sharing only compiled files hides code