week 16 – score feature, refactoring, new contributor πŸ‘

I spent of my time on refactoring the backend API which was the result of trying to speed things up few weeks agoπŸ˜’. I realized that when I started to implement the score feature. Adding new table, object etc. seemed too complicated, so I decided to clean up the code first. The second reasong for doing that was the fact that my friend decided to join me in developing codingella. He will treat that as a side project, so he will work on it when he will has some free time to code. For me that is really good news as he has a lot of experience in Angular which I’m not an expert in and I will have the opportunity to learn from him and have someone to discuss my ideas with.

what was done last week?

  • saving the user’s progress (only points at first)
  • progress bar (shows how many questions left)
  • component with the top scorers
  • another developer was introduced to the project
  • backend API was refactored (repositories and services)

what was the biggest impediment?

Refactoring the API. After I finished the first angular prototype (which took me quite a long time) I tried to develop the API as quickly as possible. Therefore I made a lot of code smells: I was not consistent with the responsibilities of the repositories/services, I left a lot of dead code and wrong names that weren’t easy to fix.

what is the plan for next week?

  • more questions
  • admin panel (managing questions) available only for the users with admin rights
  • adjust the UI for longer questions

time spent

  • from last week
    21h 0m
  • overall
    229h 0m

costs

  • from last week
    0 $
  • overall
    32 $

summary

Despite many additional, unplanned tasks (refactoring and introducing a new programmer), I managed to add two functions related to storing progress 😎 Hopefully next week I’ll finally be able to focus on filling up the database with more questions.

Related Posts

Leave a Reply

Your email address will not be published.