Key Takeaways
Use a craft, not just a microphone, to make your ideas heard
A different kind of voice. Sophie began as a student who dreaded speaking in class and judged her worth by grades. Journaling gave her a private place to express ideas, but she wanted those ideas to reach others. Learning to code offered another route: she could turn a thought into a game people could use. An early speaking circle, where strangers shared stories while being filmed, also taught her that visible nervousness did not automatically invite ridicule.
Expression takes practice. At Girls Who Code, Sophie gradually raised her hand, then helped present Tampon Run to an audience. Coding did not erase her shyness. It gave her a reason to share, while supportive experiences made speaking less frightening.
What's striking is that the book treats expression as something people can practice through different media, not a personality trait reserved for the naturally bold. A journal, a program, and a public presentation each offer a different threshold for risk. That perspective can help people who find direct self-promotion difficult: making something can give an idea a concrete form before its creator feels fully confident. Still, a project cannot speak entirely on its maker's behalf. Sophie’s growth depended on eventually letting other people hear her explain what the game meant.
Treat coding as precise problem-solving, not mysterious math
Give the computer every step. The book introduces code as instructions a computer follows, with little ability to infer what a person meant. Its peanut-butter sandwich comparison makes the point: a vague request to prepare one leaves countless unstated actions. A working program requires breaking a large task into small, explicit steps.
Start with a workable outline. For a first project, Sophie and her partner Karla planned an Elvis-themed slot machine. They identified what should happen when the player pressed Spin, how the machine would select images, and what counted as a win. They then translated those steps into Scratch, a visual coding tool. When programs fail, the problem may be a typo or a faulty plan. Finding and correcting these bugs is part of building, not proof that the builder lacks ability.
The book makes a useful bridge between programming and general problem-solving: a complicated goal becomes manageable when its assumptions are made visible. This is the same move used in project planning, scientific protocols, and clear writing. It also explains why beginners can code without advanced mathematics. The central challenge is often decomposition, not calculation. The analogy has limits, though. Human collaborators can infer intent and negotiate ambiguity; computers cannot. Learning to code therefore teaches precision, but real-world projects still need judgment about which details matter.
Put beginners where mistakes earn help, not judgment
Belonging changes participation. Sophie arrived at Girls Who Code unsure whether she belonged in technology. The program brought twenty girls together for seven weeks of coding, projects, and mentorship. Working in pairs meant confusion could not stay hidden, but classmates and instructors treated struggle as ordinary. Sophie began raising her hand because she expected support rather than humiliation.
Representation matters. The book reports that women made up 25 percent of coders in 2015, and that women of color were particularly underrepresented. It argues that visible role models can help girls imagine themselves in the field. Andy had already felt outnumbered at a coding camp where nearly every camper was a boy. An all-girl learning environment gave the authors a setting where they could take risks and build confidence.
The authors connect representation with participation: seeing people like oneself in a field can make belonging easier to imagine, while a supportive group can make the first risks less costly. That is a strong case for widening access, not lowering expectations. The figures in the book are a snapshot from 2015, not a description of the field today, and the memoir cannot isolate the effect of gender composition from excellent teaching and mentoring. Its clearest lesson is practical: inclusion requires both access to training and an environment where beginners can ask questions without being treated as exceptions.
Turn taboo into a playable joke that makes silence visible
A strange idea exposed a familiar rule. Andy and Sophie proposed a side-scrolling game in which a girl throws tampons at approaching enemies. Their satire contrasted society’s comfort with fictional gun violence against its discomfort with menstruation. The idea grew from their own habits of hiding tampons and feeling embarrassed to discuss periods, then expanded as they learned about limited access to menstrual products and the stigma surrounding them.
Play opened conversation. The game, eventually titled Tampon Run, began with a short explanation of the taboo before players started. It reached more than half a million people through its website and mobile app. The authors’ aim was not to claim that a game could solve every practical problem, but to make an ignored subject easier to discuss.
The game’s design makes its argument without requiring a lecture: players encounter the incongruity, then have a reason to ask why it feels funny or uncomfortable. Humor can lower the social cost of discussing a taboo, especially when the subject is treated as ordinary rather than shameful. But visibility is not the same as material change. A playful message may prompt conversation, while access to menstrual products and changes in institutional practice require different forms of action. The project works best as an invitation into a broader issue, not a substitute for addressing it.
Release the work before you know who will care
Publishing made the project real. After their Girls Who Code program ended, the authors improved Tampon Run, bought a web address, and put the game online. They posted it on Reddit and shared it through social media, expecting little attention. The first Reddit response was small. Then, within roughly a day, a British outlet wrote about the game, followed by a wave of press requests and messages from players.
The response was unpredictable. The sudden attention revealed practical oversights: the website did not initially include their full names or contact details, so they had to add biographies and an email address. Their story is not a recipe for going viral. It shows what can happen when a finished-enough project is shared, and why creators should be ready to respond if people do notice.
The authors distinguish making a project from giving it a chance to travel. That distinction is useful: private perfection can prevent feedback, while publication exposes an idea to audiences its creators cannot predict. Yet the sudden coverage should not be mistaken for a repeatable growth strategy. Virality depends on factors beyond a creator’s control, and most launches do not receive major press. The transferable lesson is smaller and more reliable: publish a clear version, make it possible for people to contact its makers, and learn from the response rather than treating attention as proof of worth.
Practice courage by surviving the failure you fear
The feared moment arrived. Sophie dreaded public speaking and worried that forgetting her lines would prove she could not handle an audience. At the Girls Who Code graduation, she did forget them. She turned to a notecard and finished the presentation. The audience responded warmly, and she realized that the disaster she had imagined had not destroyed the event or her ability to speak.
Confidence came through repetitions. Sophie still felt nervous before later talks. Before a fifteen-minute speech at college, she cried while practicing. Onstage, she focused on telling the story rather than monitoring every audience member’s reaction. She described that success as the result of many earlier presentations and unfamiliar situations, not a sudden cure for anxiety.
This is a persuasive account of learning through experience: feared outcomes can lose some of their power when a person encounters them and discovers a way through. The notecard matters because courage here does not mean performing flawlessly or refusing support. It means continuing with a backup plan. The book’s account is a personal story, not a universal treatment for severe anxiety, and some people need structured professional help. Still, it offers a grounded alternative to waiting for fear to vanish before acting: prepare, take a manageable risk, and learn what actually happens.
Choose collaborators who let you struggle without taking over
Different strengths can work together. Andy brought more programming experience to Tampon Run, while Sophie contributed organization, writing, and steady project management. When Sophie spent hours trying to make the game’s character jump, Andy did not simply seize the task. She offered to talk it through and trusted Sophie to keep working. Sophie eventually found the solution and shared the success with her partner.
Structure can make teamwork productive. At Pivotal Labs, the authors saw pair programming: two developers work at one computer, with one typing and the other discussing the approach and checking the logic. The arrangement felt tiring at first, but it helped them explain their reasoning, spot errors, and ask questions. Collaboration was not effortless agreement. It required patience, honest communication, and room for each person to contribute.
The story challenges a common but damaging definition of efficiency: the fastest person doing the task alone. A collaborator who supports someone through difficulty can build both the project and the other person’s capacity. Pairing also makes hidden assumptions discussable, which is valuable in technical work where a program may run while still solving the wrong problem. The approach is not automatically superior in every setting; it requires trust, compatible working habits, and time for communication. Its value depends on whether shared work produces learning and quality, not merely more conversation.
Let a breakthrough open doors, not lock you into one identity
One success does not dictate a career. After Tampon Run attracted attention, adults asked whether Andy and Sophie would keep making games or launch a company. Their experiences revealed a wider range of possibilities. Andy saw a collaborative workplace at Pivotal Labs, where developers worked with clients and designers. Her mentor Nikki used computer science knowledge in a technical project-management role rather than coding all day.
Paths can change. Sophie met Sarah Adler, a journalism graduate who learned to code and became a technology leader at Spoon University. The examples helped the authors see that studying computer science could support work beyond a conventional programmer job. Andy also learned that a high-pressure start-up or hackathon lifestyle was not the only possible route into technology.
These examples make career exploration concrete: a field of study can be a toolkit rather than a lifelong job title. Mentors are especially useful when they reveal roles that a newcomer would not know to search for. At the same time, a few visible success stories cannot guarantee that every path is available or financially secure for every person. The authors’ uncertainty is part of the point. A breakthrough can provide evidence about what someone enjoys, while leaving room to gather more evidence before making a permanent identity out of one achievement.
Protect the ordinary joys that meaningful work can crowd out
Impact has an opportunity cost. As Tampon Run expanded, Sophie struggled to balance interviews and project work with school, friends, and rest. She recognized that perfect grades had become a test of self-worth, not simply a measure of learning. Andy missed a major school event and saw piano, a long-standing part of her life, fall away as she prioritized the game and its opportunities.
The tradeoff was real, not simple. Both authors valued the project and the good it could do, yet they also missed ordinary time with friends and activities that mattered to them. Sophie later found ways to bring her humor and creativity into an internship. Their experiences suggest that ambitious work need not be joyless, but they do not pretend every commitment can be kept at once.
The book resists two easy stories: that meaningful work should always feel fulfilling, and that personal sacrifice automatically proves commitment. Its examples make the cost visible in missed rituals, depleted energy, and neglected interests. This is a useful corrective to cultures that treat constant availability as ambition. The practical challenge is that opportunities often arrive with deadlines, so balance cannot mean preserving every activity unchanged. It requires choosing deliberately, noticing what is being displaced, and allowing priorities to change rather than letting a project’s momentum make every decision.
Analysis
Girl Code is a dual memoir about learning to code, but its deeper subject is how people become able to act on ideas before they feel fully qualified to own them. Sophie begins convinced that her thoughts may be foolish. Andy begins with ambition shaped by family expectations and early exposure to programming. Their separate paths meet in an all-girl coding program, where small projects, patient teachers, and peer support convert abstract interest into practical ability.
The book’s strongest narrative move is to connect technical learning with social expression. Tampon Run is not simply a viral success story. It is evidence that a novice can build an argument into a product, then use that product to create openings for discussion. Its design translates the authors’ discomfort about menstruation into a game that makes the discomfort itself noticeable. The reach of the game matters, but the more durable change is in the authors’ sense that their ideas can leave the private page and enter public life.
The memoir also avoids presenting success as a clean transformation. Sophie still experiences fear after public speaking victories. Andy enjoys technology while questioning the start-up culture around it. Their work brings recognition and mentorship, but also consumes time once devoted to school, music, friends, and ordinary rest. That tension makes the book more useful than a simple tale of confidence: growth can be real without being total, and meaningful work can still have costs.
Its scope is personal rather than evidentiary. The book offers persuasive testimony about how supportive environments helped these two students, not a controlled demonstration that a particular program works for every girl. Nor does an inspiring project by itself remove structural barriers in technology or solve the material problems connected to menstrual stigma. The most transferable lesson is therefore not that everyone should make a viral game. It is that access, practice, collaborators, and a real audience can turn tentative ideas into competence, while reflection is needed to decide what that competence should serve.
Review Summary
Girl Code is a memoir by two teenage girls who created the viral game Tampon Run. Readers praise the book's inspiring message of female empowerment in tech and challenging menstruation taboos. Many found the authors relatable and their coding journey engaging. The book resonated with both young girls interested in STEM and adult women in tech. Some critiqued the writing style as simplistic, but most appreciated the honesty and girl power message. Several reviewers recommended it highly for middle and high school girls.
Glossary
Minimum viable product (MVP)
Simplest usable projectA minimum viable product is the simplest version of a project that can still communicate its central idea or meet its basic purpose. Before building Tampon Run, the authors defined a fallback version using simple shapes to represent the player and enemies. This gave them a deliverable target if their more ambitious design could not be completed in time.
Pair programming
Two developers, one computerPair programming is a way of developing software in which two people work together at one computer. One person types while the other discusses the approach, checks the reasoning, and notices possible errors. The authors encountered the method at Pivotal Labs, where it helped them communicate their thinking and produce code that had been reviewed as it was written.
Debugging
Finding and fixing code errorsDebugging is the process of identifying and correcting problems in a program. A bug may be a syntax error, such as a misspelled command, or a logic error, where the program runs but does not do what its creator intended. The book presents repeated testing and correction as an ordinary part of programming, not evidence that someone is unsuited to it.
Sprite
Animated game imageA sprite is an image or game object used to represent a character or other visual element. Animation can be created by rapidly switching among images that show slightly different positions. While building Tampon Run, Andy designed and animated the character Luna and other visual elements as sprites, then connected them to the game’s code.
Game jam
Timed game-building eventA game jam is an event where developers plan and build a video game within a set time, often alongside other teams. In the book’s Silicon Valley example, Andy and Sophie had twenty-seven hours to make CatCall Run with unfamiliar development tools. A game jam is one form of hackathon, a time-limited gathering organized around creating technology.
Menstrual taboo
Stigma around menstruationThe menstrual taboo is the social discomfort, shame, or silence surrounding menstruation and menstrual products. The authors connect it to their own efforts to hide tampons and avoid discussing periods, as well as broader examples involving product advertising and limited access to supplies. Tampon Run used humor and play to make this stigma visible and easier to discuss.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.