C# Front End Quiz
ArchivedApril 1, 2018
A quiz application built in C# during the Array School of Technology and Design coding bootcamp. Part of a 10-month curriculum completed in 5 months — the project that led directly to an apprenticeship.
Purpose
Built as a study tool while working through the bootcamp curriculum. The book-based coursework covered front-end fundamentals, and this quiz app was a way to internalize the material by building something that tests it.
Stack
What I Learned
- Consuming knowledge passively (reading the book) is not the same as mastering it — building a quiz that tests the material forces you to understand it deeply enough to formulate the questions
- Speed of completion is a signal. Finishing a 10-month program in 5 months was not about cutting corners — it was about intensity of focus and compounding understanding
- The apprenticeship that followed was a direct result of demonstrating undeniable competence — not credentials, not networking, just visible proof of work
- C# and .NET exposure early on built a foundation for understanding typed, compiled languages that transferred directly to TypeScript, Swift, and Dart later
Key Insights
- Mastery is not granted — it is taken. When consuming knowledge, it is incumbent on you to take the bull by the horns and develop that mastery until you become undeniable. Nobody hands you the next level. You build it yourself and dare them to ignore it.
- The fastest learners are not the ones with the most talent — they are the ones who refuse to move on until they truly understand what they just read. Depth beats breadth at every stage of a career.
- Building projects that teach you the material (like a quiz app for a textbook) is a meta-learning technique — you learn the content AND you learn to build, simultaneously
This post was composed through a conversation between Brett Owers and Claude Code (Anthropic). The content reflects Brett's recollection of each project and the lessons drawn from it. Some details may be approximate or omitted — the purpose is to paint an honest picture of a software engineer's development over time, not to serve as a precise historical record.