PRACTICAL GUIDE / 01
From Jamto your ownproject.
How to build, review and publish code on PITMA.
Watching a Jam, PITMA’s video lesson, is the first step. Next, try the idea in your own code.
On PITMA you can start a project from a Jam, write and run Python in Google Colab, get a review from another member and add the finished work to your portfolio. This guide takes you through each step.
Your route: choose a Jam → create a project → write and test your code → submit it for review → address feedback → merge → optionally publish to GitHub.
Choose a Jam and an idea to try
Open Jams and pick a topic you want to put into practice. Watch the lesson and look through its examples and materials.
Choose a specific result you can test. Plot your own data, implement an algorithm from the lesson or see how a model behaves when you change a parameter.
Once you have an idea, select Create a project on the Jam.
JamsProjectsCommunityLEARNING EXAMPLEFunctions
Turn repeated code into functions. Explore parameters, return values and how to break down a problem.
Create the project
Enter a project name that describes the result. “Monthly sales visualization” and “Text classification with sklearn” are both examples.
Check the linked Jam and its task, then select Create project.
Only you can see your project until you open a pull request. Once you submit a solution, other members can review the code.
If you already have a project for this Jam, PITMA opens the existing one.
JamsProjectsCommunityLEARNING EXAMPLECreate a project
Turn a Jam into a project with your own code, one pull request and community feedback in one place.
Python for data science
You can find the linked task in your project workspace.
Only you can see this project until you open a pull request.
Create projectFind your way around the workspace
Your project has several tabs:
- Task and code is where you implement and explain your solution.
- Pull request contains the discussion, changes and reviewers’ decisions.
- Materials contains resources for the project.
- Discussion lets you ask questions and exchange ideas about the project once you’ve submitted it for review.
Use Jam and materials to return to the lesson.
JamsProjectsCommunityLEARNING EXAMPLEMonthly sales visualization
Jam and materials
Your implementation
Prepare the code, check the output and explain your solution.
import matplotlib.pyplot as plt
months = ["Jan", "Feb", "Mar", "Apr", "May"]
sales = [12, 18, 15, 28, 36]
plt.plot(months, sales, marker="o")
plt.title("Monthly sales")
plt.show()Write and run the code
The Task and code tab offers two ways to work.
In Google Colab
Colab lets you write and run Python in your browser, use libraries and inspect plots and calculation results.
- Open the Google Colab tab.
- The first time, select Connect Google Drive and authorize the connection with Google.
- Select Open in Colab.
- Add code to the notebook, run the cells and check the output.
The first time you open Colab, PITMA creates a notebook in your Google Drive using your current project code. Subsequent visits open that same notebook.
In the PITMA editor
Choose Python editor to edit your implementation directly in PITMA. The platform checks Python syntax on submission. To test how the algorithm behaves and what it returns, run the code in Colab or on your computer.
JamsProjectsCommunityLEARNING EXAMPLEMonthly sales visualization
Jam and materials
Your notebook in the browser.
Write code, run cells and check the output.
PITMA ↔ GOOGLE COLABBring the results back from Colab
When your code is ready:
- Run the relevant Colab cells and check the output.
- Save with Ctrl+S / Cmd+S and wait for saving to finish.
- Return to your PITMA project.
- Select the circular arrows. The tooltip reads Sync.
- Check the imported code and outputs.
PITMA imports the saved version of the notebook. If you edit the notebook again, save it and select Sync again.
The reviewer sees your imported code, explanations and supported outputs, including text and plots, directly in PITMA. Interactive widgets and some other output formats may be missing.
Before submitting, check both your code and its outputs for passwords, API keys and private data.
JamsProjectsCommunityLEARNING EXAMPLEMonthly sales visualization
Jam and materials
Version imported. Review the code and outputs before submitting.
import matplotlib.pyplot as plt
months = ["Jan", "Feb", "Mar", "Apr", "May"]
sales = [12, 18, 15, 28, 36]
plt.plot(months, sales, marker="o")
plt.title("Monthly sales")
plt.show()Explain the solution and submit it
In What I changed, explain:
- Which idea from the Jam you implemented.
- How the solution works.
- Which examples you tested.
- What happened and what limitations you found.
For example:
I wrote a function that plots monthly sales. It takes lists of months and sales figures, checks that the lists have the same length and plots the result. I tested ordinary values, zeros and an empty list.
Select Submit for review. PITMA checks Python syntax. If it reports an error, fix it and submit again. When the check passes, PITMA opens a pull request and adds your work to the community review queue.
A pull request (PR) is a version of your solution that you want someone to review before you finish the project. Checks passed confirms that the automatic check succeeded. The reviewer still needs to check the solution itself.
JamsProjectsCommunityLEARNING EXAMPLEMonthly sales visualization
Jam and materials
import matplotlib.pyplot as plt
months = ["Jan", "Feb", "Mar", "Apr", "May"]
sales = [12, 18, 15, 28, 36]
plt.plot(months, sales, marker="o")
plt.title("Monthly sales")
plt.show()Work through the review
Open Pull request to read the discussion and inspect the diff in Files changed. If you used Colab, open Notebook to see the saved version.
A reviewer can examine your code in PITMA or run their own copy of the notebook in Colab. There are two possible decisions:
- Approve means the reviewer accepts the current version.
- Request changes means the reviewer explains what to fix.
When you receive a change request:
- Read the feedback and ask for clarification in the PR discussion if needed.
- Return to Task and code.
- Make the change. If you use Colab, save the notebook and sync it back to PITMA.
- Update your explanation to describe the change.
- Select Submit for review again.
The PR now contains a new version. Previous decisions stay in the history, and the new version needs a fresh review. While a version is waiting for its first review, resubmission is unavailable. You can submit another version after a request for changes.
JamsProjectsCommunityLEARNING EXAMPLEMonthly sales visualization
Jam and materials
Sales chart #a12b34
Open Author proposes changes sales · v1 → main
Saved version v1I added a plotting function and an example of how to use it.
Reviewer · Requested changes · v1Check what happens when the months and sales lists have different lengths. Validate them before plotting.
Checks passed
Merge the project
The current version needs:
- A successful syntax check.
- At least one approval.
- No outstanding requests for changes on that version.
When all three conditions are met, the author can select Merge pull request. This accepts the reviewed implementation as the finished version. Its status becomes Merged, and the project appears in Community implementations and in your PITBOOK.
The project retains its discussions and review history.
JamsProjectsCommunityLEARNING EXAMPLEMonthly sales visualization
Jam and materials
Sales chart #a12b34
Open Author proposes changes sales · v2 → main
Saved version v2I added a length check and handled empty inputs.
Reviewer · Approved · v2I checked ordinary data, an empty list and lists of different lengths. All three behaved as expected.
Checks passed
Publish the accepted code on GitHub
After merging, select Publish to GitHub.
- Enter a repository name.
- Add a description if you like.
- Choose Public or Private visibility.
- Connect GitHub and grant the requested permission if prompted.
- Select Create repository.
PITMA exports the merged Python code as a .py file, alongside a README and a dependencies file. Projects written in Colab are also exported as Python source. Later GitHub edits do not sync back to PITMA.
Publishing to GitHub is optional. Your finished implementation is already available on the platform.
JamsProjectsCommunityLEARNING EXAMPLEYour code.
Your GitHub.
Publish the approved implementation, README and dependencies to your own repository.
sales.py
README.md
requirements.txtChoose Private to create a private repository.
Create repositoryThis exports the merged version. Later changes on GitHub do not sync back to PITMA.
Review someone else’s project
Open Projects → Needs review and pick a project on a subject you know. If this is your first review, select Become a reviewer and answer three short questions. Once you pass, you can claim a PR.
Select Take for review in another member’s open PR. Check:
- Does the code implement the stated idea?
- Does it handle ordinary inputs and edge cases?
- Are the names, structure and explanation clear?
- Do the displayed results match the implementation?
For notebooks, select Run my own copy. PITMA prompts you to connect Google Drive if necessary.
Choose Approve or Request changes, write specific feedback and select Submit review. For example: “I ran the Jam example and tried an empty list. The output was correct and the error message was clear.” If you found a problem, include an input that reproduces it.
Another member must review your own project. You cannot approve it yourself.
JamsProjectsCommunityLEARNING EXAMPLESales chart #a12b34
Open Another member’s project · version v2
Check the task requirements, edge cases, readability and the author’s explanation.
Start with one small implementation. Choose a Jam, try the idea on your own example and submit it for review. Each finished project in your PITBOOK shows readers your code, how you approach a problem and how you use feedback.