Array Mobile
ArchivedJanuary 1, 2020
A mobile app for Array School of Technology and Design — the coding bootcamp that taught me to code but did not have its own mobile app. So I built one. A lesson in self-determination: do not wait for someone to assign you the work that obviously needs doing.
Purpose
Array was a coding bootcamp that taught software development, where I landed a job building mobile apps. But the bootcamp itself did not have a mobile app. The irony was too loud to ignore — so I built one. Nobody asked me to. Nobody assigned it. The gap was obvious, the skills were fresh, and waiting for permission was not an option.
Stack
What I Learned
- The best projects are not assigned — they are noticed. A coding bootcamp without a mobile app is a gap that every student walks past. Most people see the gap and think "someone should build that." Self-determined people see the gap and think "I am someone."
- Building an app for your employer or school without being asked is the highest-signal demonstration of initiative. It says: I understand the business, I see a need, I have the skills, and I do not need permission to create value. That signal is louder than any resume line.
- The app itself was a straightforward Flutter + Firebase build — course information, schedules, resources for students. Technically simple. The complexity was not in the code. It was in the decision to build it at all.
- Self-determination theory (Deci & Ryan) identifies three human needs: autonomy (I chose this), competence (I can do this), and relatedness (this matters to people I care about). Building Array Mobile hit all three: I chose the project, I had the skills to execute, and it served the community that taught me. That trifecta is why some projects feel energizing even when they are unpaid.
Key Insights
- Self-determination is the meta-skill underneath every other skill. Technical ability tells you what you can build. Self-determination tells you what you will build. The developer who waits for a ticket will always be outpaced by the developer who opens the backlog and writes their own.
- This pattern — see a gap, build the solution, present it — is the same pattern as the La Fleur mockup from bootcamp. It is a repeatable playbook that has worked at every stage of my career: bootcamp (La Fleur), first job (Array Mobile), and beyond. The playbook scales because the principle is universal: demonstrated initiative is the most compelling argument for trust, responsibility, and opportunity.
- The irony of a coding school without an app is a specific instance of a universal truth: the cobbler's children have no shoes. Every organization has internal tools, processes, or experiences that are worse than what they sell to customers. Finding and fixing those is a career accelerator because you are solving a problem the decision-makers feel daily but have deprioritized.
- In the age of AI, this playbook is even more powerful. The time cost of building a functional app has collapsed. What used to take weeks of solo development can now be scaffolded in hours. The barrier is no longer "can I build this?" — it is "will I decide to build this?" Self-determination was always the bottleneck. AI just made it more obvious.
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.