The Thursday Exchange 7:30 AM (GMT-7)[Phoenix]
Welcome to Our Collaborative Space
We gather weekly to share ideas, solve problems, and support one another in our learning and growth. This space is built on mutual respect and open communication.
Meeting Details:
- Day: Thursdays
- Time: 7:30 AM (GMT-7)[Phoenix]
Guidelines for Participation:
- Assume good intentions and respect each other's differences.
- Listen actively and with consideration.
- Use “Yes, and…” to build constructively on others' ideas.
- Be mindful of how much you speak—make space for others.
- Stay curious and open to learning from one another.
What to Expect
- Open, respectful discussion
- A space to ask questions or share progress
- Fresh perspectives and peer insight
- A no-pressure, low-barrier environment
- Support for your learning goals, projects, or roadblocks
Who It’s For
Anyone interested in technology, learning how things work, or building better systems—whether you’re just starting out or have years of experience.
Join Us
No commitment. Just show up, say hi, and see where the conversation takes you. Please follow the steps here.
Comments
-
Closing the week out
Articles I have enjoyed reading:
- How to Think Like a Computer Scientist
- https://en.wikibooks.org/wiki/Python_Programming
- https://docs.python.org/3/tutorial/index.html
When your code doesn’t work, don’t panic! Follow this step-by-step way of thinking:
1. Focus on What’s Actually Wrong
If something in a list or output is wrong or missing:
→ Look only at the incorrect part, not the whole list.
You don’t need to check every part—narrow your focus to what’s broken.
2. Ask: “How Could It Produce This Result?”
Start asking questions:
- What logic or data could lead to this output?
- What was the program trying to do?
3. Is This Part of a Pattern or Family of Problems?
Think bigger: maybe the problem isn’t just here, but happening in other places too.
<details> <summary>Examples of related issues to look for</summary>
- Aliasing – are two variables pointing to the same object by accident?
- Side Effects – is one part of the code changing something unexpectedly?
- List Mutation – is the list being changed somewhere without realizing it?
- Systematic Mistake – is the same kind of bug showing up throughout the program?
</details>
4. How Can You Fix It?
<details> <summary>Use the Scientific Method</summary>
- Study the available data
- What output are you getting?
- What should you be getting?
- Form a hypothesis
- Example: “I think this variable is getting overwritten too early.”
- Design a repeatable test
- Add print statements, write a test function, use the debugger.
- Make sure your test can fail—otherwise it doesn’t prove anything.
- Run the test and observe the results
- If your test passes, does it confirm your hypothesis?
- If it fails, does it refute your hypothesis?
</details>
5. Make Intermediate Results Useful
Don’t just print “It works” or “Fail”.
→ Print key variables, small steps, or summaries that help you understand what’s happening.
6. Know the Expected Result
Before testing:
→ Be clear about what you expect.
“I think the result should be 3 because...”
And those 6 steps will help us think through a problem set, how we approach and it and find solutions.
A closing thought:
What simple pleasures bring a smile to your face each day?
Howdy, Stranger!