Four years ago I took a leap and joined a startup. It was a culture shock after over a decade in higher education. Learning is like breathing in a startup, and wearing many hats is a given. For me that included contributing directly to our fledgling codebase. It was a small hat, but it was my favorite. It was thrilling bending code to my will (if it wanted to). Bugs were brain teasers, Jenkins was my friend, git blame was the best, and every day I learned a little more. I participated in the dev team’s sprints. On weekends I would scrum to myself. It came naturally to me, and I loved it.
Startups grow and org-charts arrive. I fought the wind to try and keep my little hat on, until one day I realized I didn’t want that little hat. I wanted a bigger hat. Once I knew it, I couldn’t ignore it. I mustered my courage. I let the little one go and followed it through the breeze to the doorstop of General Assembly. There I was introduced to a broad range of full stack technologies, from JavaScript and JSON to Rails, PostgreSQL, and AWS.
Most importantly, I saw how much work it takes to wear a big hat. It takes partnership, resourcefulness, humility, and constant learning. I’m ready to bring everything I’ve learned to a company that honors those values and shares that fashion sense. Somewhere there’s a coat rack with just the right hat for me!
Foxy File, a file upload and retreival app, was part of a group project. We used Agile methodologies to manage our workflow. In the role of Product Owner I was responsible for ensuring the goals of the user stories and feature requirements were met. My front-end JavaScript contributions included implementing bootstrap and using Handlebars.js, a new library for me that I quickly adopted. After the project was complete I identified a functionality that wasn't in the original spec. With a few changes to the express back end (using Amazon's S3 service) I added the ability to declare files as public or private, making Foxy File useful for managing personal files in addition to the public files accessible by all users.
I would be remiss if I didn't note that I had amazing partners who appreciated the importance of pairing, knowledge-sharing, staying on our timeline, failing on the path to succeeding, and having a ton of fun along the way!