Beyond Binary - NTU Women in Tech

Beyond Binary - NTU Women in Tech The flagship inclusive techathon where curiosity meets code. Join 500+ students to ideate, build, and innovate. $10,000 prize pool awaits.

Comment

Beyond Binary: An Analytical Report on Inclusive Technical Innovation

1. Inspiration and Philosophical Foundation

The genesis of Beyond Binary was rooted in a singular observation: the traditional "binary" of the tech world—expert vs. novice, coder vs. non-coder, and the historical male-dominance vs. female-underrepresentation—needed to be dismantled. Inspired by International Women's Day, this platform was designed as a "sophisticated digital catalyst" to empower female-identifying students and their allies at NTU.

The project was built as a lady's response to the competitive tech environment: it prioritizes empathy, collaboration, and intelligent support over raw, gate-kept technicality. The "Beyond" in the title signifies our move toward a spectrum of innovation where strategy and code are equally valued.

2. The Problem Statement: The Inclusion Gap

Despite the rise of local university tech scenes, female participation in hackathons remains disproportionately low due to:

  1. Teammate Friction: High barriers to finding diverse teammates who meet mandatory competition requirements.
  2. The "Blank Page" Problem: Difficulty in ideating projects that balance high social impact with technical feasibility.
  3. Skill Silos: The perception that one must be a "Full Stack God" to contribute to a Hackathon.

Analytical Modeling of Team Success

To understand the "Beyond Binary" solution, we must model team efficiency ($E_{team}$) as a function of diversity ($D$) and technical synergy ($S$):

$$E_{team} = \int_{0}^{T} (D \cdot S + \lambda \cdot I) \, dt$$

Where:

  • $D$ represents the diversity coefficient (mandatory female representation).
  • $S$ is the technical synergy between developers, designers, and strategists.
  • $I$ is the innovation factor sparked by the AI Ideator.
  • $\lambda$ is the inclusion multiplier.

3. Technical Architecture & Approach

3.1 The Innovation Hub (AI Project Ideator)

The platform leverages the Gemini 3 Flash model to bridge the gap between interest and execution. By processing user-provided skills and interests as a semantic vector, the AI generates a project $P$ defined by:

$$P = {Title, Description, Toolkit, Impact}$$

The prompt engineering ensures the output is grounded in "Impact-Driven Problem Solving." It doesn't just suggest a "To-do List app"; it suggests a "Decentralized Healthcare Ledger for Underserved Communities" if the user mentions interest in Healthcare and Blockchain.

3.2 Dynamic Team Discovery System

Building the Team Discovery tool required a shift from static string inputs to Reactive Tag-Based Management. This allows for a granular matching algorithm.

  • Data Persistence: We utilized localStorage to simulate a persistent teammate pool without requiring a heavy backend, making the platform fast and portable.
  • Diversity Validation: The UI visually highlights "Diversity Matches" to ensure teams meet the NTU requirement of at least one female-identifying member.

4. How the Project Works (User Manual)

Phase 1: Exploration

Users navigate the Tracks section to determine their path. The distinction between the Hackathon Track (Build/Code) and Ideathon Track (Concept/Pitch) is clearly demarcated using high-contrast, professional glassmorphism cards.

Phase 2: Ideation

Users enter the Innovation Hub. Here, the Gemini API acts as a "Senior Product Architect."

  • Input: The user selects a track and enters skills (e.g., Python, Figma).
  • Process: The API evaluates current industry trends (Sustainability, GenAI) against these skills.
  • Output: A structured concept with a suggested toolkit (e.g., "Use AWS Bedrock for the LLM layer").

Phase 3: Team Formation

In the Find Teammates section, users can:

  • Filter: Narrow down the pool by Role or Diversity Status.
  • Profile: Create or Edit their profile using the custom Tag System for skills.
  • Manage: Delete or update their presence as their team needs change.

5. Challenges Faced and Resilience

The most significant challenge was the UX of Inclusivity. Designing a form that felt professional yet welcoming required multiple iterations of the Tailwind color palette—shifting from a "harsh dark mode" to a "sophisticated deep indigo and slate" aesthetic.

Technical Hurdle: State Synchronization Managing a nested array of skills within a local storage object while maintaining a search filter was complex. We solved this by implementing a migration layer in useEffect:

$$ \forall p \in Profiles, \text{skills}(p) = \text{Array.isArray}(p.skills) ? p.skills : \text{migrate}(p.skills) $$

This ensured that users with old data (from earlier versions of the app) didn't experience crashes when the platform moved to the tag-based system.

6. What I Learned

Through the development of Beyond Binary, I learned that:

  • AI is a Leveler: By providing high-quality project ideas, we lower the "courage barrier" for new participants.
  • Component Reusability is Key: Building a clean Navbar and Tracks system allowed for rapid expansion into the TeamSection.
  • User Privacy: Even without a backend, providing "Delete" and "Edit" functionality is a vital part of ethical software design—respecting a user's control over their data in the pool.

7. Future Vision

In the next iteration, we aim to implement Real-Time WebSockets for instant teammate messaging and an AI Teammate Matcher that uses cosine similarity to suggest the best partners:

$$ \text{Similarity}(A, B) = \frac{A \cdot B}{|A| |B|} $$

Beyond Binary isn't just a website; it's a movement to ensure that in the future of technology, no one is left behind.

Prepared by: Senior Frontend Lead Date: February 2026 Event: Beyond Binary NTU Women in Tech

Built With

Share this project:

Updates