Week 16 Recap: Finishing Strong And just like that, we've reached the final week! Week 16 was all about refining, polishing, and giving the finishing touches to an already awesome journey. This week, I focused on elevating the look and feel of the Admin Assistant—and the results turned out fantastic. With the help of Framer Motion, I added some smooth transition effects that really bring the UI to life. The entire redesign feels snappy and modern, and I have to give a big shoutout to Daryl for his helpful tips and support along the way. The visual polish wouldn’t have come together the way it did without his keen eye. Beyond the aesthetics, I also spent time improving code scalability and reusability—making sure that what we’ve built can grow and adapt smoothly in the future. It’s all in the details, and this week was a deep dive into those final layers of refinement. We’re ending this week strong—and with that, wrapping up the internship on a high note. It’s been an incredible ride from start to finish. This weekend, we’re capping things off with a fun obstacle course event with the team—one last chance to share some laughs and memories together (at least for now). To Twintag, and especially to Michiel, Daryl, Ramazan, and the rest of the amazing crew: Thank you. It’s been an honour and a pleasure to learn, grow, and create alongside all of you. I couldn’t have asked for a more supportive and inspiring environment. You’ve made this experience unforgettable. Here’s to great code, great people, and an even greater future! 🚀

Week 15 Recap: Wrapping Up with Style We’re nearing the finish line—and Week 15 was a big step toward it. The admin portal is almost complete now, and honestly, it looks amazing. Seeing the redesign come to life has been really rewarding, both visually and functionally. It’s modern, clean, and feels great to use. On the backend side, I finally rolled out the REST API changes to production 🎉. It’s now fully integrated and available for testing through a Swagger UI playground—super handy for anyone who wants to explore and interact with the endpoints directly. Liza’s been on a roll too: her demos are now live, all eight of them. They're slick, polished, and really help bring the product story to life. Great teamwork all around! Looking ahead to Week 16, it’s mostly about final touches. We’ll continue refining the admin portal and work on making the Twintag Assistant smarter and more helpful—especially when it comes to navigating and performing actions within the portal. One more week to go on this amazing journey. Let’s make it count.

Week 14 Recap: Bug Fixes, Design Wins & Demo Prep Week 14 was all about tightening things up—and we’re happy to report that the schema builder is officially in great shape. After a focused round of bug fixing, it's now running smoothly and reliably. It's always a good feeling when everything just clicks. In parallel, Daryl and I rolled up our sleeves and dove back into the admin portal redesign. It’s been exciting to see it evolve. The updated design is already giving off a much more modern, intuitive vibe. Bit by bit, it’s becoming the kind of tool that feels good to use—and that’s the goal. Looking ahead to Week 15, the spotlight shifts to demos. Liza is leading the charge here, crafting some slick demo flows using Loveable. Of course, the dev team is stepping in here and there to fine-tune the pieces that AI can’t (yet 😉) perfect on its own. We’ll also keep iterating on the admin portal—adding new features, refining designs, and keeping the momentum going. Week 15 is shaping up to be a nice mix of polish and progress. Stay tuned!

Week 13: Pushing Boundaries and Gaining Ground This was a week of rolling up my sleeves and diving into complexity—specifically, tackling the long-awaited upgrade of the Twintag Overview API. This isn’t a small job. The overview component is the beating heart of the admin portal, and its codebase is dense, sprawling across more than a thousand lines, with logic deeply rooted beyond the main file. It's the kind of project usually reserved for seasoned developers—and rightly so. Still, I leaned in. Progress was steady. Each small win taught me something new, particularly around GraphQL and the overall architecture behind the project. My work on the Golang code generator with a chatbot has concluded. This was a small dive into the possibilities of an agent within a project. It turned out great. With help of an article explaining the steps needed to be taken to code this project, I managed to have a working version by the end. Looking ahead, the API upgrade continues. Daryl and I will also be starting a much-needed revamp of the admin portal, aiming for a refreshed look and feel. There's also some cleanup to do: an old project of mine, the Schema Builder, has resurfaced with issues. I’ll be diving back in to diagnose and document the fix.

After a refreshing break, Week 12 came roaring back to life. Together with Daryl, we put in the hard work to prepare for an important client demo—and it paid off! The demo was a success, showcasing the real progress we've made and setting the stage for deeper client engagement. Beyond the demo, I started an exciting new initiative: building a code generator agent using GoLang. This is a big new step, laying the foundation for smarter automation and internal tooling that will push our capabilities even further. Development work has just begun, but the potential is already clear—and I'm thrilled to dive deeper into it in the coming weeks. Momentum is definitely building. After the calm of Week 11, Week 12 was a strong reminder of how far we’ve come—and how much further we can go.

Week 11 was a slower-paced chapter in this journey—and intentionally so. I took three days off to be in the church for Holy Week, preparing for Easter. It was a meaningful time to step back, recharge, and return with fresh energy. Even with the lighter schedule, I stayed on top of key responsibilities. I focused on following up on pending deployments in production, making sure that everything pushed live remained stable and on track. Thanks to the groundwork laid in previous weeks, this was a smooth and easygoing week, giving me space to reset before diving into the next big milestones. Sometimes, a quieter week is exactly what’s needed to gear up for the exciting pushes ahead—and Week 11 served that purpose perfectly.

This week marked a real turning point in the journey of integrating AI into the Twintag admin portal. With backend support now fully in place, the assistant has leveled up—not just a responder to questions, but a true operator within the platform. AI With Context and Control The assistant can now: Understand user queries with full context awareness Perform real actions inside the admin portal Navigate pages and automate steps within workflows It’s a huge step forward and sets the foundation for an even more capable assistant—one that’s not just helpful, but genuinely integrated into how users interact with Twintag. Continued Production Follow-Ups Alongside this leap, I continued supporting production efforts and doing final checks on past work—making sure everything is stable and running as expected in the live environment. What’s Next? Next week, I’ll focus on making the assistant more versatile and “uitgebreid”—expanding its capabilities, fine-tuning its responses, and exploring how it can adapt even more closely to user behavior. There’s a lot of potential, and I’m just getting started. The pieces are falling into place—and Week Ten wrapped up with real momentum. Let’s keep it rolling 🚀

Week Nine was all about setting the stage. As previewed last week, I started integrating the AI assistant into the Twintag admin portal. While the initial steps were smooth, some backend functionality still needed to be brought up to speed to support the full vision. Rather than twiddling my thumbs, I took the opportunity to double down on some housekeeping and support tasks. Tying Up Loose Ends I made sure all of my older tasks were pushed cleanly to production, squashing remaining bugs and doing quality checks. It felt good to see the earlier work being finalized and running live. Lending a Hand I also spent time helping out Ramazan, my teammate, with parts of his codebase—collaboration that’s always energizing. There’s something rewarding about stepping into someone else’s problem space and being able to offer clarity or support. Looking Ahead The backend should be fully prepped by next week, unlocking more in-depth assistant development. I’ve got ideas queued up, and I’m excited to dive back into more complex problem-solving once everything’s aligned. Sometimes progress isn’t about dramatic leaps—it’s about keeping things tidy and ready for the next big push.

Week Eight: Demos, Pivots, and an Exciting New AI Chapter This week marked a bit of a pivot. While the refinement of AI-generated GraphQL queries was temporarily put on hold, it was for a good reason—an important client demo was on the horizon. And I’m happy to say it wrapped up smoothly, with everything delivered on time and to a solid standard. The feedback loop has started, and it felt great to see things come together in a real-world context. Shifting Gears for the Client Demo With the demo deadline approaching, my focus shifted toward polishing the existing work, squashing minor bugs, and ensuring everything ran smoothly. From UI tweaks to functionality checks, the goal was to showcase not just what we’d built, but how it could deliver real value. It was a different pace from the deep technical work of last week, but equally rewarding. A Glimpse Into What’s Next: AI in the Admin Portal While the AI query generation is on pause for now, an even more exciting opportunity opened up toward the end of the week: integrating the AI assistant directly into the Twintag admin portal. This means making it a core part of the user experience—not just a cool side project. The vision? An assistant that can: Run GraphQL queries on behalf of users Navigate the platform intuitively Perform actions and automate workflows Possibly even adapt based on user behavior And that’s just the starting point. There’s plenty of room for creative ideas and experimentation as we move into Week Nine and beyond. Looking Ahead Next week kicks off this new phase. I’ll be diving into design, integration strategy, and exploring what’s possible with the current setup. It’s the kind of challenge I’ve been hoping for—complex, open-ended, and full of potential. Week Eight wrapped up with a solid win and a very promising roadmap. On to the next adventure! 🚀

Week Seven: Testing, Learning, and AI Exploration This week was all about diving into Golang testing, tackling a learning curve, and taking a big step towards AI-powered API interactions. While last week had its share of roadblocks, this one felt like steady progress—new skills, successful tests, and an exciting AI integration. Cracking the Golang Testing Process Testing in Golang was a fresh challenge. The syntax and structure were different from what I was used to, but by the end of the week, I had a solid grasp of it. Writing test cases, understanding best practices, and debugging in Go took some getting used to, but the payoff was worth it. Now, I have a more structured approach to testing and a deeper understanding of the language. AI Assistant + Schema Introspection = Smarter Queries Beyond testing, I worked on configuring an AI assistant within the Golang project. The goal? Enable it to perform schema introspection on the Twintag API. By analyzing the API structure, the assistant could generate GraphQL queries based on simple user keyword inputs. No need for manual query writing—just describe what you need, and the assistant figures it out. Seeing this come to life was definitely the highlight of the week. Looking Ahead: Refining AI Query Generation With the foundation in place, next week’s focus will be refining the AI’s query generation, optimizing its accuracy, and ensuring seamless integration. It’s a step toward making API interactions more intuitive and user-friendly. On top of that, I’ll be preparing a demo for a client project—showcasing what’s been built so far and gathering feedback for the next iteration. Week seven was all about learning, adapting, and building something meaningful. On to week eight! 🚀

Week six was a rollercoaster—big goals, tough realizations, and solid wins. The plan was to upgrade the rest of the admin UI to the new GraphQL API, but reality had other ideas. Turns out, the current architecture isn’t compatible with a smooth transition, and a full rewrite would be necessary. That’s way beyond a quick upgrade, so this goal had to be shelved for now. GraphQL Migration: A Tough Nut to Crack I started the week optimistic about bringing the entire admin UI onto the new GraphQL API. But as I got deeper into the integration, it became clear that the backend API endpoints simply didn’t align with the existing frontend structure. Trying to force compatibility would’ve been a losing battle—too many breaking changes, too much complexity. The best path forward? A complete rewrite, which is a much bigger discussion for later. Wins with REST API Playground & SchemaBuilder Despite the GraphQL setback, there were still some big wins. The REST API playground and SchemaBuilder upgrade both made it to testing and production. These improvements give developers more flexibility when exploring API endpoints and refining schemas, making development smoother. It’s always satisfying to push meaningful upgrades live, even when other plans don’t go as expected. Looking Ahead: Testing in Go With week six wrapped up, my focus now shifts to testing in Golang. First up: getting familiar with the language, understanding its syntax, and exploring testing frameworks before jumping into actual code. It’s a new challenge, but I’m excited to dive in. Not every week goes as planned, but every challenge brings new insights. On to week seven!

Week Five at Twintag: Pushing GraphQL Upgrades to Production Week five was all about persistence, problem-solving, and wrapping up key milestones. After diving deep into Twintag’s GraphQL API upgrade last week, this week was about seeing those efforts come to life. Although the start was slow, we finished strong, making significant progress on both the frontend and backend. Tackling Backend Limitations One of the biggest challenges I faced this week was implementing a part of the GraphQL upgrade on a specific page. Initially, the backend wasn’t fully supporting the frontend, which meant I had to navigate around limitations before making meaningful progress. However, by the end of the week, everything was aligned, and we successfully implemented the upgrade—unlocking better performance and efficiency for that page. GraphQL Playground Goes Live Another big win this week was pushing the GraphQL playground section to production for the admin UI. This feature, which I started developing last week using the GraphiQL package, is now live and available for developers to test queries, explore our API, and debug issues more efficiently. It’s a crucial step in making our API more accessible and easier to work with. A Strong Finish & Looking Ahead to Week Six Despite the slow start, we wrapped up week five on a high note. The GraphQL upgrade is progressing well, and the playground is now in production. But there’s still more work ahead! In week six, we’ll continue upgrading the API, refining performance, and implementing an OpenAPI playground for our REST API—similar to what we did with GraphQL. This will provide a unified, interactive way to explore and test endpoints, making development even smoother. Five weeks in, and every challenge brings a new learning experience. Excited for what’s next!

Week Four at Twintag: Upgrading the GraphQL API for a More Scalable Future Week four was all about performance, scalability, and stepping into a more backend-heavy role. After spending the last two weeks focusing on Angular and UI enhancements, this week I shifted gears to work on Twintag’s GraphQL API upgrade—something that will play a crucial role in making the platform faster and more efficient in the long run. Enhancing Query Performance with GraphQL My main focus this week was upgrading our API from a beta version to v1. This upgrade is a game-changer for Twintag, making data fetching faster, reducing unnecessary queries, and improving overall scalability. GraphQL’s flexibility makes it a powerful choice for our system, but optimizing it for performance required careful planning and execution. Some key improvements included: Reducing Over-Fetching: By fine-tuning our queries, we ensured that clients only retrieve the data they need, leading to faster load times and reduced backend strain. Efficient Caching Strategies: Implementing smart caching mechanisms to enhance response times and minimize redundant requests. Building a GraphQL Playground with React To make testing and development smoother, I also built an interactive GraphQL playground using the GraphiQL package. This playground allows developers to experiment with queries, see real-time responses, and debug issues more efficiently. Having worked extensively with React before, this was a great opportunity to bring my frontend expertise into play while working on API improvements. A Full-Stack Experience This week was a fantastic blend of frontend and backend work, allowing me to see how different parts of Twintag’s ecosystem fit together. It reinforced the importance of performance optimization and scalability in building a robust platform. Continuing into Week Five The GraphQL upgrade is a big project, and I’ll be continuing this work into next week. There’s still more optimization to be done, and I’m excited to see how these changes will impact Twintag’s performance in the long run. Four weeks in, and every day brings new learnings and challenges. Can’t wait to see what’s next!

Week Three at Twintag: Diving Deep into the Admin-UI and Building for Efficiency Week three at Twintag has been all about getting my hands dirty with the Admin-UI—really digging into the platform and working on meaningful changes that enhance how users interact with it. If week two was about stepping out of my comfort zone, this week was about pushing forward with confidence and making real improvements. Implementing Faster Object and Column Creation One of the major features I worked on this week was an enhancement to how objects and columns are created within the Admin-UI. The goal? Make the process faster, more intuitive, and ultimately improve the efficiency of the platform. This was my first deep dive into making larger structural changes in Twintag’s internal system, and it came with its fair share of challenges. Since the Admin-UI is built in Angular, I had to refine my understanding of its component structure and state management. Working with dependency injection and reactive forms, I implemented a more seamless way for users to generate and configure objects dynamically. The result was a smoother, more streamlined process that eliminates unnecessary steps and allows for faster data manipulation. Going Deeper into Angular This week really solidified my Angular knowledge. I started seeing patterns more clearly—how services interact, how data flows through components, and how to optimize state changes for better performance. Concepts that felt foreign in week two now started clicking into place, and I even found myself refactoring older implementations to make them more efficient. Learning Through Doing What I appreciate most about Twintag is the balance between guidance and autonomy. While I had the team to support me whenever I hit roadblocks, I was also given the freedom to experiment and iterate on solutions. Every bug I fixed and every feature I implemented made me more confident in my ability to contribute meaningfully. Looking Ahead As I continue working on the Admin-UI, I’m excited to refine this new feature even further and explore more ways to optimize workflows within the platform. Week four is going to be an interesting shift—while I’ll still be working on UI improvements, I’ll also be diving into backend optimizations with GraphQL. More learning, more challenges, and more impact—can’t wait!

My Second Week at Twintag: Learning, Experimenting, and Making an Impact 🌟 The second week of a new job is always an interesting phase—you’re no longer the “new person” figuring out where the coffee machine is, but you’re still getting the hang of the workflows, tools, and codebase. At Twintag, this week has been all about diving deeper into the internal platform and pushing myself to learn something new while still delivering value. Familiarizing Myself with the Twintag Platform One of the key focuses of my second week was getting up to speed with Twintag’s internal platform, specifically the Admin-UI. It’s an integral part of the company’s ecosystem, and to work on it effectively, I needed to get comfortable with the platform’s architecture, the backend endpoints, and the coding conventions that the team follows. Rather than just passively learning, my tasks were designed to be hands-on. I was encouraged to experiment and explore, but also to create something that could make a tangible impact on the Admin-UI. It’s a great balance—learning through doing, while still contributing in a meaningful way. Stepping Out of My Comfort Zone with Angular While my main stack is React and TypeScript, working on the Admin-UI required me to learn Angular—a framework I hadn’t worked with extensively before. At first, it felt a little daunting, but Twintag’s supportive environment made it easier to tackle the learning curve. Angular has its quirks, and transitioning from React meant rethinking how I approach certain problems. Dependency injection, TypeScript-heavy configurations, and two-way data binding were just a few of the concepts I had to wrap my head around. But honestly? It’s been really rewarding to step out of my comfort zone and see myself grow as a developer. Making an Impact Through Experimentation Twintag’s approach to onboarding is refreshingly different. Rather than just assigning busy work, they trusted me with tasks that allowed me to explore the platform while also delivering value. My experiments were focused on identifying areas of improvement in the Admin-UI, and I’ve already started implementing some small but useful tweaks. For instance, I worked on improving usability for a specific feature within the platform by tweaking its interface and optimizing how data is displayed. These might seem like small changes, but they can make a big difference in user experience. It’s fulfilling to know that even as I’m still learning the ropes, my work is actively contributing to the platform’s evolution. Reflections and Lessons This week reinforced the idea that growth often happens outside your comfort zone. Tackling Angular was a challenge, but it was also an opportunity to broaden my skill set and contribute to a new area of Twintag’s ecosystem. The freedom to experiment while making an impact has been a great way to stay motivated and engaged. Twintag’s culture of learning and collaboration has been a huge help—I never felt alone in navigating the codebase or asking questions about Angular. The team is always ready to support, which has made a world of difference. What’s Next? As I continue working on the Admin-UI, I’m looking forward to diving even deeper into Angular and exploring more opportunities to optimize and enhance the platform. I’m also eager to tackle more client-facing tasks and learn how the different pieces of Twintag’s ecosystem fit together. Week two has been all about discovery and growth, and I’m excited to see what week three will bring. Stay tuned for more updates as I keep building, experimenting, and learning!

My First Week at Twintag as a Frontend Developer 🚀 Starting a new job always comes with a mix of excitement and nerves, but my first week at Twintag as a frontend developer has been nothing short of amazing. From diving into real-world projects to contributing to cutting-edge internal tools, this week has been an exciting whirlwind of learning and creating. Jumping Right Into the Action From day one, I was handed meaningful work, which made me feel like a valuable part of the team right away. My main stack at Twintag is React and TypeScript, so I felt right at home coding—but what really made the week stand out was the variety of projects I got to work on. Let me walk you through them. Delivering for a Client: My First Deployment One of the highlights of the week was working on a project for one of Twintag’s clients. It’s always a bit nerve-wracking deploying code to production—especially when it’s your first week! But I was entrusted with this responsibility, which shows just how much confidence the team has in each other. After writing and testing the code, I successfully deployed it to production. That moment of seeing my work live in the real world? Priceless. It’s an incredible feeling knowing something I built is out there making an impact. Innovating with the Twin AI Assistant Another project I worked on this week was for Twintag’s internal product—the Twin AI Assistant. This chatbot is designed to make interacting with data and products more intuitive, and I had the opportunity to introduce a couple of cool features: Starter Questions for Better Engagement I implemented a feature where the assistant now prompts users with basic starter questions. This helps guide conversations, especially for users who aren’t sure where to begin. Context-Specific Knowledge To make the assistant smarter, I added functionality for giving it product-specific context. Depending on the product the chatbot is linked to, it can now provide tailored answers to user questions. This makes the assistant not just a helpful tool, but a truly contextual one, improving the overall user experience. It felt amazing to contribute to something so innovative and to see how even small tweaks can make a huge difference in usability and functionality. Reflections on Week One Looking back on this week, I feel grateful for the opportunity to make an immediate impact. It’s not every day you get to work on both external client projects and internal tools within your first week at a company. I’m also incredibly impressed by Twintag’s supportive culture—everyone here has been approachable and ready to lend a hand whenever I’ve had questions. I’m excited to keep building, learning, and contributing to both our clients’ success and Twintag’s own products. If this first week is any indication of what’s to come, I know this is going to be an amazing journey.