Technical Blog — Problem Solving
The Big Idea
Writing about your problem-solving process makes you more aware of it — and more intentional next time. This blog post asks you to tell honest stories about what worked, what didn't, and how you approached getting help.
⚑ This task is assessed This blog post is assessed. We are looking for specific, honest stories about your problem-solving process — including a moment when you were reluctant to ask for help.
Your Roadmap
| Section | Time | Required? |
|---|---|---|
| Create your blog file | 5 min | ⚑ Required |
| Write your post | 75 min | ⚑ Required |
| Publish | 5 min | ⚑ Required |
Create your blog file
Create a file named problem-solving.html in your blog.
For a reminder on how to do this, see Blog Instructions.
Write your post
Use the notes you kept during the Problem Solving and Pseudocode task and the kata challenges. Write as if you are telling a non-technical friend stories from your sprint. Be specific — general statements like "I found it hard" are less useful than "I spent 45 minutes on one error before I realised I had a typo in a variable name."
1. A time you were blocked on a simple problem
- What was the problem?
- What problem-solving techniques did you use?
- How did you feel throughout the process?
- What did you learn?
2. A time you solved a problem elegantly
- What was the problem?
- What problem-solving techniques did you use?
- How did you feel throughout the process?
- What did you learn?
3. Reflect on your confidence with each technique
Rate or describe how confident you feel using each of these:
- Pseudocode
- Trying something
- Rubber ducky method
- Reading error messages
console.log- Searching online
- Asking peers for help
- Asking coaches for help
- Improving your process with reflection
4. A time you were reluctant to ask for help
- What made you reluctant?
- What did you do instead?
- What might you try differently next time?