|
....but that's far from the full picture.
It actually took me months. Months of asking our users questions, analysing their responses, and thinking.
Thinking about: What's the smallest feature set that can launch Buddy Reads and still provide an excellent experience? How should I structure the different code objects? How should I store the information for each buddy read in the database? What are the edge cases? And more!
For big new features, once I've got all of my research and thoughts in order, I'll write up a "specification" document that includes a list of high-level features and delves into some technical details. Rob and Abbie will review the doc and, if necessary, I'll tweak things, taking into account their feedback.
And then it's time to implement.
It was only because of months of thinking about Buddy Reads that I was able to get through the actual coding in a couple weeks!
There was little left to think about. 😌
|
