Blog

On 04-12-2024 i went to the Tweakers Dev Summit, this was the first time that i would go to such event. I'm still a student, and went alone, i was very excited to go, but wasn't sure how easy it would be to talk to people i've never met. I had an goal of talking to at least 3 people at stands (between the presentations there was time to drink/talk to people). I've talked to some awesome people at: 1. The police 2. AIVD 3. Amsterdam municipality 4. NS (Dutch Railways) 5. DHL 6. A.S.R Health Insurance By talking to them i had 2 other goals: 1. Networking, connecting with them through LinkedIn 2. Finding a opportunity an internship for september 2025 I've found contact persons through the event at every one of those company's, except for the AIVD, and the NS, they needed me to contact them through their website. I've talked to some awesome at each one of those company's, and i'm pretty sure that i will apply to one of those company's soon. (it's a bit early to be applying for an internship that is over 10 month). The next time i will be attending such event, i want to talk to other visitiors aswell. I've also learned alot from the sessions, i've made an summary of each presentation i attended: Paula Januszkiewicz - Keynote - A look into the future / The role of AI in Cyber Security Operations Learnings: 1. Showed why testing the security of an system is very important, and how you can leverage AI by testing for security issues. 2. Showed how easy it is to spoof someone's phone number, she adviced us to warn people around us. This in combination with AI deepfakes would be even more concerning. 3. Every company needs an incident response plan, most company's don't have this. 4. Company's need to invest in the security knowledge of their employes Lucien Immink - Devops - Seamless collaboration unlocks design-first APIs for UI components See presentation: Presentation (presentation only seems to scroll on mobile) Learnings: 1. Presentation was mostly focust on the use of web components (Mozilla Docs Web Components). Webcomponents are seperate from frameworks, which would prevent dead-locks. 2. Before building an API, you woulf first needs to discuss the future of application, to prevent too much work later on. 3. Lucien is using Lit.dev to build web components. 4. Web components would be easy to use through different projects. 5. Web components is seperate from the website dom, in it's own shadowdom, so it will not be affected by too much of the layout. Daniel van Gils - Backend - Police - The power of speaking, writing, and understanding the same API language Well i'm current a more front-end focused developer, i also try to pickup back-end development. That's why i decided to attend this presentation. I tried my best to summarize it, but might not have understand everything. Learnings 1. They use the Meta-Information Modeling Model, MEM1 and MEM2. MEM1 focuses on the concepts and their semantics. They document all concepts to ensure they are established within the police organization. MEM2 translates this from MEM1 into data models, mainly discussing how it's applied in JSON and RDF. 2. They also use RDF (Resource Description Framework), which mainly focuses on Linked Data. RDF does everything in form of "trippels". 1. Subject, example: Evi Wammes 2. Predicate: Works at 3. Object: Yummygum RDF would have the advantage that, even if the data comes from different systems, they can still be linked together. Combined with the MEM principles, this would ensure effective communication. Wesley Neelen & Rik van Duijn - Privacy & Security - Lessons learned Learnings 1. 2FA codes are not good enough anymore. Use passkeys instead. 2. There are many ways scams are carried out nowadays, for example, to steal the authentication cookie. Authentication codes no longer matter in this context. There were some cool (and scary) examples, mostly focused on Office365. For Office365, they showed how a clone could send the authentication request to your Microsoft Authenticator app on your own domain, then grab the authentication cookie and redirect the user back to the real Office365 site. They expect this way of scamming will only increase with time. Rowdy Rabouw - Frontend - Offline first! (i found this the most interesting one) Presentation: Presentation Example website that leverages all mentioned techniques: Offline First Learnings 1. Use service workers to provide offline support, which can actually benefit any website. Why: If the user loses their internet connection, they can't use your site anymore, even if they've already visited a page. For example, this is very useful for events to check the schedule. 2. Configure prefetching in combination with service workers. When a link appears on the screen, prefetch it. If the user loses internet, they can still access this page. Even without images, having the text available is often very useful. 3. If the user is offline, you can display your own custom offline page. On this page, you can also show which pages you've cached, so the user can still navigate those parts of your website. 4. Since everything is cached in the browser, the website feels extra fast. It no longer needs to fetch the page from the server first. 5. With the service worker, you can specify which assets are always needed, such as the logo or certain pages. 6. There are various caching strategies that can be used. My favorite was "Cache Only - Cache Update." You first load the cached version but immediately check if a newer version is available. If there is, the content is replaced with the updated version.