https://github.com/tafara-n/projects
These are my projects from the beginning of my journey as an SE.
https://github.com/tafara-n/projects
Last synced: 8 days ago
JSON representation
These are my projects from the beginning of my journey as an SE.
- Host: GitHub
- URL: https://github.com/tafara-n/projects
- Owner: Tafara-N
- Created: 2024-01-02T19:30:27.000Z (almost 2 years ago)
- Default Branch: main
- Last Pushed: 2024-11-23T11:09:47.000Z (11 months ago)
- Last Synced: 2025-04-12T13:57:46.732Z (6 months ago)
- Language: Python
- Size: 50.8 MB
- Stars: 4
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: Docs/README.md
Awesome Lists containing this project
README
# Approaching a Project
It can be difficult to know how to approach a project. You’ve read resources and tried some examples, and now it’s time to apply what you know. Where do you start? The following framework can help you focus how you approach a project.
Read the steps below and think about how you would follow them for a task.
- Read the task or challenge.
- Rephrase it in your own words.
- Verify expected behavior by getting example inputs and outputs.
- Whiteboard your solution with words.
- Walk through your solution with an example as if you were a machine. Do only what is written down. Correct your solution if needed.
- Whiteboard your solution with pseudocode.
- Walk through your solution with an example as if you were a machine. Do only what is written down. Correct your solution if needed.
- Whiteboard your solution with code.
- Walk through your solution with an example as if you were a machine. Do only what is written down. Correct your solution if needed.
- Write your code on your computer. [*Note: This is this first time you are using your computer! Only when you know **exactly** what to code.*]
- Test your code on your computer.
- Debug if necessary.
- You complete the task or challenge!
- Be sure to break your task or project into smaller and smaller pieces, until you are comfortable solving each piece with the above steps.
When you are in step 10, “Write your code on your computer”, you should code each piece one at a time and debug right after each small step to make sure everything works properly. This will also prevent you from having to debug multiple pieces at the same time and thus, will make your life much easier.
## Preserving your mental health & Conquering imposter syndrome
As you dive into this program, you are likely to have different kinds of days. These could be easy days where everything makes sense, hard days where you feel you like crushing your computer because for some reason you don’t understand why your code is working. Other days you just want to quit because it feels you can’t push through the program.
Irrespective of the days you have, always remember your mental health is key and important, just by getting started, you can do it and even when you think you can’t continue and you feel your peers are ahead of you, look at your journey and own.
# Resources
**Read or watch:**
- [what is imposter syndrome and how can we combat it](https://www.youtube.com/watch?v=ZQUxL4Jm1Lo)
- [Imposter syndrom is bravery](https://www.youtube.com/watch?v=SeLmwYdegLA&t=459s)
- [you are not an imposter, you are amazing](https://hbr.org/2022/01/youre-not-an-imposter-youre-actually-pretty-amazing)
## Learning Objectives
At the end of this project, you are expected to be able to [explain to anyone](https://fs.blog/feynman-learning-technique/), **without the help of Google:**
- What is imposter syndrom?
- why is it important?
- How do you deal with imposter syndrom"
## Quiz questions
### Question #0
Which of the following describes imposter syndrome? (Select all that apply)
- [ ] A nagging doubt that you haven’t really earned your accomplishment
- [ ] our ideas and skills are not worthy of other’s attention
- [ ] feeling of fraudulence