Monday
After a few meetings for I-Riide, I began working on the duplicates script.
The goal was to optimize all queries to retrieve all the necessary entities. I reviewed the script to ensure that it only retrieved the needed fields, and with these changes, the script runs much faster.
Following this, I had a call with two colleagues to review the script thoroughly, as the customer intends to launch it against some test users. During the call, we discussed the script in detail, looking for areas of improvement, and making necessary changes.
We tested the script multiple times, ensuring that it was working as expected. Post-lunch, we had another meeting to discuss the upcoming launch of the first version of the script.
We went through the final checklist for the launch, ensuring that everything was in order.
We are confident that the first version is ready to go live and plan to launch it tomorrow.
Mood: 🚎
Tuesday
I recently launched a script on production to check for duplicates. During the testing phase, I discovered that whenever an event is deleted, a notification is automatically sent to all attendees. This feature is helpful in ensuring that attendees are up-to-date with the latest information.
To further understand how MudBlazor works, I created a project called passwordify.xyz. This project allowed me to explore the different features of MudBlazor, such as the ability to create custom components and user interfaces. Through this project, I gained a deeper understanding of how MudBlazor can be used in web development.
In the future, I plan to write a blog post about my experience with MudBlazor and how it can be used to create dynamic and responsive web applications. Stay tuned for more updates!
Mood: ⚡
Wednesday
Worked on the Azure Function to create new team in Microsoft Teams based on templates.
Published the passwordify project on the real domain and source code on GitHub.
In the afternoon tried to publish the Azure Function but I got an error. It’s about the old version of Azure Core Tools installed on my machine. I tried to update them but the error still continued to appear. I discovered that I needed to install the npm version instead of the Windows Installation. Lesson learned.
I will do the same on my laptop for side projects and events.
Mood: 🚑
Thursday
I published a blog post about setting up Visual Studio Code for C# development.
https://dev.to/this-is-learning/setting-up-vs-code-for-c-development-21do
Mood: 🤯
Friday
I created a new page on my website for the newsletter with some information about it and about how to become a sponsor!
You can find the page here: https://www.emanuelebartolesi.com/newsletter
After lunch I started to write some user stories with a colleague of mine about the I-Riide App.
We will write other stories in the next days. I asked for help because we have too much screens to describe as a user story.
After that, I had a call with the Brandplane team, about the next 15 days of development. We need to focus to deliver our next features in the next sprint.
Mood: 🤞🏻
If you enjoyed this blog post and want to learn more about C# development, you might be interested in subscribing to my bi-weekly newsletter called Dev Dispatch. By subscribing, you will get access to exclusive content, tips, and tricks, as well as updates on the latest news and trends in the development world. You will also be able to interact with me, and share your feedback and suggestions. To subscribe, simply navigate to https://buttondown.email/kasuken?tag=devto, enter your email address and click on the Subscribe button. You can unsubscribe at any time. Thank you for your support!
Top comments (0)