This week, I've continued working on the new interface for entering feedback. My approach to developing these apps has been focused on fast prototyping and iteration. Rather than spending a lot of time thinking things through, I prefer to quickly implement features and then play with them to test and refine. This approach allows me to rapidly improve my prototypes, but it wouldn’t be feasible if I were working with multiple people—unless we could collaborate very closely and stay in sync. In the future, I'd like to have one or two employees to work with in person for quicker iteration. I’ve considered contracting another developer and/or a UX person, but I realized this week that the current state of my app is too chaotic to make effective use of additional team members. The good news is that I feel I'm quickly getting closer to a more polished version of my idea.

This week, I also refined the core domain object names that I had been unhappy with for a long time. It’s incredible how much clearer names can improve code readability. One of the main parts of my app has been the feedback structure, which is now organized as follows:

• Feedback Categories: These are the top-level groupings of traits, e.g., "Communication & Emotional Intelligence." Currently, there are 8 categories.

• Feedback Traits: These are now the core elements of the feedback structure, e.g., "Clear Communicator," "Emotional Distancer." Right now, each category consists of 4 traits, but this may increase to 6 or 8.

• Feedback Behaviors: These are the most specific elements of the feedback structure, closely tied to each trait. They describe specific behaviors someone might exhibit related to a trait. There are currently 5 behaviors per trait, which seems like a good number.

These new names replace the previous terms: feedback group, feedback item, and feedback detail.