Growth & Perseverance

Building SisterShield as a solo project meant every challenge — technical, design, or strategic — had to be resolved independently. This page documents that journey: the problems encountered, the reasoning behind solutions, and the growth that resulted. The Technovation rubric values a clear narrative of challenges and learning, and this page provides exactly that.

Before vs After: Design Evolution

Each entry below documents a specific issue discovered during development, the hypothesis for fixing it, the change applied, and the outcome.

Evolution 1: TODO: Title

Field	Detail
Issue Discovered	TODO: What problem was identified? (e.g., “Users experienced purple fatigue — too many elements competed for attention”)
When/How Discovered	TODO: Testing cycle, self-review, mentor feedback, etc.
Hypothesis	TODO: What did you believe would fix it?
Changes Applied	TODO: Specific UI/code changes (with links to relevant commits or files)
Before State	TODO: Screenshot or description of the UI before the change
After State	TODO: Screenshot or description of the UI after the change
Outcome (Qualitative)	TODO: User feedback, personal assessment
Outcome (Quantitative)	TODO: Task completion rate, time-on-task, error rate
Next Steps	TODO: What would you refine further?

Evolution 2: TODO: Title

Field	Detail
Issue Discovered	TODO
When/How Discovered	TODO
Hypothesis	TODO
Changes Applied	TODO
Before State	TODO
After State	TODO
Outcome (Qualitative)	TODO
Outcome (Quantitative)	TODO
Next Steps	TODO

Evolution 3: TODO: Title

Field	Detail
Issue Discovered	TODO
When/How Discovered	TODO
Hypothesis	TODO
Changes Applied	TODO
Before State	TODO
After State	TODO
Outcome (Qualitative)	TODO
Outcome (Quantitative)	TODO
Next Steps	TODO

Adding More Evolutions

Three or more is a strong target, but quality matters more than quantity. More documented evolutions demonstrate deeper iterative thinking. Consider adding entries for Quick Exit refinements, i18n challenges, AI prompt tuning, or accessibility improvements.

---

Challenge & Ambiguity Log

Real projects involve ambiguity — moments where there is no clear right answer. This log documents those moments and how they were resolved.

Challenge 1: TODO: Title

Field	Detail
Challenge Encountered	TODO: What was the problem or ambiguity?
Why It Was Hard	TODO: What made this non-obvious? Multiple valid options, conflicting requirements, unknown territory?
Constraints Identified	TODO: Time, technical, design, ethical constraints
Alternatives Considered	TODO: List at least 2 alternatives and why each was or was not viable
Resolution Approach	TODO: What was decided and why?
What Was Learned	TODO: Transferable insight gained from this experience

Challenge 2: TODO: Title

Field	Detail
Challenge Encountered	TODO
Why It Was Hard	TODO
Constraints Identified	TODO
Alternatives Considered	TODO
Resolution Approach	TODO
What Was Learned	TODO

Challenge 3: TODO: Title

Field	Detail
Challenge Encountered	TODO
Why It Was Hard	TODO
Constraints Identified	TODO
Alternatives Considered	TODO
Resolution Approach	TODO
What Was Learned	TODO

Types of Challenges to Document

Strong entries include: architectural decisions with trade-offs, moments where user feedback contradicted assumptions, ethical dilemmas in content design, scope management as a solo developer, debugging complex integrations (AI, Twine, i18n), and moments of self-doubt resolved through research or persistence.

---

Solo Project Narrative

Building SisterShield as a single developer required wearing every hat: designer, developer, researcher, project manager, tester, and content creator. This narrative documents the personal growth that came from that breadth.

Time Management

TODO: How was the project timeline managed? What tools or methods were used? Were there moments when scope had to be cut, and how were those decisions made?

Self-Directed Learning

TODO: What new skills were required that were not known at the start? How were they learned? What resources were most helpful?

Motivation Through Difficulty

TODO: What kept the project moving during the hardest moments? Was it the mission, a specific user story, a personal connection to the problem, or something else?

---

Technical Growth Areas

Document specific technical skills learned during the project.

Skill Area	Starting Level	Ending Level	How Learned	Evidence
Next.js 14 App Router	TODO	TODO	TODO	TODO: Link to specific implementation
Prisma ORM	TODO	TODO	TODO	TODO: Link to schema or migration
AI Integration (LLM APIs)	TODO	TODO	TODO	TODO: Link to AI course generation code
Trauma-Informed Design	TODO	TODO	TODO	TODO: Link to design decisions
i18n Implementation	TODO	TODO	TODO	TODO: Link to locale configuration
Twine Parsing & Injection	TODO	TODO	TODO	TODO: Link to Twine builder code
TypeScript	TODO	TODO	TODO	TODO: Link to complex type usage
Accessibility (WCAG AA)	TODO	TODO	TODO	TODO: Link to accessibility implementation

Be Honest About Levels

Judges value authenticity. Starting at “beginner” and reaching “intermediate” is more impressive than claiming to go from “intermediate” to “expert.” Honest self-assessment demonstrates maturity.

---

Rubric Mapping

Rubric Category	How This Page Contributes
Growth & Perseverance	Clear narrative of challenges encountered, alternatives considered, and learning outcomes
Technical	Technical growth areas with evidence of skill development
User Experience	Before/After evolutions show iterative refinement driven by user needs

Strengthening This Section

To score Level 5 on Growth & Perseverance:

• Fill in Before/After evolutions with concrete evidence (screenshots, data, links) (recommended: 3+).
• Fill in Challenge Log entries with genuine, non-trivial challenges (recommended: 3+).
• Write the solo project narrative with specific, personal detail — not generic statements.
• Include links to commits, files, or screenshots wherever possible.