Weekly 0066

#weeklyretro #devjournal

Monday

In the morning I had a call with my co-founder Dereck about defining the final steps for releasing our I-Riide app to the Apple Store.
After that I synched my GitHub repo for I-Riide on my new Apple Mac Air.
Before of that, I applied 3-4 stickers on it!
I started to work on some small fixes in the UI because I am a kind of junior with Swift and xCode as well.
We are all forever learner.

After that I worked on an opensource project: Front Matter.
I created the italian translations for the Visual Studio Code Extension.
You can find the Pull Request here: https://github.com/estruyf/vscode-front-matter/pull/630

Mood: 🤘

Tuesday

My colleagues have been struggling with finding duplicate items in Microsoft 365 (after a wrong migration), which has been causing some inefficiencies in a customer environment. In order to address this issue, I suggest creating a script using PowerShell and Graph API that can automate the process of identifying and managing duplicate items. This script can be customized to our specific needs and can save us a significant amount of time and effort.
I started to work on it as a very important task.

Mood: 🧑‍🚀

Wednesday

In order to ensure the success of Brandplane, it is imperative that we meticulously check all of the tickets. This means going through each ticket with a fine-tooth comb, analyzing every detail to make sure that everything is in order. By doing this, I can identify any potential issues or errors that may have been missed and address them before they become bigger problems. Additionally, this process can help us to gain a deeper understanding of the needs and preferences of our customers, allowing us to better tailor our services to meet their needs.
I closed a lot of them and I opened some issues on GitHub with a better description for us.

In the afternoon I started to improve the script for the duplicate items. Now it’s faster.

Mood: 😱

Thursday

To create an accurate and comprehensive report for the duplicates tool, we will need to follow several steps. Firstly, we must identify the scope of the report, including which data sets and fields will be included. Once this has been established, we can proceed with gathering the necessary data. This may require coordinating with other teams or departments to obtain access to the relevant systems and databases.

It is also important to consider any potential outliers or anomalies that may affect the accuracy of the report. This could include data entry errors, missing data, or inconsistencies in formatting or naming conventions. By thoroughly reviewing and cleaning the data, we can ensure that the final report is as accurate and comprehensive as possible.

Once the duplicates have been identified and the data has been cleaned, we can then proceed with creating the actual CSV report with the script.

Call to define the next steps for I-Riide

In the afternoon I had a meeting with the I-Riide team to define the next steps for the near future. We are very close to release the beta in the iOS Store. 🙂

Mood: 😪

Friday

I had the opportunity to participate in an internal community event as a speaker, where I gave a session on GitHub Codespaces. It was a great experience sharing my knowledge and expertise with my colleagues and learning from their feedback and questions. However, I must admit that I initially forgot about the event, which caused me some anxiety and stress as I had to prepare my session in a short amount of time. Despite this setback, I was able to deliver a successful presentation thanks to my hard work and dedication. Overall, I believe that participating in community events like this one is a valuable way to grow both personally and professionally, and I look forward to future opportunities to do so.

In the afternoon I still worked on the duplicates script.

Mood: 🙂

Are you interested in learning GitHub but don't know where to start? Try my course on LinkedIn Learning: Learning GitHub.