This past week has been pretty good all things considered. The offshore team stopped working for us (till we get more funding to pay them) so I had to take over fixing things. They pushed out v1.0.0 to production though which is good. I just had to clean up the rest and push that out as well. With that, our CEO can start investor talks again.
Monday, February 5th
The day began with high hopes as I wrapped up and pushed the "various prompt fixes" branch to staging. This task, which had consumed much of my focus, was finally ready for review. I enlisted our CSO to test the changes, eager for positive feedback. However, the software development journey is seldom a straight path. The testing revealed issues that necessitated a reversion of the branch. While disappointing, this step back was a reminder of the importance of thorough testing and the need to remain flexible. The purpose of the fixes were to make the todo list creation a lot more robust since it is the primary purpose of our app at the moment. With it I also added in a bunch of refactoring for the future.
Tuesday, February 6th
Undeterred by yesterday's setback, I tackled the todo list issues head-on. With some creative problem-solving, I managed to fix the issues without a complete rewrite of the actual parser as I'd originally set out to do Monday night, a small victory that kept the momentum going. I then turned my attention to the skeleton of the decision engine, laying the groundwork for what promises to be a key component of our project.
Wednesday, February 7th
Wednesday was a day of significant progress. This was the day that the offshore team stopped working for us. I deployed the new version number on the settings page, marking the completion of another task with a sense of accomplishment. The deployment to production was a major milestone, followed closely by addressing and fixing mood mods bugs/issues. Mood mods is a feature where you click on a face related to an emoji and it will give you the option to do something to combat that emotion. For example, an angry face will take you to a guided exercise with an audio file to follow along. The day was rounded off with some necessary housekeeping: tidying up git, organizing Trello, and creating new cards based on the User Acceptance Testing (UAT) document. These tasks, though less glamorous, are crucial for maintaining order and clarity in our project's development.
Thursday, February 8th
With the public release of v1.0.0 on the horizon, I focused on pushing out any remaining commits. The pull requests for both the server and webapp were a testament to the collaborative effort and hard work of the team. I also revisited our Trello organization, making adjustments to ensure that priority and difficulty are now more straightforwardly managed with vanilla fields, moving away from the less effective powerup we had been using.
Friday, February 9th
The week closed with attention to detail and collaboration. After changing the width of the action bar, Dan flagged a potential bug during onboarding, prompting a review and adjustment phase. The deployment to staging of this change signifies our commitment to refinement and user experience. Additionally, my wife had joined the team as well and my work with her on Rewardful, although currently on the backburner, is an exciting venture into new territory, promising future development and integration. We would like to use it for affiliate links in the future.
Anyway, that's all for this week, cheers. Hopefully we secure funding this week and we can get the dough rollin in!
Top comments (0)