Routizer

routizer

Authors:
(1) Benzar Glen S. Grepon, Northern Bukidnon State College, Philippines ben.it2c@gmail.com (corresponding author);
(2) JC P. Margallo, Northern Bukidnon State College, Philippines;
(3) Jonathan B. Maserin, Northern Bukidnon State College, Philippines;
(4) Rio Al-Di A. Dompol, Northern Bukidnon State College, Philippines. Table of Links Abstract and Intro Literature Review Methodology Results Discussions Conclusions Recommendations Research Implications Practical Implications Declarations References and Author's Biography METHODOLOGY Software Development Over the years, SDLC has remained the reliable approach to software development (Khan et al., 2020). The Agile technique, as indicated in Figure 1, is ideally suited for speedy and effective software development due to its adaptive nature, early delivery, and flexible lifecycle (Srivastava, Bhardwaj & Saraswat, 2017). Planning The researchers obtained data in a Municipality of Bukidnon. They examined the typical issues they ran into. According to the report, many people have accidents because they lack information; thus, they require information to warn them of accident-prone areas, roadblocks, and on-going construction. Requirements Analysis To analyze the requirements using some of the many system flow diagrams and flow charts available. Data flow diagrams are used to represent the flow and to help advocates better understand how to put systems into place and ensure that data is flowing accurately. Additionally, flowcharts are used to demonstrate the system's process, which aids the proponents in making clear how things will operate. The process that needs to be carried out in an operation is depicted using a flowchart as a series of steps. Design In this phase, the researcher plans to make a good design for the project. The researcher surveyed random riders and commuters to gather data information to collect the essential needs of this system. The proponents came up with a functional design of the Network Infrastructure, a framework for the specification of a network's physical components and their functional organization and configuration; the System Architecture, which is the conceptual model that defines the structure, behavior, and more views of a system, the Database Model that determines the logical structure of a database and fundamentally determines in which manner data can be stored. Coding In this phase, the development and writing of the actual code, the researcher uses WordPress to develop web apps; WordPress is the most popular open-source Content Management System (CMS), used by approximately 75 million websites. The researcher studied the hypertext processor (PHP) as the programming language used for web development. The researcher also uses CSS cascading style sheets for creative design to look better. Lastly is JavaScript (JS) for animation and interaction. User Testing The researcher must repeat this procedure until no errors are identified in the functionality of the software development at this stage, where it involves the designing and coding processes. Acceptance for the Client The researchers presented the output web application to propose a random user for acceptance through mobile browser demonstration with System Evaluation Scale (SUS). A mobile browser demonstration will be used as the introductory and brief flow of the application. System Testing and Evaluation During the evaluation of the regular users, it gives the feedback score about the system of the final output. ISO/IEC 25010 is used for the application evaluation assigned to the participants because this ISO Standard provides a uniform vocabulary for defining, assessing, and comparing the quality of systems and software products. Table 1. The Likert table for qualitative interpretation is used in interpreting the results of the survey. Formula: Over-all Average = Total Average/Total Number of Items Equation 1 Table 2 is the ISO overall result for the application quality evaluation. By getting the total average, the researchers used the following formula. This paper is available on arxiv under CC 4.0 license. Authors: (1) Benzar Glen S. Grepon, Northern Bukidnon State College, Philippines ben.it2c@gmail.com (corresponding author); (2) JC P. Margallo, Northern Bukidnon State College, Philippines; (3) Jonathan B. Maserin, Northern Bukidnon State College, Philippines; (4) Rio Al-Di A. Dompol, Northern Bukidnon State College, Philippines. Authors: Authors: (1) Benzar Glen S. Grepon, Northern Bukidnon State College, Philippines ben.it2c@gmail.com (corresponding author); (2) JC P. Margallo, Northern Bukidnon State College, Philippines; (3) Jonathan B. Maserin, Northern Bukidnon State College, Philippines; (4) Rio Al-Di A. Dompol, Northern Bukidnon State College, Philippines. Table of Links Abstract and Intro Abstract and Intro Literature Review Literature Review Methodology Methodology Results Results Discussions Discussions Conclusions Conclusions Recommendations Recommendations Research Implications Research Implications Practical Implications Practical Implications Declarations Declarations References and Author's Biography References and Author's Biography METHODOLOGY Software Development Software Development Over the years, SDLC has remained the reliable approach to software development (Khan et al., 2020). The Agile technique, as indicated in Figure 1, is ideally suited for speedy and effective software development due to its adaptive nature, early delivery, and flexible lifecycle (Srivastava, Bhardwaj & Saraswat, 2017). Planning Planning The researchers obtained data in a Municipality of Bukidnon. They examined the typical issues they ran into. According to the report, many people have accidents because they lack information; thus, they require information to warn them of accident-prone areas, roadblocks, and on-going construction. Requirements Analysis Requirements Analysis To analyze the requirements using some of the many system flow diagrams and flow charts available. Data flow diagrams are used to represent the flow and to help advocates better understand how to put systems into place and ensure that data is flowing accurately. Additionally, flowcharts are used to demonstrate the system's process, which aids the proponents in making clear how things will operate. The process that needs to be carried out in an operation is depicted using a flowchart as a series of steps. Design Design In this phase, the researcher plans to make a good design for the project. The researcher surveyed random riders and commuters to gather data information to collect the essential needs of this system. The proponents came up with a functional design of the Network Infrastructure, a framework for the specification of a network's physical components and their functional organization and configuration; the System Architecture, which is the conceptual model that defines the structure, behavior, and more views of a system, the Database Model that determines the logical structure of a database and fundamentally determines in which manner data can be stored. Coding Coding In this phase, the development and writing of the actual code, the researcher uses WordPress to develop web apps; WordPress is the most popular open-source Content Management System (CMS), used by approximately 75 million websites. The researcher studied the hypertext processor (PHP) as the programming language used for web development. The researcher also uses CSS cascading style sheets for creative design to look better. Lastly is JavaScript (JS) for animation and interaction. User Testing User Testing The researcher must repeat this procedure until no errors are identified in the functionality of the software development at this stage, where it involves the designing and coding processes. Acceptance for the Client Acceptance for the Client The researchers presented the output web application to propose a random user for acceptance through mobile browser demonstration with System Evaluation Scale (SUS). A mobile browser demonstration will be used as the introductory and brief flow of the application. System Testing and Evaluation System Testing and Evaluation During the evaluation of the regular users, it gives the feedback score about the system of the final output. ISO/IEC 25010 is used for the application evaluation assigned to the participants because this ISO Standard provides a uniform vocabulary for defining, assessing, and comparing the quality of systems and software products. Table 1. The Likert table for qualitative interpretation is used in interpreting the results of the survey. Formula: Over-all Average = Total Average/Total Number of Items Equation 1 Over-all Average = Total Average/Total Number of Items Equation 1 Table 2 is the ISO overall result for the application quality evaluation. By getting the total average, the researchers used the following formula. This paper is available on arxiv under CC 4.0 license. This paper is available on arxiv under CC 4.0 license. available on arxiv

An Agile Approach to Developing Accurate Navigation Systems for Road Safety

সড়ক নিরাপত্তার জন্য সঠিক নেভিগেশন সিস্টেম বিকাশে চটপটে দৃষ্টিভঙ্গি

Agiler Ansatz bei der Entwicklung präziser Navigationssysteme für die Verkehrssicherheit

Enfoque ágil en el desarrollo de sistemas de navegación precisos para la seguridad vial

Approche agile dans le développement de systèmes de navigation précis pour la sécurité routière

सड़क सुरक्षा के लिए सटीक नेविगेशन सिस्टम विकसित करने में चुस्त दृष्टिकोण

道路安全のための正確なナビゲーション システムの開発におけるアジャイル アプローチ

도로 안전을 위한 정확한 내비게이션 시스템 개발에 대한 민첩한 접근 방식

Abordagem Ágil no Desenvolvimento de Sistemas de Navegação Precisos para Segurança Rodoviária

Гибкий подход к разработке точных навигационных систем для обеспечения безопасности дорожного движения

Yol Güvenliği İçin Doğru Navigasyon Sistemlerinin Geliştirilmesinde Çevik Yaklaşım

Phương pháp tiếp cận linh hoạt trong việc phát triển hệ thống định vị chính xác cho an toàn đường bộ

敏捷方法开发道路安全精确导航系统

Markus Lanieux Fled a Traffic Stop - He's Now Doing Life in Prison

Markus Lanieux একটি ট্রাফিক স্টপ পালিয়ে গেছে - তিনি এখন কারাগারে জীবন করছেন

Markus Lanieux floh vor einer Verkehrskontrolle – jetzt sitzt er im Gefängnis

Markus Lanieux escapó de una parada de tráfico y ahora cumple cadena perpetua

Markus Lanieux a fui un contrôle routier – il purge désormais une peine de prison à vie

मार्कस लैनियक्स ट्रैफिक स्टॉप से भाग गया - वह अब जेल में जीवन बिता रहा है

マルクス・ラニュー、交通停止から逃走 - 現在は刑務所で暮らしている

Markus Lanieux는 교통 정체를 피해 도망쳤으며 현재 감옥에서 생활하고 있습니다.

Markus Lanieux fugiu de uma parada de trânsito - agora ele está cumprindo prisão perpétua

Маркус Ланье сбежал с остановки и теперь ведет жизнь в тюрьме

Markus Lanieux Trafik Durdurmasından Kaçtı - Şimdi Müebbet Hapis Cezasında

Markus Lanieux Chạy trốn khỏi điểm dừng giao thông - Anh ta hiện đang sống trong tù

马库斯·拉尼厄克斯 (Markus Lanieux) 逃离了交通堵塞 - 他现在在监狱里过着生活

Each time I read about a crypto hack on the internet, I usually heave a sigh of disappointment. I always ask myself whether there will ever be an end to the alarming rate of cyber attacks on blockchain protocols. For every crypto hack that has occurred, it feels like the cryptocurrency industry has taken ten steps backward, undermining its progress and worsening the industry’s image problem. Apparently, crypto hacks happen not because there are no effective cyber security measures in place but because they are either not enough or they are currently outpaced. Developing a superior cybersecurity technology must be seen as a race to beat hackers to their own game, and further improvements are required to match their tactics for tactics, so much so that cybersecurity technologies must be ten steps ahead of cyber threats. In this article, I will be delving into the efficacy of smart contract audits, highlighting the significance of a routine audit and the convergence of various approaches that are tailored towards a safer blockchain ecosystem. What Are Smart Contracts? Smart contracts are pieces of self-executing computer programs on a blockchain. They are designed to function when a particular set of conditions are fulfilled (i.e., minting an NFT), and the ultimate purpose they serve is to cut off intermediaries. It is hard to imagine today's world of decentralized applications(DApps) without its functionalities. However, deploying it on a blockchain protocol comes with potential risks. In other words, they are vulnerable to cyber attacks such as DOS attacks, phishing, flash loan attacks, and rentrancy attacks. One of the earliest events that proved that blockchain technology is not the gold standard for cybersecurity involved a smart contract. Many people remember this event as the infamous DAO hack, which happened in 2016 after hackers exploited a flaw in the code and stole over $50 million. The most recent example of this type of exploit is the Normie memecoin hack, which took place on the 26th of May 2024. This exploit not only resulted in the loss of over $800,000  but also saw the market capitalization of the memecoin slump to $35,000 from $41 million in a matter of days. Why Do Smart Contract Hacks Occur? There are bad actors in every dark corner of the web. Smart contract hacks occur because hackers are able to identify and exploit the vulnerabilities of a smart contract. In most cases, they are written by humans, making them prone to errors that hackers usually exploit. In another instance, hackers do this by tricking unsuspecting users into interacting with a malicious smart contract in order to steal their funds. Combating Smart Contract Hacks Blockchain protocols continue to suffer heavy financial loss due to the recurring exploit. To address this menace, a regular smart contract audit is usually recommended by cyber security experts. While this security measure might offer a semblance of efficacy, obtaining an audit certificate has never turned out to be the most assuring safety measure. As a matter of fact, a one-off audit is never enough because experience has shown that it must be carried out from time to time. Furthermore, the DeFi landscape has witnessed significant advances in blockchain security with the emergence of AI, so much so that AI is increasingly becoming a viable tool in the detection of anomalies. Leveraging AI can further enhance the ability of professional auditors to carry out a thorough risk assessment because it raises the bar for audit technology and reduces the dependence on the traditional manual process. The Significance of  Smart Contract Audit Auditing smart contracts is the process of running checks on the code to discover potential security flaws. While it is not the ultimate measure, it has grown in importance over the years, especially with the rise of professional audit firms. Regularly checking for vulnerability is an industry-standard procedure justified by collective wisdom: prevention is better than cure. It is also a reminder that cyber threats are always lurking around the corner. Most importantly, there is a need for blockchain protocols to diversify their cybersecurity strategies so that a regular audit is combined with other evolving techniques, such as artificial intelligence(AI). Commenting on the importance of a regular smart contract auditing UBET Sports CEO Daniel Jiwoong. Im said: “Smart contract auditing is essential for platform like UBET Sports operating in the decentralized finance (DeFi) space. These audits identify and mitigate security vulnerabilities that could be exploited by malicious actors, safeguarding user assets and maintaining the platform's integrity. Regular audits also build trust and confidence among users, reassuring them that the platform has been rigorously tested and verified by independent experts.” “Recently, UBET Sports underwent three comprehensive smart contract audits, demonstrating its commitment to security and reliability. The first audit coincided with the launch of UBET Sports' decentralized exchange (DEX) for sports betting, establishing a secure foundation. Subsequent audits focused on enhancing the Automated Market Maker (AMM) to improve slippage, optimizing gas fees, improving push settlements, and structuring revenue-sharing mechanisms for liquidity provision, ”he added. Is a routine smart contract audit worth it? “Building an on-chain product presents challenges, such as the need for audits before each release, preventing continuous integration and deployment. Despite these challenges and the high costs associated with multiple audits, we prioritized security to protect its users. With two more smart contract updates planned this year, we continue to make steady progress in the SportiFi space, merging sports and DeFi” Daniel further said. Conclusion Billions of dollars have been lost over the years to crypto hacks perpetrated by bad actors. Smart contract vulnerability can give rise to a potential hack, which can, in turn, undermine a blockchain protocol and drain the funds of its users. Promoting a secure blockchain ecosystem has been at the heart of every cybersecurity measure, like smart contract audits that are designed to combat the incidence of cyber-attacks. A smart contract audit, which typically involves a detailed examination of a protocol’s codebase, has been recognized as one of the standard techniques for combating potential crypto hacks. It has increasingly become a significant practice in blockchain security with the emergence of professional audit firms and sophisticated tools. Each time I read about a crypto hack on the internet, I usually heave a sigh of disappointment. I always ask myself whether there will ever be an end to the alarming rate of cyber attacks on blockchain protocols. For every crypto hack that has occurred, it feels like the cryptocurrency industry has taken ten steps backward, undermining its progress and worsening the industry’s image problem. Apparently, crypto hacks happen not because there are no effective cyber security measures in place but because they are either not enough or they are currently outpaced. Developing a superior cybersecurity technology must be seen as a race to beat hackers to their own game, and further improvements are required to match their tactics for tactics, so much so that cybersecurity technologies must be ten steps ahead of cyber threats. In this article, I will be delving into the efficacy of smart contract audits, highlighting the significance of a routine audit and the convergence of various approaches that are tailored towards a safer blockchain ecosystem. What Are Smart Contracts? Smart contracts are pieces of self-executing computer programs on a blockchain. They are designed to function when a particular set of conditions are fulfilled (i.e., minting an NFT), and the ultimate purpose they serve is to cut off intermediaries. It is hard to imagine today's world of decentralized applications(DApps) without its functionalities. However, deploying it on a blockchain protocol comes with potential risks. In other words, they are vulnerable to cyber attacks such as DOS attacks, phishing, flash loan attacks, and rentrancy attacks. One of the earliest events that proved that blockchain technology is not the gold standard for cybersecurity involved a smart contract. Many people remember this event as the infamous DAO hack, which happened in 2016 after hackers exploited a flaw in the code and stole over $50 million. The most recent example of this type of exploit is the Normie memecoin hack, which took place on the 26th of May 2024. This exploit not only resulted in the loss of over $800,000  but also saw the market capitalization of the memecoin slump to $35,000 from $41 million in a matter of days. Why Do Smart Contract Hacks Occur? There are bad actors in every dark corner of the web. Smart contract hacks occur because hackers are able to identify and exploit the vulnerabilities of a smart contract. In most cases, they are written by humans, making them prone to errors that hackers usually exploit. In another instance, hackers do this by tricking unsuspecting users into interacting with a malicious smart contract in order to steal their funds. Combating Smart Contract Hacks Blockchain protocols continue to suffer heavy financial loss due to the recurring exploit. To address this menace, a regular smart contract audit is usually recommended by cyber security experts. While this security measure might offer a semblance of efficacy, obtaining an audit certificate has never turned out to be the most assuring safety measure. As a matter of fact, a one-off audit is never enough because experience has shown that it must be carried out from time to time. Furthermore, the DeFi landscape has witnessed significant advances in blockchain security with the emergence of AI, so much so that AI is increasingly becoming a viable tool in the detection of anomalies. Leveraging AI can further enhance the ability of professional auditors to carry out a thorough risk assessment because it raises the bar for audit technology and reduces the dependence on the traditional manual process. The Significance of  Smart Contract Audit Auditing smart contracts is the process of running checks on the code to discover potential security flaws. While it is not the ultimate measure, it has grown in importance over the years, especially with the rise of professional audit firms. Regularly checking for vulnerability is an industry-standard procedure justified by collective wisdom: prevention is better than cure. It is also a reminder that cyber threats are always lurking around the corner. Most importantly, there is a need for blockchain protocols to diversify their cybersecurity strategies so that a regular audit is combined with other evolving techniques, such as artificial intelligence(AI). Commenting on the importance of a regular smart contract auditing UBET Sports CEO Daniel Jiwoong. Im said: “Smart contract auditing is essential for platform like UBET Sports operating in the decentralized finance (DeFi) space. These audits identify and mitigate security vulnerabilities that could be exploited by malicious actors, safeguarding user assets and maintaining the platform's integrity. Regular audits also build trust and confidence among users, reassuring them that the platform has been rigorously tested and verified by independent experts.” “Smart contract auditing is essential for platform like UBET Sports operating in the decentralized finance (DeFi) space. These audits identify and mitigate security vulnerabilities that could be exploited by malicious actors, safeguarding user assets and maintaining the platform's integrity. Regular audits also build trust and confidence among users, reassuring them that the platform has been rigorously tested and verified by independent experts.” “Recently, UBET Sports underwent three comprehensive smart contract audits, demonstrating its commitment to security and reliability. The first audit coincided with the launch of UBET Sports' decentralized exchange (DEX) for sports betting, establishing a secure foundation. Subsequent audits focused on enhancing the Automated Market Maker (AMM) to improve slippage, optimizing gas fees, improving push settlements, and structuring revenue-sharing mechanisms for liquidity provision, ”he added. “Recently, UBET Sports underwent three comprehensive smart contract audits, demonstrating its commitment to security and reliability. The first audit coincided with the launch of UBET Sports' decentralized exchange (DEX) for sports betting, establishing a secure foundation. Subsequent audits focused on enhancing the Automated Market Maker (AMM) to improve slippage, optimizing gas fees, improving push settlements, and structuring revenue-sharing mechanisms for liquidity provision, ”he added. Is a routine smart contract audit worth it? “Building an on-chain product presents challenges, such as the need for audits before each release, preventing continuous integration and deployment. Despite these challenges and the high costs associated with multiple audits, we prioritized security to protect its users. With two more smart contract updates planned this year, we continue to make steady progress in the SportiFi space, merging sports and DeFi” Daniel further said. “Building an on-chain product presents challenges, such as the need for audits before each release, preventing continuous integration and deployment. Despite these challenges and the high costs associated with multiple audits, we prioritized security to protect its users. With two more smart contract updates planned this year, we continue to make steady progress in the SportiFi space, merging sports and DeFi” Daniel further said. Conclusion Conclusion Billions of dollars have been lost over the years to crypto hacks perpetrated by bad actors. Smart contract vulnerability can give rise to a potential hack, which can, in turn, undermine a blockchain protocol and drain the funds of its users. Promoting a secure blockchain ecosystem has been at the heart of every cybersecurity measure, like smart contract audits that are designed to combat the incidence of cyber-attacks. A smart contract audit, which typically involves a detailed examination of a protocol’s codebase, has been recognized as one of the standard techniques for combating potential crypto hacks. It has increasingly become a significant practice in blockchain security with the emergence of professional audit firms and sophisticated tools.

The Importance Of a Routine Smart Contract Audit In Blockchain Security

A brief history of my journey with vue-router Virtually every developer using Vue.js is currently using or has only ever used Vue-router. Many of those developers, myself included, are mostly happy with it. The biggest complaint I hear is the lack of strongly typed routes, which is usually solved with a bit of Typescript wrapping your routes. // router/routes.ts
import { RouteLocationRaw, RouteRecordRaw } from 'vue-router'

type RouteFunction = (...args: any[]) => RouteLocationRaw

export const routes = {
  home: () => ({ name: 'home' }) as const,
  club: (clubId: string) => ({ name: 'clubs.view', params: { clubId } }) as const,
  profile: (userId?: string) => ({ name: 'profile.view', query: { userId } }) as const,
} satisfies Record<string, RouteFunction> Then routes becomes your source of truth, so navigation should always use a route from routes to send proper names to vue-router. <router-link :to="routes.club('club-123')">go to club</router-link> The syntax of defining routes is a bit cumbersome but honestly works fairly well. However, because I’m a serial starter-of-new-projects and love a challenge, I teamed up with Pleek91 to see if we could build our own. Introducing Kitbag Router https://router.kitbag.dev We made the decision to start the project from scratch; solving problems from first principles rather than taking the path of so many others and trying to build on top of the relatively old vue-router project. This means Kitbag Router is NOT a drop-in replacement for projects using vue-router. Therefore, this freedom also means we can have a relentless pursuit of the best possible developer experience, not weighed down by the need to have feature parity with Vue-router. Let’s take a look at some of Kitbag’s features First and foremost, it’s type safe! Kitbag Router uses a createRoutes utility that returns routes with the name, path, and query, all preserved in the Route type. This means the routes you provide to createRouter will maintain type safety when accessing the current route or performing navigation. Type safety in routing means auto-complete when assigning to on <router-link>, the easy discovery of available routes when defining a beforeRouteEnter hook, and ensuring that Typescript will error if the expected params for a route change without updating the router.push() call. Params are way more powerful Not only does Kitbag Router know what params are expected for a given route, it can also support param types beyond String. Kitbag Router ships with built-in support for params of typeString, Number, Boolean, Date, RegExp, JSON, as well as any custom param type you define. Not only is this type useful when navigating, but it also means a route that expects a number for an “id” param won’t be considered a match if the value provided in the URL doesn’t satisfy the number constraint. Furthermore, your Vue component that gets rendered for the route doesn’t have to worry about whether the param will be present or not or having to convert it from string to the type we know it’s supposed to be. Support for the query Params aren’t relegated to only the path. Kitbag Router allows you to configure your expected params in the query the same way you’re used to defining params in other parts of the URL. Handling rejections Inevitably when defining your routes, you’ll want to add a “catch-all” or “not found” route. While Kitbag Router fully supports defining plain ol’ Regex in your path/query, it also ships with even better support for handling NotFound. We call this a “rejection”, which is customizable and can be extended to any custom rejection you need, like perhaps NotAuthorized. When a rejection is triggered, usually from within one of your hooks, the Kitbag Router will automatically render the rejection component you assigned for the given rejection type. And more… These are the key features we think really make Kitbag Router compelling but there is so much more. Kitbag router is built for Vue3 and supports async components, route hooks, editable params from useRoute, components for RouterLink and RouterView, and more. Is it ready? Kitbag Router is still super green and currently maintained by a team of 2. It has not yet had a stable release (on 0.2.0 as of the time I’m writing this), so things are still likely to change. That being said, I hope you’ll give it a try, maybe give it a star. We’re excited to hear from the community on what features we should focus on next. Happy engineering! A brief history of my journey with vue-router Virtually every developer using Vue.js is currently using or has only ever used Vue-router. Many of those developers, myself included, are mostly happy with it. The biggest complaint I hear is the lack of strongly typed routes, which is usually solved with a bit of Typescript wrapping your routes. Vue.js // router/routes.ts
import { RouteLocationRaw, RouteRecordRaw } from 'vue-router'

type RouteFunction = (...args: any[]) => RouteLocationRaw

export const routes = {
  home: () => ({ name: 'home' }) as const,
  club: (clubId: string) => ({ name: 'clubs.view', params: { clubId } }) as const,
  profile: (userId?: string) => ({ name: 'profile.view', query: { userId } }) as const,
} satisfies Record<string, RouteFunction> // router/routes.ts
import { RouteLocationRaw, RouteRecordRaw } from 'vue-router'

type RouteFunction = (...args: any[]) => RouteLocationRaw

export const routes = {
  home: () => ({ name: 'home' }) as const,
  club: (clubId: string) => ({ name: 'clubs.view', params: { clubId } }) as const,
  profile: (userId?: string) => ({ name: 'profile.view', query: { userId } }) as const,
} satisfies Record<string, RouteFunction> Then routes becomes your source of truth, so navigation should always use a route from routes to send proper names to vue-router. routes routes <router-link :to="routes.club('club-123')">go to club</router-link> <router-link :to="routes.club('club-123')">go to club</router-link> The syntax of defining routes is a bit cumbersome but honestly works fairly well. However, because I’m a serial starter-of-new-projects and love a challenge, I teamed up with Pleek91 to see if we could build our own. Pleek91 Introducing Kitbag Router https://router.kitbag.dev https://router.kitbag.dev We made the decision to start the project from scratch; solving problems from first principles rather than taking the path of so many others and trying to build on top of the relatively old vue-router project. This means Kitbag Router is NOT a drop-in replacement for projects using vue-router. Therefore, this freedom also means we can have a relentless pursuit of the best possible developer experience, not weighed down by the need to have feature parity with Vue-router. Let’s take a look at some of Kitbag’s features Let’s take a look at some of Kitbag’s features First and foremost, it’s type safe! Kitbag Router uses a createRoutes utility that returns routes with the name, path, and query, all preserved in the Route type. This means the routes you provide to createRouter will maintain type safety when accessing the current route or performing navigation. Type safety in routing means auto-complete when assigning to on <router-link> , the easy discovery of available routes when defining a beforeRouteEnter hook, and ensuring that Typescript will error if the expected params for a route change without updating the router.push() call. <router-link> beforeRouteEnter router.push() Params are way more powerful Not only does Kitbag Router know what params are expected for a given route, it can also support param types beyond String . String Kitbag Router ships with built-in support for params of typeString, Number , Boolean , Date , RegExp , JSON , as well as any custom param type you define. Number Boolean Date RegExp JSON Not only is this type useful when navigating, but it also means a route that expects a number for an “id” param won’t be considered a match if the value provided in the URL doesn’t satisfy the number constraint. Furthermore, your Vue component that gets rendered for the route doesn’t have to worry about whether the param will be present or not or having to convert it from string to the type we know it’s supposed to be. number Support for the query Params aren’t relegated to only the path. Kitbag Router allows you to configure your expected params in the query the same way you’re used to defining params in other parts of the URL. Handling rejections Inevitably when defining your routes, you’ll want to add a “catch-all” or “not found” route. While Kitbag Router fully supports defining plain ol’ Regex in your path/query, it also ships with even better support for handling NotFound . We call this a “rejection”, which is customizable and can be extended to any custom rejection you need, like perhaps NotAuthorized . When a rejection is triggered, usually from within one of your hooks, the Kitbag Router will automatically render the rejection component you assigned for the given rejection type. NotFound NotAuthorized And more… These are the key features we think really make Kitbag Router compelling but there is so much more. Kitbag router is built for Vue3 and supports async components, route hooks, editable params from useRoute, components for RouterLink and RouterView, and more. Is it ready? Kitbag Router is still super green and currently maintained by a team of 2. It has not yet had a stable release (on 0.2.0 as of the time I’m writing this), so things are still likely to change. That being said, I hope you’ll give it a try, maybe give it a star . We’re excited to hear from the community on what features we should focus on next. give it a star Happy engineering!

Say Hello to Kitbag Router: A New Era of Vue.js Routing

MariaDB 11.4 introduced many advanced features. One that grabbed my attention is the general support of packages for stored routines. Although this was previously available by activating the Oracle compatibility mode, now, the feature is available generally out-of-the-box. This will help you to significantly enhance the organization of database development within a MariaDB environment. Packages provide a modular approach to managing database logic. This addition aligns MariaDB more closely with other advanced database systems that have long utilized packages, such as Oracle, and sets it apart in that regard from other open-source relational databases that don't support packages. Packages in MariaDB allow you to group related stored procedures, functions, variables, and other elements together into a single unit. This structure provides several benefits, including improved code organization, enhanced reusability, and simplified maintenance. Prior to this update, each stored procedure and function in MariaDB existed independently, which could lead to a cluttered schema and more complicated management of complex business logic when implemented in the database. Packages address this issue by providing a way to logically group related routines. Again, the primary advantage of using packages is the encapsulation of related routines. For example, in an e-commerce application, operations related to order processing can be grouped into a single package called OrderProcessing. This package might include procedures like PlaceOrder, CancelOrder, and UpdateOrderStatus, as well as functions such as GetOrderDetails. This logical grouping makes the database schema more organized and the codebase easier to navigate and hence to maintain. Creating Packages Creating and using packages in MariaDB 11.4 and later is straightforward. Simply use the CREATE PACKAGE statement to define a package and the CREATE PACKAGE BODY statement to implement the package’s routines. Here is a simplified example without the actual business logic implementation: DELIMITER $$

CREATE OR REPLACE PACKAGE OrderProcessing
  PROCEDURE PlaceOrder(customer_id INT, product_id INT, quantity INT);
  PROCEDURE CancelOrder(order_id INT);
  FUNCTION GetOrderDetails(order_id INT) RETURNS JSON;
END;

CREATE OR REPLACE PACKAGE BODY OrderProcessing
  PROCEDURE PlaceOrder(customer_id INT, product_id INT, quantity INT)
  BEGIN
    -- Implementation code here
  END;

  PROCEDURE CancelOrder(order_id INT)
  BEGIN
    -- Implementation code here
  END;

  FUNCTION GetOrderDetails(order_id INT) RETURNS JSON
  BEGIN
    -- Implementation code here
  END;
END;

$$
DELIMITER ; In this example, the OrderProcessing package is defined with two procedures and one function. The package body provides the implementation for these routines, encapsulating the logic related to order processing within a single package. Calling Packaged Stored Routines To call a procedure or function that was defined in a package, you use the "dot notation." Here's an example of how to call the CancelOrder procedure in the OrderProcessing package: CALL OrderProcessing.CancelOrder(7); The same applies to functions in packages: SELECT OrderProcessing.GetOrderDetails(7); You can also define package-level variables and constants, which are accessible to all routines within the package. This way, you can share common data without relying on global variables or passing around parameters between routines. By centrally managing shared data within the package, you reduce code duplication and minimize the risk of errors. The following is an example (don't take the variable names too seriously in this snippet of code): DELIMITER $$

CREATE OR REPLACE PACKAGE OrderProcessing
  -- procedure list (see previous example)
END;

CREATE OR REPLACE PACKAGE BODY OrderProcessing
  -- variable declarations
  DECLARE some_count INT DEFAULT 1;
  DECLARE some_total INT DEFAULT 0;

  -- procedure definitions (see previous example)
END;

$$
DELIMITER ; Other Benefits of Packages The introduction of packages in MariaDB 11.4 also brings the possibility of better version control and modularization of code. You can now manage stored routines more effectively, making it easier to track changes and updates. This modularization is particularly beneficial in large projects, where multiple developers might be working on different parts of the database logic simultaneously. By isolating different functionalities into packages, conflicts, and overlaps can be minimized, leading to a smoother development process. Moreover, packages support forward declarations, which means that the routines can be defined before their actual implementation. This feature allows for a more flexible and structured approach to coding, where developers can outline the package interface first and then fill in the details. This separation of interface and implementation can lead to cleaner, more understandable code, facilitating collaboration, and reducing the learning curve for new developers joining a project. For developers accustomed to working with Oracle databases, the inclusion of packages in MariaDB 11.4 will feel familiar and welcome. It bridges a functional gap between MariaDB and Oracle, making it easier to transition between these platforms. Packages vs Multiple Schemas It's important to note the distinction between packages and merely using multiple database schemas. While multiple schemas can help segregate different parts of a database, they do not offer the same level of organization and encapsulation as packages. Schemas are useful for dividing distinct areas of data and logic, but they do not inherently group related procedures and functions together in a way that enhances modularity and maintainability. Packages, on the other hand, allow for a more granular and cohesive approach, grouping related logic together within the same schema. This not only simplifies the management of routines but also improves the clarity and maintainability of the code. Try It Out As always, MariaDB continues to evolve. Try it out today by downloading the latest version of MariaDB, or if you have Docker running: docker run --name mariadb-11.4 -e MARIADB_ROOT_PASSWORD=my-secret-pw -e MARIADB_DATABASE=mydb -e MARIADB_USER=myuser -e MARIADB_PASSWORD=mypassword -d mariadb:11.4

docker exec -it mariadb-11.4 mariadb -p"mypassword" MariaDB 11.4 introduced many advanced features . One that grabbed my attention is the general support of packages for stored routines. Although this was previously available by activating the Oracle compatibility mode , now, the feature is available generally out-of-the-box. This will help you to significantly enhance the organization of database development within a MariaDB environment. MariaDB 11.4 advanced features Oracle compatibility mode Packages provide a modular approach to managing database logic. This addition aligns MariaDB more closely with other advanced database systems that have long utilized packages, such as Oracle, and sets it apart in that regard from other open-source relational databases that don't support packages. Packages in MariaDB allow you to group related stored procedures, functions, variables, and other elements together into a single unit. This structure provides several benefits, including improved code organization, enhanced reusability, and simplified maintenance. Prior to this update, each stored procedure and function in MariaDB existed independently, which could lead to a cluttered schema and more complicated management of complex business logic when implemented in the database . implemented in the database Packages address this issue by providing a way to logically group related routines. Again, the primary advantage of using packages is the encapsulation of related routines. For example, in an e-commerce application, operations related to order processing can be grouped into a single package called OrderProcessing . This package might include procedures like PlaceOrder , CancelOrder , and UpdateOrderStatus , as well as functions such as GetOrderDetails . OrderProcessing PlaceOrder CancelOrder UpdateOrderStatus GetOrderDetails This logical grouping makes the database schema more organized and the codebase easier to navigate and hence to maintain. Creating Packages Creating and using packages in MariaDB 11.4 and later is straightforward. Simply use the CREATE PACKAGE statement to define a package and the CREATE PACKAGE BODY statement to implement the package’s routines. Here is a simplified example without the actual business logic implementation: CREATE PACKAGE CREATE PACKAGE BODY DELIMITER $$

CREATE OR REPLACE PACKAGE OrderProcessing
  PROCEDURE PlaceOrder(customer_id INT, product_id INT, quantity INT);
  PROCEDURE CancelOrder(order_id INT);
  FUNCTION GetOrderDetails(order_id INT) RETURNS JSON;
END;

CREATE OR REPLACE PACKAGE BODY OrderProcessing
  PROCEDURE PlaceOrder(customer_id INT, product_id INT, quantity INT)
  BEGIN
    -- Implementation code here
  END;

  PROCEDURE CancelOrder(order_id INT)
  BEGIN
    -- Implementation code here
  END;

  FUNCTION GetOrderDetails(order_id INT) RETURNS JSON
  BEGIN
    -- Implementation code here
  END;
END;

$$
DELIMITER ; DELIMITER $$

CREATE OR REPLACE PACKAGE OrderProcessing
  PROCEDURE PlaceOrder(customer_id INT, product_id INT, quantity INT);
  PROCEDURE CancelOrder(order_id INT);
  FUNCTION GetOrderDetails(order_id INT) RETURNS JSON;
END;

CREATE OR REPLACE PACKAGE BODY OrderProcessing
  PROCEDURE PlaceOrder(customer_id INT, product_id INT, quantity INT)
  BEGIN
    -- Implementation code here
  END;

  PROCEDURE CancelOrder(order_id INT)
  BEGIN
    -- Implementation code here
  END;

  FUNCTION GetOrderDetails(order_id INT) RETURNS JSON
  BEGIN
    -- Implementation code here
  END;
END;

$$
DELIMITER ; In this example, the OrderProcessing package is defined with two procedures and one function. The package body provides the implementation for these routines, encapsulating the logic related to order processing within a single package. OrderProcessing Calling Packaged Stored Routines To call a procedure or function that was defined in a package, you use the "dot notation." Here's an example of how to call the CancelOrder procedure in the OrderProcessing package: CancelOrder OrderProcessing CALL OrderProcessing.CancelOrder(7); CALL OrderProcessing.CancelOrder(7); The same applies to functions in packages: SELECT OrderProcessing.GetOrderDetails(7); SELECT OrderProcessing.GetOrderDetails(7); You can also define package-level variables and constants, which are accessible to all routines within the package. This way, you can share common data without relying on global variables or passing around parameters between routines. By centrally managing shared data within the package, you reduce code duplication and minimize the risk of errors. The following is an example (don't take the variable names too seriously in this snippet of code): DELIMITER $$

CREATE OR REPLACE PACKAGE OrderProcessing
  -- procedure list (see previous example)
END;

CREATE OR REPLACE PACKAGE BODY OrderProcessing
  -- variable declarations
  DECLARE some_count INT DEFAULT 1;
  DECLARE some_total INT DEFAULT 0;

  -- procedure definitions (see previous example)
END;

$$
DELIMITER ; DELIMITER $$

CREATE OR REPLACE PACKAGE OrderProcessing
  -- procedure list (see previous example)
END;

CREATE OR REPLACE PACKAGE BODY OrderProcessing
  -- variable declarations
  DECLARE some_count INT DEFAULT 1;
  DECLARE some_total INT DEFAULT 0;

  -- procedure definitions (see previous example)
END;

$$
DELIMITER ; Other Benefits of Packages The introduction of packages in MariaDB 11.4 also brings the possibility of better version control and modularization of code. You can now manage stored routines more effectively, making it easier to track changes and updates. This modularization is particularly beneficial in large projects, where multiple developers might be working on different parts of the database logic simultaneously. By isolating different functionalities into packages, conflicts, and overlaps can be minimized, leading to a smoother development process. Moreover, packages support forward declarations, which means that the routines can be defined before their actual implementation. This feature allows for a more flexible and structured approach to coding, where developers can outline the package interface first and then fill in the details. This separation of interface and implementation can lead to cleaner, more understandable code, facilitating collaboration, and reducing the learning curve for new developers joining a project. For developers accustomed to working with Oracle databases, the inclusion of packages in MariaDB 11.4 will feel familiar and welcome. It bridges a functional gap between MariaDB and Oracle, making it easier to transition between these platforms. Packages vs Multiple Schemas It's important to note the distinction between packages and merely using multiple database schemas. While multiple schemas can help segregate different parts of a database, they do not offer the same level of organization and encapsulation as packages. Schemas are useful for dividing distinct areas of data and logic, but they do not inherently group related procedures and functions together in a way that enhances modularity and maintainability. Packages, on the other hand, allow for a more granular and cohesive approach, grouping related logic together within the same schema. This not only simplifies the management of routines but also improves the clarity and maintainability of the code. Try It Out As always, MariaDB continues to evolve . Try it out today by downloading the latest version of MariaDB, or if you have Docker running: MariaDB continues to evolve downloading docker run --name mariadb-11.4 -e MARIADB_ROOT_PASSWORD=my-secret-pw -e MARIADB_DATABASE=mydb -e MARIADB_USER=myuser -e MARIADB_PASSWORD=mypassword -d mariadb:11.4

docker exec -it mariadb-11.4 mariadb -p"mypassword" docker run --name mariadb-11.4 -e MARIADB_ROOT_PASSWORD=my-secret-pw -e MARIADB_DATABASE=mydb -e MARIADB_USER=myuser -e MARIADB_PASSWORD=mypassword -d mariadb:11.4

docker exec -it mariadb-11.4 mariadb -p"mypassword"

Packages for Store Routines in MariaDB 11.4: What You Need to Know

Router Protocol is pleased to announce that it has completed an oversubscribed strategic funding round with participation from prominent crypto angels and funds. The primary goal of the strategic round was to thoughtfully expand Router's cap table with crypto operators who deeply understand the importance of cross-chain infrastructure and can accelerate the ecosystem growth as Router evolves into a Layer 1 blockchain. Router Protocol is honored to welcome an exceptional group of accomplished founders and web3 executives as angels and advisors, including Keone Hon (Monad), Parker Jou (Caldera), Amrit Kumar (Altlayer), Aniket (Biconomy), Anurag Arjun (Avail), Amitej (Stader), Ravindra (Frontier), and several others. In a testament to the unwavering belief in its vision, Router Protocol also received overwhelming support from existing investors, including heavyweight players such as Wintermute Ventures, Woodstock, DeFi Capital, CryptoBanter, RavenDAO, and Luganodes. Other renowned advisors and angels include Zaki Manian (Sommelier/Cosmos), Ajit Tripathi (@chainyoda), Gokul Rajaram (Google/Doordash), and Surojit Chatterjee (Coinbase, Google, Flipkart, EMA). The proceeds from this funding round will be deployed strategically to fuel the development and highly anticipated launch of the Router Chain mainnet. Router Chain is set to revolutionize value transfer by abstracting away blockchain complexity and unlocking a new era of frictionless cross-chain applications and user experiences. "Router Chain embodies the evolution of our unwavering vision to build the universal interconnectivity layer between fragmented L1/L2 networks," said Ramani Ramachandran, CEO of Router Protocol. "By abstracting away blockchain complexity, we are laser-focused on delivering the most seamless and intuitive user and developer experience for multi-chain applications. This funding round propels us closer to realising this transformative vision." Router Protocol’s mantra has always been "developers first." Its mission is to empower builders to focus on bringing their groundbreaking ideas to life, rather than grappling with infrastructure complexities. Router Chain will provide a robust suite of flexible interoperability primitives, including its innovative cross-chain intent framework and developer-friendly toolkits, to make this vision a reality. "We are thrilled to witness the rapid expansion of our ecosystem, with trailblazing cross-chain projects like StakeEase, FolioX, and many more leveraging our interoperability primitives to push the boundaries of what's possible," said Shubham Singh, CTO of Router Protocol. In a major milestone, Router Protocol launched Router Nitro, a super-fast, gas-efficient, intent-based cross-chain bridge powered by an innovative reverse-verification mechanism. Nitro Bridge crossed $350M volume in the past 4 months, over 650K+ transactions, and almost 300K unique users. To further accelerate ecosystem growth, Router Protocol is thrilled to announce the upcoming launch of the Router Ecosystem Grants Program, which will provide substantial financial support and resources to promising projects building on Router Chain. Moreover, the project’s recently revamped tokenomics empowers it to aggressively focus on community engagement, ecosystem expansion, and the promotion of exciting new cross-chain primitives that will redefine the landscape of interoperability. The oversubscribed round demonstrates the demand for high-value web3 infrastructure and marks a crucial step in Router's maturation from a bridge solution to a core Web3 connecting layer. Backing from this expanded group of partners will aid in evangelizing Router's vision and unique value proposition to a global audience. Router Protocol is pleased to announce that it has completed an oversubscribed strategic funding round with participation from prominent crypto angels and funds. Router Protocol is pleased to announce that it has completed an oversubscribed strategic funding round with participation from prominent crypto angels and funds. The primary goal of the strategic round was to thoughtfully expand Router's cap table with crypto operators who deeply understand the importance of cross-chain infrastructure and can accelerate the ecosystem growth as Router evolves into a Layer 1 blockchain. Router Protocol is honored to welcome an exceptional group of accomplished founders and web3 executives as angels and advisors, including Keone Hon (Monad), Parker Jou (Caldera), Amrit Kumar (Altlayer), Aniket (Biconomy), Anurag Arjun (Avail), Amitej (Stader), Ravindra (Frontier), and several others. In a testament to the unwavering belief in its vision, Router Protocol also received overwhelming support from existing investors, including heavyweight players such as Wintermute Ventures, Woodstock, DeFi Capital, CryptoBanter, RavenDAO, and Luganodes. Other renowned advisors and angels include Zaki Manian (Sommelier/Cosmos), Ajit Tripathi (@chainyoda), Gokul Rajaram (Google/Doordash), and Surojit Chatterjee (Coinbase, Google, Flipkart, EMA). The proceeds from this funding round will be deployed strategically to fuel the development and highly anticipated launch of the Router Chain mainnet. Router Chain is set to revolutionize value transfer by abstracting away blockchain complexity and unlocking a new era of frictionless cross-chain applications and user experiences. "Router Chain embodies the evolution of our unwavering vision to build the universal interconnectivity layer between fragmented L1/L2 networks," said Ramani Ramachandran, CEO of Router Protocol. "By abstracting away blockchain complexity, we are laser-focused on delivering the most seamless and intuitive user and developer experience for multi-chain applications. This funding round propels us closer to realising this transformative vision." Router Protocol’s mantra has always been "developers first." Its mission is to empower builders to focus on bringing their groundbreaking ideas to life, rather than grappling with infrastructure complexities. Router Chain will provide a robust suite of flexible interoperability primitives, including its innovative cross-chain intent framework and developer-friendly toolkits, to make this vision a reality. "We are thrilled to witness the rapid expansion of our ecosystem, with trailblazing cross-chain projects like StakeEase, FolioX, and many more leveraging our interoperability primitives to push the boundaries of what's possible," said Shubham Singh, CTO of Router Protocol. In a major milestone, Router Protocol launched Router Nitro, a super-fast, gas-efficient, intent-based cross-chain bridge powered by an innovative reverse-verification mechanism. Nitro Bridge crossed $350M volume in the past 4 months, over 650K+ transactions, and almost 300K unique users. To further accelerate ecosystem growth, Router Protocol is thrilled to announce the upcoming launch of the Router Ecosystem Grants Program, which will provide substantial financial support and resources to promising projects building on Router Chain. Moreover, the project’s recently revamped tokenomics empowers it to aggressively focus on community engagement, ecosystem expansion, and the promotion of exciting new cross-chain primitives that will redefine the landscape of interoperability. The oversubscribed round demonstrates the demand for high-value web3 infrastructure and marks a crucial step in Router's maturation from a bridge solution to a core Web3 connecting layer. Backing from this expanded group of partners will aid in evangelizing Router's vision and unique value proposition to a global audience.

Router Protocol Completes Oversubscribed Strategic Funding Round

রাউটার প্রোটোকল ওভারসাবস্ক্রাইবড স্ট্র্যাটেজিক ফান্ডিং রাউন্ড সম্পূর্ণ করে

Router Protocol schließt überzeichnete strategische Finanzierungsrunde ab

Router Protocol completa una ronda de financiación estratégica con exceso de suscripción

Le protocole de routeur finalise un cycle de financement stratégique sursouscrit

राउटर प्रोटोकॉल ने ओवरसब्सक्राइब्ड रणनीतिक फंडिंग राउंड पूरा किया

ルータープロトコル、募集額超過の戦略的資金調達ラウンドを完了

라우터 프로토콜, 초과 구독된 전략적 자금 조달 라운드 완료

Router Protocol conclui rodada de financiamento estratégico com excesso de inscrições

Router Protocol завершает раунд стратегического финансирования переподписки

Yönlendirici Protokolü Aşırı Abone Olunan Stratejik Finansman Turunu Tamamladı

Giao thức bộ định tuyến hoàn thành vòng tài trợ chiến lược được đăng ký vượt mức

路由器协议完成超额认购的战略融资轮

If a product is complex and releases are substantial, there are multiple ways to ensure quality. One key tool I use in our development process is team testing: stepping into the customer’s shoes, traversing various user journeys, and ensuring all key interactions work as intended. This approach offers numerous benefits, from engaging the entire team in understanding the product to correcting flaws in the original business logic. Despite its usefulness, team testing sessions tend to be tedious and generally disliked: building a product is far more enjoyable than repeatedly clicking through it. In this post, I will describe how I made team testing more engaging and somewhat enjoyable by incorporating ChatGPT into the process, transforming it into a competitive activity. How We Conduct Team Testing The process was straightforward: Deploy a feature to a testing environment.
Document what needs to be checked: main user journeys and definitions of success.
Gather on a call or in a room, use the product, discuss, and exchange feedback.
Organize and prioritize feedback, then act accordingly. As a result, the team has usually compiled a list of issues to address. Introducing ChatGPT With the rise of ChatGPT in mid-2023, I decided to integrate it into our testing sessions. Initially, I used it to analyze and count issue reports in Slack—since Slack lacks convenient export functionality. Here’s the prompt I tried: The text below is the log of slack channel.

It contains bugs reported by people, each bug report starts with a first name, then timestamp, then the message itself (normally 1 or 2 lines).

Strings containing ".png", IMG" or ".mov"  could be ignored.

Read the text, count the number of reports per person and rank them from highest ChatGPT struggled at first, glitching in about 60% of cases with verbose error messages. I realized I needed a different approach. Switching to a Script Since ChatGPT ran a Python interpreter for our task, I decided to directly utilize the Python code it wrote. I adjusted the script to account for the way Slack handles attached files as separate messages: # Initialize counters for each name based on the list provided
# The names should match the displayed names in Slack
name_counts = {
    "John": 0,
    "Jane": 0,
    "Rosy": 0,
}

# Open the file and count the occurrences of each name
with open("testing_session_log.txt", "r") as file:
    lines = file.readlines()

# Filtering out garbage lines and counting names
for line in lines:
    # Ignore garbage lines
    if any(garbage in line for garbage in [".png", ".IMG", ".mov"]):
        continue
    for name in name_counts.keys():
        if name in line:
            name_counts[name] += 1

print(name_counts) Returning to ChatGPT for Creativity and Recognition Implementing the script to generate a leaderboard immediately after the session introduced a sense of competition. I saw the engagement growing, and people reporting more bugs! So, I continued to use ChatGPT for crafting personalized praise based on the team’s reported issues, acknowledging their contributions: Using the attached testing session log, praise everyone for their impact and highligh one report of a choice for each person.

Participants names:
John
Jane
Rosy

Wrap the praise in a form of a short, sincere and inspirational message, no more than 4 sentences long. I found it deeply satisfying to read the praise from a machine: John: Your insight on UI details like the collapsed header buttons and gallery navigation enhances our project's usability.
Your contributions are crucial for a seamless user experience.

Jane: Your keen observations, especially on navigation issues, enhance our platform's intuitiveness.
Your ability to catch subtle bugs is invaluable.

Rosy:Your focus on mobile usability, from download behaviors to icon alignment, significantly polishes our mobile interface.
Your efforts make a substantial difference. Conclusion What I’ve implemented isn’t rocket science, but in the pre-LLM era, this would have taken considerably longer to achieve, if at all. While the future of AI-driven products is still shaping up, it’s clear that product teams can benefit greatly by integrating such technologies to simplify tasks, boost positive reinforcement, and free up time for critical projects. Image credit: Midjourney, prompt “team of engineers coding late at night, Hyper-realistic textures, Precise details --version 6.0 --weird 1000” If a product is complex and releases are substantial, there are multiple ways to ensure quality. One key tool I use in our development process is team testing: stepping into the customer’s shoes, traversing various user journeys, and ensuring all key interactions work as intended. This approach offers numerous benefits, from engaging the entire team in understanding the product to correcting flaws in the original business logic. Despite its usefulness, team testing sessions tend to be tedious and generally disliked: building a product is far more enjoyable than repeatedly clicking through it. In this post, I will describe how I made team testing more engaging and somewhat enjoyable by incorporating ChatGPT into the process, transforming it into a competitive activity. How We Conduct Team Testing The process was straightforward: Deploy a feature to a testing environment. Document what needs to be checked: main user journeys and definitions of success. Gather on a call or in a room, use the product, discuss, and exchange feedback. Organize and prioritize feedback, then act accordingly. Deploy a feature to a testing environment. Document what needs to be checked: main user journeys and definitions of success. Gather on a call or in a room, use the product, discuss, and exchange feedback. Organize and prioritize feedback, then act accordingly. As a result, the team has usually compiled a list of issues to address. Introducing ChatGPT With the rise of ChatGPT in mid-2023, I decided to integrate it into our testing sessions. Initially, I used it to analyze and count issue reports in Slack—since Slack lacks convenient export functionality. Here’s the prompt I tried: The text below is the log of slack channel.

It contains bugs reported by people, each bug report starts with a first name, then timestamp, then the message itself (normally 1 or 2 lines).

Strings containing ".png", IMG" or ".mov"  could be ignored.

Read the text, count the number of reports per person and rank them from highest The text below is the log of slack channel.

It contains bugs reported by people, each bug report starts with a first name, then timestamp, then the message itself (normally 1 or 2 lines).

Strings containing ".png", IMG" or ".mov"  could be ignored.

Read the text, count the number of reports per person and rank them from highest ChatGPT struggled at first, glitching in about 60% of cases with verbose error messages. I realized I needed a different approach. Switching to a Script Since ChatGPT ran a Python interpreter for our task, I decided to directly utilize the Python code it wrote. Python interpreter I adjusted the script to account for the way Slack handles attached files as separate messages: # Initialize counters for each name based on the list provided
# The names should match the displayed names in Slack
name_counts = {
    "John": 0,
    "Jane": 0,
    "Rosy": 0,
}

# Open the file and count the occurrences of each name
with open("testing_session_log.txt", "r") as file:
    lines = file.readlines()

# Filtering out garbage lines and counting names
for line in lines:
    # Ignore garbage lines
    if any(garbage in line for garbage in [".png", ".IMG", ".mov"]):
        continue
    for name in name_counts.keys():
        if name in line:
            name_counts[name] += 1

print(name_counts) # Initialize counters for each name based on the list provided
# The names should match the displayed names in Slack
name_counts = {
    "John": 0,
    "Jane": 0,
    "Rosy": 0,
}

# Open the file and count the occurrences of each name
with open("testing_session_log.txt", "r") as file:
    lines = file.readlines()

# Filtering out garbage lines and counting names
for line in lines:
    # Ignore garbage lines
    if any(garbage in line for garbage in [".png", ".IMG", ".mov"]):
        continue
    for name in name_counts.keys():
        if name in line:
            name_counts[name] += 1

print(name_counts) Returning to ChatGPT for Creativity and Recognition Implementing the script to generate a leaderboard immediately after the session introduced a sense of competition. I saw the engagement growing, and people reporting more bugs! So, I continued to use ChatGPT for crafting personalized praise based on the team’s reported issues, acknowledging their contributions: Using the attached testing session log, praise everyone for their impact and highligh one report of a choice for each person.

Participants names:
John
Jane
Rosy

Wrap the praise in a form of a short, sincere and inspirational message, no more than 4 sentences long. Using the attached testing session log, praise everyone for their impact and highligh one report of a choice for each person.

Participants names:
John
Jane
Rosy

Wrap the praise in a form of a short, sincere and inspirational message, no more than 4 sentences long. I found it deeply satisfying to read the praise from a machine: John: Your insight on UI details like the collapsed header buttons and gallery navigation enhances our project's usability.
Your contributions are crucial for a seamless user experience.

Jane: Your keen observations, especially on navigation issues, enhance our platform's intuitiveness.
Your ability to catch subtle bugs is invaluable.

Rosy:Your focus on mobile usability, from download behaviors to icon alignment, significantly polishes our mobile interface.
Your efforts make a substantial difference. John: Your insight on UI details like the collapsed header buttons and gallery navigation enhances our project's usability.
Your contributions are crucial for a seamless user experience.

Jane: Your keen observations, especially on navigation issues, enhance our platform's intuitiveness.
Your ability to catch subtle bugs is invaluable.

Rosy:Your focus on mobile usability, from download behaviors to icon alignment, significantly polishes our mobile interface.
Your efforts make a substantial difference. Conclusion What I’ve implemented isn’t rocket science, but in the pre-LLM era, this would have taken considerably longer to achieve, if at all. While the future of AI-driven products is still shaping up, it’s clear that product teams can benefit greatly by integrating such technologies to simplify tasks, boost positive reinforcement, and free up time for critical projects. Image credit: Midjourney, prompt “team of engineers coding late at night, Hyper-realistic textures, Precise details --version 6.0 --weird 1000” Image credit: Midjourney, prompt “team of engineers coding late at night, Hyper-realistic textures, Precise details --version 6.0 --weird 1000”

From Routine to Rewarding: Integrating ChatGPT Into Product Testing Workflow

Introduction For those who have never worked with Feature-Sliced Design, aka I recommend reading my article about FSD first. FSD, https://hackernoon.com/the-best-complex-frontend-architecture-what-you-need-to-know-about-feature-sliced-design?embedable=true Many developers faced a problem when starting a project using NextJS with FSD, spending time to get it right to combine NextJS and FSD to make it work together, especially using the NextJS App Router. This article describes how to make NextJS App Router work with the FSD methodology. Problem NextJS App Router expects files in the . This routing mechanism to the FSD concept since it is not possible to maintain a flat slice structure in such a routing mechanism. app folder to match URLs does not correspond Approach The approach is pretty simple. You should simply move the NextJS folder to the root folder of the project, and import the FSD pages into the NextJS folder. This saves the FSD project structure inside the folder. app app src ├── app                # NextJS app folder
├── src
│   ├── app            # FSD app folder
│   ├── entities
│   ├── features
│   ├── pages
│   ├── shared
│   ├── widgets And that's it! The problem of combining NextJS App Router and FSD is solved! See Also I highly recommend reading the official FSD documentation article about Usage with NextJS

How to Fix the NextJS App Router and FSD Problem

How to Write Your Own Typesafe React Router in 500 Lines

কিভাবে 500 লাইনে আপনার নিজের টাইপসেফ রিঅ্যাক্ট রাউটার লিখবেন

So schreiben Sie Ihren eigenen typsicheren React-Router in 500 Zeilen

Cómo escribir su propio enrutador Typesafe React en 500 líneas

Comment écrire votre propre routeur Typesafe React en 500 lignes

500 पंक्तियों में अपना खुद का टाइपसेफ रिएक्ट राउटर कैसे लिखें

独自のタイプセーフな React Router を 500 行で書く方法

500줄로 나만의 Typesafe React Router를 작성하는 방법

Como escrever seu próprio roteador Typesafe React em 500 linhas

Как написать свой собственный Typesafe React Router в 500 строк

Kendi Typesafe React Router'ınızı 500 Satırda Nasıl Yazabilirsiniz?

Cách viết Bộ định tuyến React Typesafe của riêng bạn trong 500 dòng

如何用 500 行代码编写自己的类型安全 React 路由器

VANCOUVER, BC, Canada, November 6th, 2023/Chainwire/--MaestroBots, a prominent cryptocurrency trading bot on the Telegram messenger app, has swiftly taken action to refund users who were affected by a recent smart contract exploit. In an incident that unfolded on October 24, a total of 280 ETH was targeted. In response, the Maestro team took immediate action to refund the users impacted by the Maestro Router 2 contract exploit. This commitment to user security and trust was announced on social media platform X (formerly Twitter) on October 25. MaestroBots allocated a substantial sum of 610 ETH from its own revenue to cover all user losses. At the time of writing, this sum exceeded $1 million. The statement from MaestroBots read: "Every wallet that lost tokens in the router exploit has now received the full amount they lost. Some of you ended up with even bigger bags." For nine out of the 11 exploited tokens, MaestroBots opted to buy and refund tokens, instead of sending ETH, deeming it the most equitable and comprehensive refund. MaestroBots spent 276 ETH to secure users' tokens, demonstrating their commitment to user safety. For the remaining two tokens, Joe (JOE) and Lockheed Martin Inu (LMI), the refund was issued in ETH due to liquidity constraints in buying back the lost tokens. To express appreciation for the affected users' trust and support, MaestroBots increased the refund amount by 20%, resulting in a total cost of 334 ETH. CertiK, a blockchain security firm, verified the transactions, confirming the 334 ETH compensation disbursed to users by MaestroBots. Abbas Abou Daya, CEO of MaestroBots, said: "We absolutely refuse to expose our users to such bad actors, and we needed to do right by the few who were affected. The only right option was refunding every single user to the absolute best of our ability. Every wallet that lost tokens in the router exploit has now received the full amount they lost. Some of you ended up with even bigger bags." Abou Daya further explained the choice to buy and refund tokens for most of the affected tokens, stating: "For 9 out of the 11 exploited tokens, we chose to buy and refund tokens instead of simply sending ETH because it's the most equitable and complete refund we can offer for the incident. This gives full control back to the user (plus you can dump on our buys). We spent 276 ETH to secure our users' tokens. For the other two tokens (JOE and LMI), there simply wasn't enough liquidity to allow us to buy back the lost tokens, so we compensated affected users with the ETH equivalent of their tokens, and boosted that amount by 20% because you deserve it. These refunds cost 334 ETH." Abou Daya went on to highlight the quick response to the incident, stating: "Overall, the full refund campaign concluded a mere 10 hours after the exploit. These refunds cost us a total of 610 ETH (~$1.1M), but it's a small price to pay to ensure your safety and peace of mind." The MaestroBot team is committed to user safety: "Team Maestro apologizes for the error. We hold ourselves to a higher standard. That being said, the exploit was fully shut down within 30 minutes, trading capabilities were restored within 2 hours, and full refunds were issued within 10 hours. Anyone who was affected was made whole. Maestro: Router 2 is now completely safe. We hope that the swiftness of our response, paired with the completeness of the offered refund, can serve as a powerful reminder of our continued commitment to do right by our users." CertiK, a blockchain security firm, confirmed the safety and integrity of Maestro: Router 2 following the swift response and resolution of the incident. About MaestroBots MaestroBots is the leading Telegram bot for cryptocurrency trading, offering a wide range of services across Ethereum, BNB Chain, and Arbitrum networks. The platform prioritizes user security and has shown its commitment to safeguarding user assets by promptly addressing and resolving the recent smart contract exploit. For more information about MaestroBots, please visit https://www.maestrobots.com/ Contact Abbas Abou Daya MaestroBots maestro@gearlay.com This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program. Learn more about the program . here

MaestroBots Makes Users Whole: Refunds 610 ETH Following Router Exploit

MaestroBots ব্যবহারকারীদের সম্পূর্ণ করে তোলে: রাউটার এক্সপ্লয়েট অনুসরণ করে 610 ETH ফেরত দেয়

MaestroBots macht Benutzer gesund: Erstattet 610 ETH nach Router-Exploit

MaestroBots recupera la integridad de los usuarios: reembolsa 610 ETH tras el exploit del enrutador

MaestroBots rend les utilisateurs entiers : rembourse 610 ETH suite à un exploit de routeur

मेस्ट्रोबॉट्स उपयोगकर्ताओं को संपूर्ण बनाता है: राउटर एक्सप्लॉइट के बाद 610 ईटीएच वापस करता है

MaestroBots がユーザーを完全にする: ルーター悪用後に 610 ETH を返金

MaestroBots는 사용자를 온전하게 만듭니다: 라우터 공격에 따라 610 ETH를 환불합니다.

MaestroBots torna os usuários inteiros: reembolsa 610 ETH após exploração do roteador

MaestroBots спасает пользователей: возвращает 610 ETH после взлома маршрутизатора

MaestroBots Kullanıcıları Bütünleştiriyor: Yönlendirici Saldırısının Ardından 610 ETH'yi İade Ediyor

MaestroBots khiến toàn bộ người dùng: Hoàn lại 610 ETH sau khi khai thác bộ định tuyến

MaestroBots 让用户完整：路由器漏洞后退款 610 ETH

Stories, News & Mentions about ROUTIZER

Routizer’s Stories on HackerNoon