Skip to content

Weekly report

Student:mustafa.sarikaya@student.ucll.be
Study: Professional BachelorMajor: ICT
Company: YappaCity: Bilzen

Activities Week 02 (16/02/2026 - 20/02/2026)

Monday (Day 6)

I started the day by working on the new Proof of Concept (POC) that links the Notion backend with the Slack bot.

At 11:00, I met with Lotte Smeets, the Project Manager, to gather feedback on the POC. I quickly learned that Notion is used extensively by PM's, and she could envision using the tool. Her feedback included automating and integrating with the Slack bots that are currently being used in a couple of channels, in order to feed information into the system. This way for example, a category (Thematische Lijst) called Deals could be created to provide periodic reports of newly added content.

Later, at 13:00, I had another meeting with Laura Schrijvers, also a Project Manager at Yappa. I presented the POC demo, highlighting the Slack integration for adding knowledge, viewing lists, and generating digest reports. I also explained how the Symfony backend API handles Slack requests and how the Notion API ingests knowledge into the database. The feedback was very positive; she liked the Notion integration and confirmed she would use it in the future.

Half an hour later, I met with the CEO, Yoeri Severy, over a Google Meet call to demonstrate the POC. He was positively impressed and mentioned he is looking forward to the continued development of the tool.

I concluded the day by refining the POC, fixing various UI elements, and preparing the VitePress documentation website.

Tuesday (Day 7)

Every two weeks on Tuesday morning, the Flow dev team holds a project meeting at the end of their sprint, which I decided to join. During the meeting, I observed how the team works and manages their projects. The use of the Jira board, sprint planning, and daily standups are recurring activities. From now on, I will also participate in these sprint meetings.

After the meeting, I gave a brief presentation to the dev team regarding my POC and the overall progress of my project. I explained the entire stack, from using Slack Bolt JS to Symfony PHP as the backend API service (chosen due to the team's experience with Symfony). Finally, I explained how the data is stored in Notion and synced via Symfony. They were impressed with my progress. I also asked a couple of technical questions, such as whether to switch to a TypeScript monolith or keep the stack divided (PHP/JS), and inquired about their prior experience with Notion integrations.

I ended the day by finalizing some changes to my POC and preparing user stories in Jira to start my first sprint.

Wednesday (Day 8)

I began the day with a 9:00 AM meeting to showcase my POC demo to Jeroen Peetermans and gather feedback from the head of the Online Marketing Hub. The meeting lasted about an hour and was highly fruitful. I received valuable insights regarding the tool's output—specifically, the Digest Reports generated for the Thematische Lijsten based on each target group. Jeroen mentioned that each summary should be personalized based on the user's skills and competence (e.g., a marketer might specialize in SEO or SEA). This way, each user group receives highly relevant output and is more incentivized to use the tool. He also suggested prioritizing the knowledge items: if a certain piece of knowledge is particularly important to the target group, the system should highlight it for users who might not want to read every single item on the list.

I continued my day by planning the upcoming sprint and closing tickets for the user stories I had previously generated that were already completed during the POC development. This resulted in resolving 25 of the initial 100 generic Jira user stories. However, I noticed that the majority of the original user stories lacked the specific details required for implementation. Consequently, I created additional user stories to define actionable, finer requirements for the upcoming tasks and features in the MVP.

Given the positive feedback on my POC, my focus now shifts to developing the Minimum Viable Product (MVP) of the KnowledgeHub. To facilitate this, I evaluated the backlog to select the critical user stories required to build the core MVP functionalities for the current sprint.

Thursday (Day 9)

Engineer Plaza

Today, I did not work at the Yappa office as I attended the annual Engineer Plaza at UCLL. The event ran from 15:00 to 19:00, and I used the time to explore the booths of the 100+ companies present.

I visited the Equans booth since I had heard a lot about them, and it made sense to learn more about their work.

Intersoft Electronics I visited the Intersoft booth, where I met Jeroen Van Wouwe, a Radar Support Engineer. He provided excellent information about their work. Jeroen explained that Intersoft builds and develops radar systems. I asked him what programming languages they use for such low-level systems, and he replied that they primarily use Rust, C, and C++. He mentioned they employ about 400 people worldwide, with 315 based in Belgium across multiple locations (contact: Jeroen.VanWouwe@intersoft-electronics.com). I realized that languages like Rust and C++ do not align with my current focus; I have more experience in C#, PHP, and web technologies that I would prefer to utilize in my future career.

Yitch I spent some time at the Yitch booth talking to Noke De Smet, the HR manager. I was personally very interested in Yitch because their primary programming language is .NET/C#. They focus on .NET development for applications ranging from web interfaces in Blazor to WPF desktop apps. The biggest downside—which is a dealbreaker for me—is that Yitch is located in Breda. Because I am unwilling to relocate or have a long commute, I do not think I would want to work there. Their contact email is People@Yitch.eu.

Deloitte The representative I spoke with told me about Deloitte, a well-established company with a large workforce. I asked about the technologies they work with and the general opportunities available for an IT graduate. The answer was very expansive; they work in a wide variety of domains, including data analysis, cybersecurity, AI, app development, and technology consulting. I spoke with a recruiter at their booth, and this definitely seems like an organization I would consider working for in the future.

Friday (Day 10)

I spent the entire day organizing the user stories currently resolved by the POC. In total, 25 Jira work items were resolved during Sprint 0, so I marked them as such and moved the completed Jira tickets to the appropriate sprint. Furthermore, I worked on creating the GitHub pull requests and commits for the resolved Jira items.

Finally, I ended the day by working on the VitePress documentation page. I decided to move the hosting provider from GitHub Pages to Cloudflare Pages. I made this choice because GitHub Pages does not support private repositories on free accounts. Henceforth, the documentation lives on the following Cloudflare page: https://knowledgehub-aks.pages.dev.


New skills

  • Integration of the Notion API with the Slack bot
  • Participating in Agile/Scrum sprint planning and daily standups
  • Translating generic user stories into actionable Jira tickets
  • Deploying VitePress documentation to Cloudflare Pages

Useful data