Note: this should have been posted on Sunday, 12/01/25.
Things I've worked on/completed since my last post…
I am still working on To-do. I have been coming across multiple small issues and each time I fix one, another presents itself, so I am just taking my time trying to fix each problem. I will not detail every problem I have encountered, as keeping in-depth record-keeping is difficult, especially when you have limited time to progress with project. However, I will summarise my experience this week below…
Things that went well...
This is the first project I have done in which I have used Chrome debugger. I feel much more comfortable with it (still probably only using the basics), but glad to be finally using it (I may have mentioned this in a recent post also).
Even though my progress is slower than I would like, I have learnt to take time pressure off myself, which is leading to clearer thinking.
Things that didn't go quite so well...
I initally set up my logic to create and array of tasks which would be identified by their index in the array. I thought this was great until I started deleting things and realised this would affect functions which relied on index numbers to function, as deleting tasks would change those index numbers. ** This was a huge problem**. although there may have been a way to work with this, I thought it better to rework things to have a unique ID for each task instead.
I had a lot of trouble trying to implement what I thought would be a simple filter on an array. Why? Well, a combination of factors. The way my array was set up, it was in fact the value of a property in an object and I wasn’t sure how that would affect things. I then ‘grabbed’ an example of a filter (which I hadn’t used in quite a long time) and discovered that I was misunderstanding what each part of the syntax meant (especially in relation to the items in the array, which I thought needed some ‘special syntax’ because they were contained within an object) I attribute my struggles with this to the fact that I was rushing and not thinking things through clearly and methodically, as I felt that I was spending too much time on things and this was causing me to not concentrate properly. I had to go through everything line-by-line and slowly. I had a number of variables that I had forgotten the significance of along the way and I needed to figure out what role they played. I eventually solved this problem.
I thought I had a number of things working and then realised that once all tasks were deleted from a project (without refreshing the page), this was causing further issues as certain variable counters needed to be reset, so I had to implement logic for this.
A few days ago, as I was testing the app (adding /deleting/editing tasks), I saw that my ‘trigger’ to indicate that a task was edited, was causing undesired effects in other places. Although I think I the logic to fix this is not complicated, the current problem I am now having is that my ‘fix’ is not working due to scoping issues and I am trying to figure out a way around that. In trying ot fix that today, I think I have accidentally deleted something that is causing syntax issues and so I am going to try to fix that before contiuing with the other problem I had
Things I've learnt/need to improve on...
Putting myself under time pressure causes me to make more mistakes/not think clearly. For me at least, it’s best to take the time pressure off and just work slowly through the problem.
In my rush to ty to fix my editTask problem,** I think I implemented more than one method without deleting the previous one, which is a great way to cause a mess** - one at a time will be the strategy moving forward.
Plan for the forthcoming week...
I hope to finally fix my editTask scope problem in the To-do project.
Top comments (0)