Skip to content

Working in Your Course IDE

Jump to bottom
mike-snhu edited this page Aug 15, 2026 · 1 revision

Working in Your Course IDE

An integrated development environment (IDE) brings together tools used to create software.

In IT 140, you use Visual Studio Code (VS Code) as the main editor and interface for your course development environment.

This page is a reference, not a setup guide. You should already have completed the Module One Setup Tasks before beginning the Module Two Assignment.

If your course IDE is not configured or verified, return to:

https://github.com/GC-STEM/it140-m1-setup-tasks

The IT 140 Course IDE

The course IDE includes more than the VS Code window.

Your configured environment includes tools used for activities such as:

  • Editing Python and Markdown files
  • Running Python
  • Using Git
  • Connecting to GitHub
  • Viewing diagrams
  • Checking code and spelling
  • Running course tests and commands

The Codio Virtual Desktop (CVD) is the reference environment for IT 140. You may also use a supported local environment configured through the Module One Setup Tasks.

For course-wide information about the IDE, see:

https://github.com/GC-STEM/it140/wiki/Course-IDE-and-Tools

Open the Assignment as a Folder

When working on Module Two, open your cloned:

it140-m2-assignment

folder in VS Code.

The repository should appear as the top-level folder in the Explorer.

This matters because the assignment uses a project structure containing related files in Part-A, Part-B, and their subfolders.

Top-level assignment instructions:

https://github.com/GC-STEM/it140-m2-assignment

Explorer

The Explorer displays the files and folders in your open workspace.

You can use it to move among:

  • README files
  • The SDW
  • SRS and SDD files
  • Flowchart and pseudocode
  • Python source code
  • Test files
  • The Part B reflection

The Explorer helps you see that a software project can contain much more than one .py file.

File Paths Matter

Two files can have the same name in different folders.

For example, this repository contains several README.md files. Each README explains the folder it is stored in.

When instructions give a path such as:

Part-A/src/name_age.py

follow the complete path rather than searching only for name_age.py.

Editor

The Editor is the main area where you read and modify files.

VS Code changes what it displays based on the file type.

For example:

  • .py files are treated as Python source code.
  • .md files are Markdown text.
  • .drawio files can open as diagrams when the course extension is available.
  • .pseudo files contain the assignment's pseudocode.

Part B asks you to notice IDE features that helped while you worked. The Editor is a good place to begin observing those features.

Markdown Preview

README files, the SDW, SRS, SDD, and the Part B reflection use Markdown.

Markdown is plain text that can be displayed as formatted headings, lists, links, code, tables, and other document elements.

The repository files include a reminder to open Markdown files in Preview when you want the clean formatted view.

Preview is useful because you can:

  • Read headings and lists more easily
  • Follow links
  • View formatted code blocks
  • See how your Part B reflection will render

For general Markdown help:

https://github.com/GC-STEM/it140-m1-setup-tasks/wiki/Explore-Your-Course-IDE

Microsoft VS Code Markdown documentation:

https://code.visualstudio.com/docs/languages/markdown

Side-by-Side Work

VS Code can display more than one editor at a time.

For Module Two, side-by-side views can help you compare related information, such as:

  • SRS and SDW
  • SDD and flowchart
  • Pseudocode and name_age.py
  • Part B instructions and ide_features.md
  • Markdown source and Markdown Preview

This can reduce repeated switching between files while you work.

Integrated Terminal

The integrated terminal lets you run command-line tools without leaving VS Code.

The assignment uses it for tasks such as:

  • Checking GitHub authentication
  • Creating and cloning your personal repository
  • Running Git commands
  • Running Python
  • Optionally running the provided automated tests

Open it from:

Terminal → New Terminal

The terminal is still a command-line environment. The exact shell can differ by operating system.

Follow the command block for your platform when the assignment provides separate commands.

Running a Python Program

During Construct and Test, you will run:

Part-A/src/name_age.py

Use the method identified by the assignment instructions and your configured course IDE.

When the program runs, pay attention to three things:

  1. Input — what the program asks you to enter.
  2. Processing — what the program does with the data.
  3. Output — what the program displays.

If Python reports an error, read the error message before changing code. See Testing and Debugging for help interpreting common situations.

Syntax Highlighting

Syntax highlighting displays different parts of source code using different visual formatting.

For example, the editor can visually distinguish Python language elements, strings, comments, and names.

Syntax highlighting does not prove that code is correct. It can make source code easier to scan and may help you notice something that looks different from nearby code.

If you discuss syntax highlighting in Part B, describe what you personally noticed and how it affected your work.

Code Completion and Suggestions

VS Code and installed language support can offer possible completions while you type.

A suggestion can save typing or help you discover available names, but you are still responsible for deciding whether the suggestion matches the assignment requirements.

Do not assume a suggested line is correct merely because the IDE offered it.

If you accept an outside or AI-assisted code suggestion that contributes to your work, follow the assignment's source and acknowledgement requirements.

See Sources, Citations, and AI Use.

Error Indicators and the Problems Panel

The editor can identify some problems before or while you run the program.

You may see indicators such as:

  • Underlines
  • Warning or error markers
  • Messages in the Problems panel

These are development aids. They do not replace running and testing your program.

A program can have no visible editor warning and still produce the wrong result.

Likewise, an editor warning may need to be interpreted in context before you change anything.

Indentation Guides

Python uses indentation as part of its syntax.

VS Code can visually show indentation levels, which can help you see whether lines are aligned with nearby code.

The Module Two starter file already provides the structure and indentation for code inside main().

Follow the Construct instructions carefully and keep replacement code at the required indentation level.

Draw.io Integration

The Design phase includes:

Part-A/design/name_age.drawio

The course IDE includes Draw.io support so the diagram can be viewed in VS Code.

This allows you to compare the flowchart with the SDD and pseudocode without needing a separate diagram application.

The flowchart is a provided reference file. Do not change it unless current assignment instructions tell you to do so.

Source Control

VS Code includes a Source Control view for Git repositories.

Git records versions of project files. The assignment README also provides terminal commands for committing and pushing your work.

You do not need to master every Source Control feature during Module Two.

The important distinction is:

Save updates a file on your current computer.
Commit records selected changes in the local Git repository.
Push sends committed changes to your GitHub repository.

See Git and GitHub During the Assignment.

IDE Features to Notice During Part A

Part B asks you to identify three IDE features that helped make programming easier or more effective.

During Part A, notice features that help you:

  • Navigate files
  • Read technical documents
  • Understand code
  • Write code
  • Maintain indentation
  • Find errors or warnings
  • Run the program
  • Run commands
  • View diagrams
  • Test or debug
  • Organize project work

The Part B README gives the required reflection instructions:

https://github.com/GC-STEM/it140-m2-assignment/blob/main/Part-B/README.md

If you are unsure of the official name of a VS Code feature, use Microsoft's documentation:

Use the documentation to confirm terminology. Your reflection should still describe your own experience.

If the IDE Is Not Working

First identify whether the problem is:

  • A Module Two assignment problem
  • A Git or GitHub problem
  • A Python program problem
  • A course IDE setup/configuration problem

For setup or configuration problems, return to the Module One support page:

https://github.com/GC-STEM/it140-m1-setup-tasks/wiki/Setup-Problems-and-Support

For assignment-specific troubleshooting, see Assignment Problems and Support.

IT 140 Module Two Assignment

Assignment Links

Help and Course Resources

Clone this wiki locally