Pittsburgh Regional Transit provided an update Tuesday after a cybersecurity incident occurred back in Dec. 2024.

Pittsburgh Regional Transit provides update amid cybersecurity incident

Pittsburgh Regional Transit provided an update Tuesday after a cybersecurity incident that occurred back in Dec. 2024.

Pittsburgh Regional Transit is investigating a ransomware attack detected on Thursday, Dec. 19.

Pittsburgh Regional Transit investigating cybersecurity incident - CBS Pittsburgh

(Bloomberg) -- China’s long-awaited stimulus measures may have been too much for the markets to handle.Most Read from BloombergVanderbilt Leases Struggling NYC Seminary for Campus ExpansionNJ Transit, Amtrak Trains Delayed After Derailment Near NYCWhere Cargo Bikes Are Freeing Cities From ...

China’s Market Marred by Glitches as Frenzy Grips Stocks

MicroCAT will help to expand services into “transit desert” areas in Albermarle County, Va., where public transport is scarce.

Albermarie County, CAT launch on-demand ride sharing pilot

The phase includes training for operators and maintenance staff and continued testing to ensure stations, tracks, utilities and vehicles work together as expected in

Sound Transit enters pre-revenue phase on East Link light-rail extension project

All of that has led to a $750 million budget shortfall that will slam the transit system when federal pandemic funds run out in July 2024 — unless contributing jurisdictions step up to provide more funding. Metro has released some of the “doomsday ...

EDITORIAL: The DMV Cannot Let Metro Fall Off the Fiscal Cliff

The next round of EU sanctions on Moscow could hit more than 5 billion in trade according to Bloomberg sources Read Full Article at RTcom

EU looks to expand sanctions on Russia - Bloomberg

The meeting, at the George Howard Building in Ellicott City, included representatives from the Maryland Department of Transportation, the Maryland State Highway Administration, the Motor Vehicle Administration, Maryland Transit Administration and Maryland ...

Howard County and state officials outline transportation priorities, bicycle safety improvements

From Hollywood's death-dealing Terminator to warnings from genius Stephen Hawking or Silicon Valley stars, fears have been fueled that artificial intelligence (AI) could one day destroy humanity. Tech titans are racing toward creating AI far smarter than ...

AI anxiety as computers get super smart

Transit

transit

In many major cities, public transportation has been suffering from the decrease in profitability and reliability, as well as poor customer experience. As the global economy continues to shift to an on-demand model, commuters expect more personalized services and more pleasant experience, that rely on technology. Meet Mobility-as-a-Service (MaaS) — a solution that integrates public and private transportation into one system. Think of using one mobile app for multiple modes of transportation (bike, shared car, train…) to get to your destination and paying one fee for that journey. The payment will be distributed between all operators. The technology will connect vehicles, public transit, and infrastructure with the customers and will offer flexible and safe travel. In 2019–2024, we will see broader use and adoption of MaaS due to the advancements in and machine learning and the increasing adoption rates of unconventional transportation modes, such as bike- and car-sharing services. IoT According to , MaaS will have a “disruptive impact on traditional transportation modes like car ownership, buses, trains, aviation, taxis and rental cars.” ABI Research This idea is being tested around the world and relies heavily on IoT technology. MaaS needs real-time vehicle connectivity and artificial intelligence to plan trips, optimize routes, and shorten travel times. Without knowing each vehicle’s precise location and status, in addition to other data, such as traffic and maintenance information, usability of MaaS will suffer. The mobility algorithm will calculate the most appropriate travel option from the user’s location to the destination and provide the optimal combination of transportation types. Travel options will account for scheduled maintenance (based on asset utilization) and unexpected breakdowns. While artificial intelligence and route optimization are already at work at Google, Uber, and others, IoT in mass transit is in a nascent phase. Both AI and IoT will become much more widespread in the transportation sector in the next 2–3 years, with IoT accelerating its adoption rate even faster. For example, companies like use IoT to collect and analyze traffic data to anticipate traffic issues. DENSO A journey planner will be an inherent part of the solution and will unite all means of transportation in a single network. The application will be always aware of each vehicle’s location and status and will provide the users with the precise arrival and departure times for each leg. There’s a clear benefit to the end user: simplicity of journey planning, shorter travel, and, likely, a lower price. Helsinki rolled out a , which brings together public transportation, taxis, city bikes, and car-sharing services. The app enjoyed strong support from the city and the community. MaaS solution MaaS isn’t without caveats. Public transportation, subsidized by the local taxpayers, often has complicated cost structures that may make it difficult to figure out which part of the total fee should be attributed to each of the types of transportation used in a journey. Public mass transit can also be slow to adopt new technologies — and all that can hinder the development of MaaS. Nonetheless, public sector is the backbone of MaaS solutions, which will get people out of private cars into shared transportation mode and benefit economic activity by lowering transportation costs. future

The Future of Mass Transit and IoT

Expertise Delivered Frontend, Backend & QA Industry Food and Beverage The Client Ann’s Boba Tea is an American bubble tea franchise (also known as Pearl Milk Tea or Boba Milk Tea). It was founded in 2010 and has over 350+ locations across the US. The tea is brewed at the perfect temperature with milk, fresh ingredients, and a unique recipe and presented innovatively. Customers can earn rewards for each order placed and redeem reward points against future orders. Disclaimer— The name Ann’s Boba Tea is a placeholder, as both parties have signed an NDA. The Challenge Ann’s in-store and online ordering applications were created using LevelUp (a customer engagement and mobile payment platform) as the backend. However, LevelUp was being discontinued, so our client needed to transition its existing user data and ordering system to Paytronix (a cloud-based customer experience management platform for restaurants and convenience stores). Here are the top 6 challenges faced while implementing this transition. 1. Store Information: Paytronix, the newer platform, failed to provide detailed store-related information compared to the older tool’s backend. To maintain consistency with the user experience, regardless of the transition, we had to find a way to ensure users continued to receive the same amount and quality of detailed information. 2. User Experience: A crucial challenge was ensuring that all features on Paytronix functioned precisely as they did with LevelUp, especially the in-store and online ordering systems, which primarily accounted for the user experience (for employees and customers). 3. Credit Card Management: Adding a credit card to a wallet and auto-recharge were important payment features included with LevelUp. Therefore, we had to find ways to replicate them with Paytronix. 4. Customizing Orders: LevelUp offered ample options to customize an order by allowing customers to choose from different toppings like Tapioca, Pudding, Nata Jelly, Red Beans, and more. This same functionality was complex to include with Paytronix. 5. Paytronix Migration: One of the biggest challenges was understanding Paytronix's operational landscape. To migrate successfully, we needed to understand the different Paytronix APIs and code bases. Only then could we match the behavior of features/functionalities offered by LevelUp. 6. Time-Constraints: As LevelUp was getting discontinued by a particular date, adhering to a strict timeline was imperative. Why Maruti Techlabs? Ann’s Boba Tea chose Maruti Techlabs as their partner due to our extensive experience developing and implementing innovative IT solutions, precise understanding of their problem, and detailed migration strategy. Our experts presented the potential challenges and proposed solutions to ensure a seamless transition. Furthermore, we time-boxed tasks and delivered on our committed timeline to conclude the entire migration before sunsetting the previous platform. This offered us ample time to conduct numerous tests on the new platform. Our technical prowess, reliable governance, and timely communication impressed our client the most. What made us an ideal partner was our commitment to delivering on time and within budget following a transparent process. Solution Ann’s in-store and mobile apps are operated via the same backend platform, LevelUp. Therefore, not switching would have caused significant disruptions with our client’s services, tainted their brand’s reputation, and incurred substantial monetary losses. Here’s how we approached the switch to Paytronix. We commenced with ‘Sprint Zero,’ a planning phase, before beginning active development. In this phase, we allotted two programmers to work on the same code (AKA pair programming) to gain clarity on the app’s original code, structure, and how it functioned. The programmers also reviewed different Paytronix APIs to help ease this transition. This approach helped us maneuver migration challenges. After a thorough analysis, we decided on a two-part solution and proposed working parallelly on both to meet the deadline. Phase 1: Firstly, we integrated the Paytronix online ordering website within the app to keep the online ordering experience intact. If developing the native application proves challenging and time-consuming, our client could deploy this solution to avoid downtime and disruptions. Phase 2: We parallelly created a replica of the app leveraging the Paytronix API for in-store and online ordering. This approach was more straightforward but required more development time. Using Paytronix, we created features like: User Onboarding (account creation)


Authentication


Online Payment


Restaurant Listing


Order Customization


Menu Categorization


Calculating & Redeeming Loyalty Points


Adding Tips


Tracking Orders via GPS The timely backend switch to Paytronix prevented service downtime and sales reductions. Ann’s Boba Tea continued to offer its services as it had earlier without causing any inconvenience to its customers or compromising its sales or reputation. Communication and Collaboration To deliver the project on schedule, we deployed a five-member team of 3 React Native developers, 1 QA engineer, and 1 Technical Project manager. Our primary source of communication was the Technical Lead at Ann’s Boba Tea. The project's total timeline was 3.5 months. Every Tuesday, we conducted a weekly call to discuss the progress, doubts, and other updates. Here are the platforms we used for communication. Slack: Daily Communication
Jira: Project Management
Zoom: Weekly Calls
Google Meet: Unplanned Calls Technology Stack Result Making this timely transition to Paytronix resulted in significant improvements and service perks. Here’s a brief list of these enhancements. Our timely completion of the platform (before its current backend platform sunsetted) resulted in no downtime in the online ordering services.


We facilitated a seamless transition to the new platform, ensuring no disruptions to the user experience.


The exquisite app experience significantly boosted its ratings on the App Store (4.7).


Our experts added extra layers to protect the data and enhance the app’s security.


The transition enhanced the app’s performance and reduced app glitches and crashes.


We designed a futuristic app that could adapt to new technological developments. Maruti Techlabs helped plan and execute the transition of the backend platform. This timely switch allowed Ann’s Boba Tea to offer continual services without disrupting their online and physical store services. If you, too, face such a situation and cannot decide on the next step, contact us today and let our experts devise the perfect strategy for your next tech upgrade. Our Development Process We follow Agile, Lean, & DevOps best practices to create a superior prototype that brings your users’ ideas to fruition through collaboration & rapid execution. Our top priority is quick reaction time & accessibility. We really want to be your extended team, so apart from the regular meetings, you can be sure that each of our team members is one phone call, email, or message away. Expertise Delivered Frontend, Backend & QA Industry Food and Beverage The Client Ann’s Boba Tea is an American bubble tea franchise (also known as Pearl Milk Tea or Boba Milk Tea). It was founded in 2010 and has over 350+ locations across the US. The tea is brewed at the perfect temperature with milk, fresh ingredients, and a unique recipe and presented innovatively. Customers can earn rewards for each order placed and redeem reward points against future orders. Disclaimer— The name Ann’s Boba Tea is a placeholder, as both parties have signed an NDA. Disclaimer— The Challenge Ann’s in-store and online ordering applications were created using LevelUp (a customer engagement and mobile payment platform) as the backend. However, LevelUp was being discontinued, so our client needed to transition its existing user data and ordering system to Paytronix (a cloud-based customer experience management platform for restaurants and convenience stores). Here are the top 6 challenges faced while implementing this transition. 1. Store Information: 1. Store Information: Paytronix, the newer platform, failed to provide detailed store-related information compared to the older tool’s backend. To maintain consistency with the user experience, regardless of the transition, we had to find a way to ensure users continued to receive the same amount and quality of detailed information. 2. User Experience: 2. User Experience: A crucial challenge was ensuring that all features on Paytronix functioned precisely as they did with LevelUp, especially the in-store and online ordering systems, which primarily accounted for the user experience (for employees and customers). 3. Credit Card Management: 3. Credit Card Management: Adding a credit card to a wallet and auto-recharge were important payment features included with LevelUp. Therefore, we had to find ways to replicate them with Paytronix. 4. Customizing Orders: 4. Customizing Orders: LevelUp offered ample options to customize an order by allowing customers to choose from different toppings like Tapioca, Pudding, Nata Jelly, Red Beans, and more. This same functionality was complex to include with Paytronix. 5. Paytronix Migration: 5. Paytronix Migration: One of the biggest challenges was understanding Paytronix's operational landscape. To migrate successfully, we needed to understand the different Paytronix APIs and code bases. Only then could we match the behavior of features/functionalities offered by LevelUp. 6. Time-Constraints: 6. Time-Constraints: As LevelUp was getting discontinued by a particular date, adhering to a strict timeline was imperative. Why Maruti Techlabs? Ann’s Boba Tea chose Maruti Techlabs as their partner due to our extensive experience developing and implementing innovative IT solutions, precise understanding of their problem, and detailed migration strategy. Our experts presented the potential challenges and proposed solutions to ensure a seamless transition. Furthermore, we time-boxed tasks and delivered on our committed timeline to conclude the entire migration before sunsetting the previous platform. This offered us ample time to conduct numerous tests on the new platform. Our technical prowess, reliable governance, and timely communication impressed our client the most. What made us an ideal partner was our commitment to delivering on time and within budget following a transparent process. Solution Ann’s in-store and mobile apps are operated via the same backend platform, LevelUp. Therefore, not switching would have caused significant disruptions with our client’s services, tainted their brand’s reputation, and incurred substantial monetary losses. Here’s how we approached the switch to Paytronix. We commenced with ‘Sprint Zero,’ a planning phase, before beginning active development. In this phase, we allotted two programmers to work on the same code (AKA pair programming) to gain clarity on the app’s original code, structure, and how it functioned. The programmers also reviewed different Paytronix APIs to help ease this transition. This approach helped us maneuver migration challenges. After a thorough analysis, we decided on a two-part solution and proposed working parallelly on both to meet the deadline. Phase 1: Firstly, we integrated the Paytronix online ordering website within the app to keep the online ordering experience intact. Phase 1: If developing the native application proves challenging and time-consuming, our client could deploy this solution to avoid downtime and disruptions. Phase 2: We parallelly created a replica of the app leveraging the Paytronix API for in-store and online ordering. This approach was more straightforward but required more development time. Phase 2: Using Paytronix, we created features like: User Onboarding (account creation) Authentication Online Payment Restaurant Listing Order Customization Menu Categorization Calculating & Redeeming Loyalty Points Adding Tips Tracking Orders via GPS User Onboarding (account creation) User Onboarding (account creation) Authentication Authentication Online Payment Online Payment Restaurant Listing Restaurant Listing Order Customization Order Customization Menu Categorization Menu Categorization Calculating & Redeeming Loyalty Points Calculating & Redeeming Loyalty Points Adding Tips Adding Tips Tracking Orders via GPS Tracking Orders via GPS The timely backend switch to Paytronix prevented service downtime and sales reductions. Ann’s Boba Tea continued to offer its services as it had earlier without causing any inconvenience to its customers or compromising its sales or reputation. Communication and Collaboration To deliver the project on schedule, we deployed a five-member team of 3 React Native developers, 1 QA engineer, and 1 Technical Project manager. Our primary source of communication was the Technical Lead at Ann’s Boba Tea. The project's total timeline was 3.5 months. Every Tuesday, we conducted a weekly call to discuss the progress, doubts, and other updates. Here are the platforms we used for communication. Slack: Daily Communication Jira: Project Management Zoom: Weekly Calls Google Meet: Unplanned Calls Slack: Daily Communication Jira: Project Management Zoom: Weekly Calls Google Meet: Unplanned Calls Technology Stack Result Making this timely transition to Paytronix resulted in significant improvements and service perks. Here’s a brief list of these enhancements. Our timely completion of the platform (before its current backend platform sunsetted) resulted in no downtime in the online ordering services. We facilitated a seamless transition to the new platform, ensuring no disruptions to the user experience. The exquisite app experience significantly boosted its ratings on the App Store (4.7). Our experts added extra layers to protect the data and enhance the app’s security. The transition enhanced the app’s performance and reduced app glitches and crashes. We designed a futuristic app that could adapt to new technological developments. Our timely completion of the platform (before its current backend platform sunsetted) resulted in no downtime in the online ordering services. Our timely completion of the platform (before its current backend platform sunsetted) resulted in no downtime in the online ordering services. We facilitated a seamless transition to the new platform, ensuring no disruptions to the user experience. We facilitated a seamless transition to the new platform, ensuring no disruptions to the user experience. The exquisite app experience significantly boosted its ratings on the App Store (4.7). The exquisite app experience significantly boosted its ratings on the App Store (4.7). Our experts added extra layers to protect the data and enhance the app’s security. Our experts added extra layers to protect the data and enhance the app’s security. The transition enhanced the app’s performance and reduced app glitches and crashes. The transition enhanced the app’s performance and reduced app glitches and crashes. We designed a futuristic app that could adapt to new technological developments. We designed a futuristic app that could adapt to new technological developments. Maruti Techlabs helped plan and execute the transition of the backend platform. This timely switch allowed Ann’s Boba Tea to offer continual services without disrupting their online and physical store services. If you, too, face such a situation and cannot decide on the next step, contact us today and let our experts devise the perfect strategy for your next tech upgrade. Our Development Process We follow Agile, Lean, & DevOps best practices to create a superior prototype that brings your users’ ideas to fruition through collaboration & rapid execution. Our top priority is quick reaction time & accessibility. We really want to be your extended team, so apart from the regular meetings, you can be sure that each of our team members is one phone call, email, or message away.

Facilitating a Seamless Backend Transition From LevelUp to Paytronix

Садзейнічанне плыўнаму бэкэнд-пераходу ад LevelUp да Paytronix

Улесняване на безпроблемен бекенд преход от LevelUp към Paytronix

লেভেলআপ থেকে পেট্রোনিক্সে একটি নির্বিঘ্ন ব্যাকএন্ড ট্রানজিশনের সুবিধা প্রদান

Usnadnění bezproblémového přechodu backendu z LevelUp na Paytronix

Facilitando una transición fluida del backend de LevelUp a Paytronix

LevelUp から Paytronix へのシームレスなバックエンド移行を促進

LevelUpдан Paytronixке үзгүлтүксүз өтүүнү жеңилдетүү

Ko faciliter Transition ya Backend sans soudure De LevelUp ti na Paytronix

Олеснување на беспрекорна транзиција на задниот дел од LevelUp до Paytronix

लेभलअपबाट पेट्रोनिक्समा निर्बाध ब्याकएन्ड ट्रान्जिसनलाई सहज बनाउँदै

LevelUp සිට Paytronix දක්වා බාධාවකින් තොරව පසුබිම් සංක්‍රාන්තියක් සඳහා පහසුකම් සැලසීම

Uľahčenie bezproblémového prechodu backendu z LevelUp na Paytronix

One day, you wake up and decide you can't live without TypeScript in your legacy JavaScript project anymore. That's what happened to me and my сolleagues, too, and now I want to tell you about our experience. About the project: JavaScript + jQuery + Webpack, no frameworks.
5+ years of enterprise.
1M+ unique users a month.
Growing with new features. Step 1. Understanding the needs The longer you develop an app, the more complex it becomes. With time, we realized that we couldn't ignore the following issues anymore: Increase in codebase complexity.
Difficulty in understanding the project.
Decline in relevancy of the app from a tech point of view.
Lack of interest among developers working with the same old technologies. Why TypeScript? Besides the obvious benefits, such as handy static typing, a self-documented codebase, and enhanced code reliability, we found a few nice advantages for our project specifically: TypeScript could help us: Handle increasing codebase complexity by implementing strict rules and following them.
Make the codebase more understandable with TypeScript’s self-documenting capabilities.
Keep the project in line with modern technologies.
Maintain motivation within the development team to learn and develop. Step 2. Convincing the management team These benefits were enough to convince the development team to adopt TS, but we still had to convince the management team of the reason to spend money on implementing TypeScript. The points above didn't seem convincing enough to explain what management would get from this transition. Well, we had some arguments here, too. TypeScript could help the management team: Save time ( == money) on possible bug fixing.
Decrease the risks of costly bugs appearing in production.
Slow down the growing backlog.
Decrease the cost of onboarding new developers to the project with the help of improved documentation.
Increase developer productivity. As a result, we managed to get approval and started the task! Step 3. Adding TypeScript to the project First, we needed to install TypeScript as a dev dependency: npm install typescript Also, we needed a basictsconfig.json file to make it work inside the project as recommended: {
  "compilerOptions": {
    "target": "ES2022",
    "module": "NodeNext",
    "strict": true
  }
} Of course, it wasn't that easy, right? Let's see what issues we had. Since we're using Webpack in our project, we had to show it how to approach TS files. To do this, we added a ts-loader package: npm install --save-dev ts-loaderand added parameters to the Webpack config file: module.exports = {
  module: {
    rules: [{
        test: /\\.ts$/,
        exclude: /node_modules/,
        use: 'ts-loader'
      }]
  }
} Also, there was a need to tell our linter to check TS files, too: module.exports = {
  plugins: [
    new ESLintPlugin({
      extensions: './*.{js,ts}',
      files: './*.{js,ts}'
    })
  ]
} Since we are using jQuery in our project (jQuery is still alive in 2025!), we needed types for jQuery: npm install --save-dev @types/jquery Voila! TypeScript was now working in our project. But what next? Our project still completely consisted of JS. How did we transition it to TS? Step 4. Transitioning the project to TS We couldn't afford to convert all the JS files to TS simultaneously, so we decided to do this gradually. We chose the following strategy: We used TypeScript for newly created files


Since the project is still being developed, components are getting redesigned and constantly refactored, so we areexpected to create new files.


We converted existing JS to TS when possible
Whenever we had the rare opportunity to take a pause from developing features, we dedicated it to technical improvements like rewriting entire files to TS. This is still a work in progress, but we have some results after 1 year of the transition: JavaScript to TypeScript ratio in the project
Let's compare the number of lines of code for both JS and TS inside the project:JS: 9190 total(76.5%)TS: 2812 total(23.5%)Not bad so far!


Decreased backlog
For the first time in many years, we managed to resolve most of our backlog, which, of course, is a result of different parameters, but TypeScript still contributed to this achievement.


The Dev team acquired new skills
This process was also quite fun for some of our developers who weren't very familiar with TypeScript. It kept them entertained and motivated to reach for new heights in their professional lives! I collected some thoughts from my teammates on their current experience with TS, especially from those who hadn't used it or other typings in programming before: It took some time to get familiar with TS, and it felt difficult at the beginning, but eventually, they got used to it and now see the benefits of using TS.
The best thing is that TypeScript highlights the expected type or the wrong ones that were passed. This is really handy and saves time.
TypeScript adds predictability when it comes to the complex logic of components (that's what I meant by "handle increasing codebase complexity"!)
A downside is that it requires a bit more time to write in TS, but it is still worth it.
Sometimes, creating the right type can be challenging (thank goodness we love challenges)
There were an enormous number of cases when errors were prevented before even running the code.
Our code became more readable and self-documented.
People like working with TypeScript because it can be exciting. If you've read the article to this point, this is your sign to put some TypeScript in your legacy project! It's worth it and not that painful after all. One day, you wake up and decide you can't live without TypeScript in your legacy JavaScript project anymore. That's what happened to me and my сolleagues, too, and now I want to tell you about our experience. About the project: JavaScript + jQuery + Webpack, no frameworks. 5+ years of enterprise. 1M+ unique users a month. Growing with new features. JavaScript + jQuery + Webpack, no frameworks. 5+ years of enterprise. 1M+ unique users a month. Growing with new features. Step 1. Understanding the needs Step 1. Understanding the needs The longer you develop an app, the more complex it becomes. With time, we realized that we couldn't ignore the following issues anymore: Increase in codebase complexity. Difficulty in understanding the project. Decline in relevancy of the app from a tech point of view. Lack of interest among developers working with the same old technologies. Increase in codebase complexity. Difficulty in understanding the project. Decline in relevancy of the app from a tech point of view. Lack of interest among developers working with the same old technologies. Why TypeScript? Besides the obvious benefits, such as handy static typing, a self-documented codebase, and enhanced code reliability, we found a few nice advantages for our project specifically: TypeScript could help us: Handle increasing codebase complexity by implementing strict rules and following them. Make the codebase more understandable with TypeScript’s self-documenting capabilities. Keep the project in line with modern technologies. Maintain motivation within the development team to learn and develop. Handle increasing codebase complexity by implementing strict rules and following them. Make the codebase more understandable with TypeScript’s self-documenting capabilities. Keep the project in line with modern technologies. Maintain motivation within the development team to learn and develop. Step 2. Convincing the management team Step 2. Convincing the management team These benefits were enough to convince the development team to adopt TS, but we still had to convince the management team of the reason to spend money on implementing TypeScript. The points above didn't seem convincing enough to explain what management would get from this transition. Well, we had some arguments here, too. TypeScript could help the management team: Save time ( == money) on possible bug fixing. Decrease the risks of costly bugs appearing in production. Slow down the growing backlog. Decrease the cost of onboarding new developers to the project with the help of improved documentation. Increase developer productivity. Save time ( == money) on possible bug fixing. Decrease the risks of costly bugs appearing in production. Slow down the growing backlog. Decrease the cost of onboarding new developers to the project with the help of improved documentation. Increase developer productivity. As a result, we managed to get approval and started the task! Step 3. Adding TypeScript to the project Step 3. Adding TypeScript to the project First, we needed to install TypeScript as a dev dependency: npm install typescript npm install typescript Also, we needed a basic tsconfig.json file to make it work inside the project as recommended: tsconfig.json {
  "compilerOptions": {
    "target": "ES2022",
    "module": "NodeNext",
    "strict": true
  }
} {
  "compilerOptions": {
    "target": "ES2022",
    "module": "NodeNext",
    "strict": true
  }
} Of course, it wasn't that easy, right? Let's see what issues we had. Since we're using Webpack in our project, we had to show it how to approach TS files. To do this, we added a ts-loader package: ts-loader npm install --save-dev ts-loader and added parameters to the Webpack config file: module.exports = {
  module: {
    rules: [{
        test: /\\.ts$/,
        exclude: /node_modules/,
        use: 'ts-loader'
      }]
  }
} module.exports = {
  module: {
    rules: [{
        test: /\\.ts$/,
        exclude: /node_modules/,
        use: 'ts-loader'
      }]
  }
} Also, there was a need to tell our linter to check TS files, too: module.exports = {
  plugins: [
    new ESLintPlugin({
      extensions: './*.{js,ts}',
      files: './*.{js,ts}'
    })
  ]
} module.exports = {
  plugins: [
    new ESLintPlugin({
      extensions: './*.{js,ts}',
      files: './*.{js,ts}'
    })
  ]
} Since we are using jQuery in our project (jQuery is still alive in 2025!), we needed types for jQuery: npm install --save-dev @types/jquery npm install --save-dev @types/jquery Voila! TypeScript was now working in our project. But what next? Our project still completely consisted of JS. How did we transition it to TS? Step 4. Transitioning the project to TS Step 4. Transitioning the project to TS We couldn't afford to convert all the JS files to TS simultaneously, so we decided to do this gradually. We chose the following strategy: We used TypeScript for newly created files Since the project is still being developed, components are getting redesigned and constantly refactored, so we areexpected to create new files. We converted existing JS to TS when possible
Whenever we had the rare opportunity to take a pause from developing features, we dedicated it to technical improvements like rewriting entire files to TS. We used TypeScript for newly created files We used TypeScript for newly created files Since the project is still being developed, components are getting redesigned and constantly refactored, so we areexpected to create new files. Since the project is still being developed, components are getting redesigned and constantly refactored, so we are expected to create new files. expected We converted existing JS to TS when possible Whenever we had the rare opportunity to take a pause from developing features, we dedicated it to technical improvements like rewriting entire files to TS. We converted existing JS to TS when possible Whenever we had the rare opportunity to take a pause from developing features, we dedicated it to technical improvements like rewriting entire files to TS. This is still a work in progress, but we have some results after 1 year of the transition: JavaScript to TypeScript ratio in the project
Let's compare the number of lines of code for both JS and TS inside the project:JS: 9190 total(76.5%)TS: 2812 total(23.5%)Not bad so far! Decreased backlog
For the first time in many years, we managed to resolve most of our backlog, which, of course, is a result of different parameters, but TypeScript still contributed to this achievement. The Dev team acquired new skills
This process was also quite fun for some of our developers who weren't very familiar with TypeScript. It kept them entertained and motivated to reach for new heights in their professional lives! JavaScript to TypeScript ratio in the project Let's compare the number of lines of code for both JS and TS inside the project:JS: 9190 total(76.5%)TS: 2812 total(23.5%)Not bad so far! JavaScript to TypeScript ratio in the project Let's compare the number of lines of code for both JS and TS inside the project: JS: 9190 total (76.5%) TS: 2812 total (23.5%) Not bad so far! JS: 9190 total TS: 2812 total Decreased backlog For the first time in many years, we managed to resolve most of our backlog, which, of course, is a result of different parameters, but TypeScript still contributed to this achievement. Decreased backlog For the first time in many years, we managed to resolve most of our backlog, which, of course, is a result of different parameters, but TypeScript still contributed to this achievement. The Dev team acquired new skills This process was also quite fun for some of our developers who weren't very familiar with TypeScript. It kept them entertained and motivated to reach for new heights in their professional lives! The Dev team acquired new skills This process was also quite fun for some of our developers who weren't very familiar with TypeScript. It kept them entertained and motivated to reach for new heights in their professional lives! I collected some thoughts from my teammates on their current experience with TS, especially from those who hadn't used it or other typings in programming before: It took some time to get familiar with TS, and it felt difficult at the beginning, but eventually, they got used to it and now see the benefits of using TS. The best thing is that TypeScript highlights the expected type or the wrong ones that were passed. This is really handy and saves time. TypeScript adds predictability when it comes to the complex logic of components (that's what I meant by "handle increasing codebase complexity"!) A downside is that it requires a bit more time to write in TS, but it is still worth it. Sometimes, creating the right type can be challenging (thank goodness we love challenges) There were an enormous number of cases when errors were prevented before even running the code. Our code became more readable and self-documented. People like working with TypeScript because it can be exciting. It took some time to get familiar with TS, and it felt difficult at the beginning, but eventually, they got used to it and now see the benefits of using TS. The best thing is that TypeScript highlights the expected type or the wrong ones that were passed. This is really handy and saves time. TypeScript adds predictability when it comes to the complex logic of components (that's what I meant by "handle increasing codebase complexity"!) A downside is that it requires a bit more time to write in TS, but it is still worth it. Sometimes, creating the right type can be challenging (thank goodness we love challenges) There were an enormous number of cases when errors were prevented before even running the code. Our code became more readable and self-documented. People like working with TypeScript because it can be exciting. If you've read the article to this point, this is your sign to put some TypeScript in your legacy project! It's worth it and not that painful after all.

Transitioning From JavaScript to TypeScript Is Easier Than You Think

Apache Kafka provides schema management capabilities through the Schema Registry, including various levels of compatibility. In this article, we will discuss three types of transitive compatibility: BACKWARD_TRANSITIVE, FORWARD_TRANSITIVE, and FULL_TRANSITIVE. Additionally, we will analyze their pros, cons, and provide code examples. BACKWARD_TRANSITIVE Description Backward transitive compatibility means that a new version of the schema must be compatible with all previous versions. This is useful in systems with a long data lifecycle. Code Example curl -X PUT \
  -H "Content-Type: application/vnd.schemaregistry.v1+json" \
  --data '{"compatibility": "BACKWARD_TRANSITIVE"}' \
  http://localhost:8081/config/<subject_name> Java Code Example import io.confluent.kafka.schemaregistry.client.CachedSchemaRegistryClient;
import io.confluent.kafka.schemaregistry.client.SchemaRegistryClient;
import io.confluent.kafka.schemaregistry.rest.exceptions.RestClientException;

import java.io.IOException;

public class BackwardTransitiveExample {
    public static void main(String[] args) throws IOException, RestClientException {
        String schemaRegistryUrl = "http://localhost:8081";
        SchemaRegistryClient client = new CachedSchemaRegistryClient(schemaRegistryUrl, 10);

        String subject = "<subject_name>";
        String compatibility = "BACKWARD_TRANSITIVE";

        // Set compatibility type
        client.updateCompatibility(subject, compatibility);

        // Check current compatibility type
        String currentCompatibility = client.getCompatibility(subject);
        System.out.println("Current compatibility level: " + currentCompatibility);
    }
} Pros ✅ Ensures compatibility with historical data.
✅ Useful for long-term data storage. Cons ❌ May restrict adding new fields or changing the structure. FORWARD_TRANSITIVE Description Forward transitive compatibility requires that a new version of the schema be compatible with all future versions. This is useful when consumers are updated asynchronously with producers. Code Example curl -X PUT \
  -H "Content-Type: application/vnd.schemaregistry.v1+json" \
  --data '{"compatibility": "FORWARD_TRANSITIVE"}' \
  http://localhost:8081/config/<subject_name> Java Code Example import io.confluent.kafka.schemaregistry.client.CachedSchemaRegistryClient;
import io.confluent.kafka.schemaregistry.client.SchemaRegistryClient;
import io.confluent.kafka.schemaregistry.rest.exceptions.RestClientException;

import java.io.IOException;

public class ForwardTransitiveExample {
    public static void main(String[] args) throws IOException, RestClientException {
        String schemaRegistryUrl = "http://localhost:8081";
        SchemaRegistryClient client = new CachedSchemaRegistryClient(schemaRegistryUrl, 10);

        String subject = "<subject_name>";
        String compatibility = "FORWARD_TRANSITIVE";

        // Set compatibility type
        client.updateCompatibility(subject, compatibility);

        // Check current compatibility type
        String currentCompatibility = client.getCompatibility(subject);
        System.out.println("Current compatibility level: " + currentCompatibility);
    }
} Pros ✅ Ensures stability for old consumers with new data. ✅ Convenient for systems with asynchronous updates. Cons ❌ Does not guarantee compatibility with historical data. FULL_TRANSITIVE Description Full transitive compatibility combines the requirements of backward and forward compatibility. A new schema version must be compatible with both previous and future versions. Code Example curl -X PUT \
  -H "Content-Type: application/vnd.schemaregistry.v1+json" \
  --data '{"compatibility": "FULL_TRANSITIVE"}' \
  http://localhost:8081/config/<subject_name> Java Code Example import io.confluent.kafka.schemaregistry.client.CachedSchemaRegistryClient;
import io.confluent.kafka.schemaregistry.client.SchemaRegistryClient;
import io.confluent.kafka.schemaregistry.rest.exceptions.RestClientException;

import java.io.IOException;

public class FullTransitiveExample {
    public static void main(String[] args) throws IOException, RestClientException {
        String schemaRegistryUrl = "http://localhost:8081";
        SchemaRegistryClient client = new CachedSchemaRegistryClient(schemaRegistryUrl, 10);

        String subject = "<subject_name>";
        String compatibility = "FULL_TRANSITIVE";

        // Set compatibility type
        client.updateCompatibility(subject, compatibility);

        // Check current compatibility type
        String currentCompatibility = client.getCompatibility(subject);
        System.out.println("Current compatibility level: " + currentCompatibility);
    }
} Pros ✅ Maximum flexibility and resilience.
✅ Guarantees compatibility with all schema versions. Cons ❌ The strictest compatibility type.
❌ Requires careful planning for schema changes. Comparison Table Compatibility Type

Compatibility with Past Versions

Compatibility with Future Versions

Ease of Use

Applicability



BACKWARD_TRANSITIVE

✅

❌

Medium

Long-term data storage



FORWARD_TRANSITIVE

❌

✅

Medium

Asynchronous updates



FULL_TRANSITIVE

✅

✅

Low

Maximum resilience These compatibility types allow you to configure the system to meet your stability and flexibility requirements. The correct choice depends on your system architecture and use cases. Apache Kafka provides schema management capabilities through the Schema Registry, including various levels of compatibility. In this article, we will discuss three types of transitive compatibility: BACKWARD_TRANSITIVE, FORWARD_TRANSITIVE, and FULL_TRANSITIVE. Additionally, we will analyze their pros, cons, and provide code examples. BACKWARD_TRANSITIVE Description Backward transitive compatibility means that a new version of the schema must be compatible with all previous versions. This is useful in systems with a long data lifecycle. all Code Example curl -X PUT \
  -H "Content-Type: application/vnd.schemaregistry.v1+json" \
  --data '{"compatibility": "BACKWARD_TRANSITIVE"}' \
  http://localhost:8081/config/<subject_name> curl -X PUT \
  -H "Content-Type: application/vnd.schemaregistry.v1+json" \
  --data '{"compatibility": "BACKWARD_TRANSITIVE"}' \
  http://localhost:8081/config/<subject_name> Java Code Example import io.confluent.kafka.schemaregistry.client.CachedSchemaRegistryClient;
import io.confluent.kafka.schemaregistry.client.SchemaRegistryClient;
import io.confluent.kafka.schemaregistry.rest.exceptions.RestClientException;

import java.io.IOException;

public class BackwardTransitiveExample {
    public static void main(String[] args) throws IOException, RestClientException {
        String schemaRegistryUrl = "http://localhost:8081";
        SchemaRegistryClient client = new CachedSchemaRegistryClient(schemaRegistryUrl, 10);

        String subject = "<subject_name>";
        String compatibility = "BACKWARD_TRANSITIVE";

        // Set compatibility type
        client.updateCompatibility(subject, compatibility);

        // Check current compatibility type
        String currentCompatibility = client.getCompatibility(subject);
        System.out.println("Current compatibility level: " + currentCompatibility);
    }
} import io.confluent.kafka.schemaregistry.client.CachedSchemaRegistryClient;
import io.confluent.kafka.schemaregistry.client.SchemaRegistryClient;
import io.confluent.kafka.schemaregistry.rest.exceptions.RestClientException;

import java.io.IOException;

public class BackwardTransitiveExample {
    public static void main(String[] args) throws IOException, RestClientException {
        String schemaRegistryUrl = "http://localhost:8081";
        SchemaRegistryClient client = new CachedSchemaRegistryClient(schemaRegistryUrl, 10);

        String subject = "<subject_name>";
        String compatibility = "BACKWARD_TRANSITIVE";

        // Set compatibility type
        client.updateCompatibility(subject, compatibility);

        // Check current compatibility type
        String currentCompatibility = client.getCompatibility(subject);
        System.out.println("Current compatibility level: " + currentCompatibility);
    }
} Pros ✅ Ensures compatibility with historical data. ✅ Useful for long-term data storage. ✅ Ensures compatibility with historical data. ✅ Useful for long-term data storage. Cons ❌ May restrict adding new fields or changing the structure. ❌ May restrict adding new fields or changing the structure. FORWARD_TRANSITIVE Description Forward transitive compatibility requires that a new version of the schema be compatible with all future versions. This is useful when consumers are updated asynchronously with producers. all Code Example curl -X PUT \
  -H "Content-Type: application/vnd.schemaregistry.v1+json" \
  --data '{"compatibility": "FORWARD_TRANSITIVE"}' \
  http://localhost:8081/config/<subject_name> curl -X PUT \
  -H "Content-Type: application/vnd.schemaregistry.v1+json" \
  --data '{"compatibility": "FORWARD_TRANSITIVE"}' \
  http://localhost:8081/config/<subject_name> Java Code Example import io.confluent.kafka.schemaregistry.client.CachedSchemaRegistryClient;
import io.confluent.kafka.schemaregistry.client.SchemaRegistryClient;
import io.confluent.kafka.schemaregistry.rest.exceptions.RestClientException;

import java.io.IOException;

public class ForwardTransitiveExample {
    public static void main(String[] args) throws IOException, RestClientException {
        String schemaRegistryUrl = "http://localhost:8081";
        SchemaRegistryClient client = new CachedSchemaRegistryClient(schemaRegistryUrl, 10);

        String subject = "<subject_name>";
        String compatibility = "FORWARD_TRANSITIVE";

        // Set compatibility type
        client.updateCompatibility(subject, compatibility);

        // Check current compatibility type
        String currentCompatibility = client.getCompatibility(subject);
        System.out.println("Current compatibility level: " + currentCompatibility);
    }
} import io.confluent.kafka.schemaregistry.client.CachedSchemaRegistryClient;
import io.confluent.kafka.schemaregistry.client.SchemaRegistryClient;
import io.confluent.kafka.schemaregistry.rest.exceptions.RestClientException;

import java.io.IOException;

public class ForwardTransitiveExample {
    public static void main(String[] args) throws IOException, RestClientException {
        String schemaRegistryUrl = "http://localhost:8081";
        SchemaRegistryClient client = new CachedSchemaRegistryClient(schemaRegistryUrl, 10);

        String subject = "<subject_name>";
        String compatibility = "FORWARD_TRANSITIVE";

        // Set compatibility type
        client.updateCompatibility(subject, compatibility);

        // Check current compatibility type
        String currentCompatibility = client.getCompatibility(subject);
        System.out.println("Current compatibility level: " + currentCompatibility);
    }
} Pros ✅ Ensures stability for old consumers with new data. ✅ Ensures stability for old consumers with new data. ✅ Convenient for systems with asynchronous updates. ✅ Convenient for systems with asynchronous updates. Cons ❌ Does not guarantee compatibility with historical data. ❌ Does not guarantee compatibility with historical data. FULL_TRANSITIVE Description Full transitive compatibility combines the requirements of backward and forward compatibility. A new schema version must be compatible with both previous and future versions. Code Example curl -X PUT \
  -H "Content-Type: application/vnd.schemaregistry.v1+json" \
  --data '{"compatibility": "FULL_TRANSITIVE"}' \
  http://localhost:8081/config/<subject_name> curl -X PUT \
  -H "Content-Type: application/vnd.schemaregistry.v1+json" \
  --data '{"compatibility": "FULL_TRANSITIVE"}' \
  http://localhost:8081/config/<subject_name> Java Code Example import io.confluent.kafka.schemaregistry.client.CachedSchemaRegistryClient;
import io.confluent.kafka.schemaregistry.client.SchemaRegistryClient;
import io.confluent.kafka.schemaregistry.rest.exceptions.RestClientException;

import java.io.IOException;

public class FullTransitiveExample {
    public static void main(String[] args) throws IOException, RestClientException {
        String schemaRegistryUrl = "http://localhost:8081";
        SchemaRegistryClient client = new CachedSchemaRegistryClient(schemaRegistryUrl, 10);

        String subject = "<subject_name>";
        String compatibility = "FULL_TRANSITIVE";

        // Set compatibility type
        client.updateCompatibility(subject, compatibility);

        // Check current compatibility type
        String currentCompatibility = client.getCompatibility(subject);
        System.out.println("Current compatibility level: " + currentCompatibility);
    }
} import io.confluent.kafka.schemaregistry.client.CachedSchemaRegistryClient;
import io.confluent.kafka.schemaregistry.client.SchemaRegistryClient;
import io.confluent.kafka.schemaregistry.rest.exceptions.RestClientException;

import java.io.IOException;

public class FullTransitiveExample {
    public static void main(String[] args) throws IOException, RestClientException {
        String schemaRegistryUrl = "http://localhost:8081";
        SchemaRegistryClient client = new CachedSchemaRegistryClient(schemaRegistryUrl, 10);

        String subject = "<subject_name>";
        String compatibility = "FULL_TRANSITIVE";

        // Set compatibility type
        client.updateCompatibility(subject, compatibility);

        // Check current compatibility type
        String currentCompatibility = client.getCompatibility(subject);
        System.out.println("Current compatibility level: " + currentCompatibility);
    }
} Pros ✅ Maximum flexibility and resilience. ✅ Guarantees compatibility with all schema versions. ✅ Maximum flexibility and resilience. ✅ Guarantees compatibility with all schema versions. Cons ❌ The strictest compatibility type. ❌ Requires careful planning for schema changes. ❌ The strictest compatibility type. ❌ Requires careful planning for schema changes. Comparison Table Compatibility Type

Compatibility with Past Versions

Compatibility with Future Versions

Ease of Use

Applicability



BACKWARD_TRANSITIVE

✅

❌

Medium

Long-term data storage



FORWARD_TRANSITIVE

❌

✅

Medium

Asynchronous updates



FULL_TRANSITIVE

✅

✅

Low

Maximum resilience Compatibility Type

Compatibility with Past Versions

Compatibility with Future Versions

Ease of Use

Applicability BACKWARD_TRANSITIVE

✅

❌

Medium

Long-term data storage FORWARD_TRANSITIVE

❌

✅

Medium

Asynchronous updates FULL_TRANSITIVE

✅

✅

Low

Maximum resilience Compatibility Type Compatibility with Past Versions Compatibility with Future Versions Ease of Use Applicability Compatibility Type Compatibility Type Compatibility with Past Versions Compatibility with Past Versions Compatibility with Future Versions Compatibility with Future Versions Ease of Use Ease of Use Applicability Applicability BACKWARD_TRANSITIVE ✅ ❌ Medium Long-term data storage BACKWARD_TRANSITIVE BACKWARD_TRANSITIVE ✅ ✅ ❌ ❌ Medium Medium Long-term data storage Long-term data storage FORWARD_TRANSITIVE ❌ ✅ Medium Asynchronous updates FORWARD_TRANSITIVE FORWARD_TRANSITIVE ❌ ❌ ✅ ✅ Medium Medium Asynchronous updates Asynchronous updates FULL_TRANSITIVE ✅ ✅ Low Maximum resilience FULL_TRANSITIVE FULL_TRANSITIVE ✅ ✅ ✅ ✅ Low Low Maximum resilience Maximum resilience These compatibility types allow you to configure the system to meet your stability and flexibility requirements. The correct choice depends on your system architecture and use cases.

Transitive Compatibility Types in Schema Registry for Apache Kafka

IPv6: Managing The Transition

DUBAI, UAE, October 30th, 2024/Chainwire/--In light of recent changes, DWF Labs is pleased to announce that Lingling Jiang, our esteemed partner for Business Development, will be stepping up to lead the company’s strategic initiatives in this area. With a proven track record of driving growth and creating meaningful partnerships, Lingling will be taking over the roles and responsibilities necessary to support and expand our work with valued partners and collaborators. This transition is part of our ongoing commitment to fostering a resilient, forward-focused business environment that remains steadfast in supporting our portfolio companies. Lingling brings a wealth of experience to her new role, positioning her as a key leader in DWF Labs’s Business Development and strategic initiatives. With over two years at DWF Labs as the Business Partner of Business Development and previously serving as Head of Regional Sales in Asia, Lingling has demonstrated her ability to drive cross-functional collaboration, optimise business operations, and build sustainable partnerships across the globe. Her tenure as Head of Hong Kong further solidified her expertise in regional and global market dynamics, fostering strong relationships within the business ecosystem. This expanded role will include active participation in corporate decision-making, leading business development strategies, and representing DWF Labs at industry events worldwide. Her dedication to fostering impactful collaborations will strengthen our support for both new and existing partners, ensuring continuity and reinforcing our commitment to providing exceptional service. “We are confident that Lingling’s expertise and leadership will play a crucial role in shaping our strategic direction,” said Andrei Grachev, Managing Partner of DWF Labs. “Her deep understanding of our industry and dedication to excellence make her the ideal leader to take our business development efforts to new heights.” We look forward to the continued growth and success of DWF Labs under Lingling’s leadership in Business Development. We remain committed to our mission of driving innovation, creating value for our partners, and supporting the success of our portfolio companies. Contact Head of Marketing Lynn Chia pr@dwf-labs.com This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program. Learn more about the program here DUBAI, UAE, October 30th, 2024/Chainwire/--In light of recent changes, DWF Labs is pleased to announce that Lingling Jiang, our esteemed partner for Business Development, will be stepping up to lead the company’s strategic initiatives in this area. With a proven track record of driving growth and creating meaningful partnerships, Lingling will be taking over the roles and responsibilities necessary to support and expand our work with valued partners and collaborators. This transition is part of our ongoing commitment to fostering a resilient, forward-focused business environment that remains steadfast in supporting our portfolio companies. Lingling brings a wealth of experience to her new role, positioning her as a key leader in DWF Labs’s Business Development and strategic initiatives. With over two years at DWF Labs as the Business Partner of Business Development and previously serving as Head of Regional Sales in Asia, Lingling has demonstrated her ability to drive cross-functional collaboration, optimise business operations, and build sustainable partnerships across the globe. Her tenure as Head of Hong Kong further solidified her expertise in regional and global market dynamics, fostering strong relationships within the business ecosystem. This expanded role will include active participation in corporate decision-making, leading business development strategies, and representing DWF Labs at industry events worldwide. Her dedication to fostering impactful collaborations will strengthen our support for both new and existing partners, ensuring continuity and reinforcing our commitment to providing exceptional service. “We are confident that Lingling’s expertise and leadership will play a crucial role in shaping our strategic direction,” said Andrei Grachev, Managing Partner of DWF Labs. “Her deep understanding of our industry and dedication to excellence make her the ideal leader to take our business development efforts to new heights.” “We are confident that Lingling’s expertise and leadership will play a crucial role in shaping our strategic direction,” said Andrei Grachev, Managing Partner of DWF Labs. “Her deep understanding of our industry and dedication to excellence make her the ideal leader to take our business development efforts to new heights.” We look forward to the continued growth and success of DWF Labs under Lingling’s leadership in Business Development. We remain committed to our mission of driving innovation, creating value for our partners, and supporting the success of our portfolio companies. Contact Head of Marketing Lynn Chia pr@dwf-labs.com This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program. Learn more about the program here This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program. Learn more about the program here here

DWF Labs Announces Leadership Transition In Business Development

DWF Labs annoncerer lederskabsovergang i forretningsudvikling

DWF Labs anuncia transición de liderazgo en desarrollo empresarial

DWF Labs ilmoittaa johtajuuden siirtymisestä liiketoiminnan kehityksessä

DWF Labs、事業開発におけるリーダーシップの移行を発表

DWF Labs აცხადებს ლიდერობის გადასვლას ბიზნესის განვითარებაში

DWF Labs бизнести өнүктүрүүдө лидерликке өтүүнү жарыялайт

DWF Labs Esakoli Transition Ya Leadship Na Développement Ya Ba Affaires

DWF Labs dia manambara ny Tetezamita mpitarika eo amin'ny fampandrosoana ny fandraharahana

DWF ल्याबहरूले व्यापार विकासमा नेतृत्व संक्रमणको घोषणा गर्दछ

DWF Labs anuncia transição de liderança em desenvolvimento de negócios

Maabara ya DWF Yatangaza Mpito wa Uongozi Katika Maendeleo ya Biashara

DWF Labs ประกาศการเปลี่ยนแปลงความเป็นผู้นำในการพัฒนาธุรกิจ

Understanding requestAnimationFrame, Linear Interpolation, and CSS Transitions in Web Animations

Day 10: Smooth as Butter Transitions 🌀 In the tenth post of the #30DaysOfSwift series, we’re diving into Custom Transitions and Animations to create seamless page/view transitions in SwiftUI. With SwiftUI’s built-in animation tools, you can give your app a smooth, polished look when users navigate between different views. Steps to Create Custom Transitions: Set Up the Views and Transitions: Start by making two views: a home screen and a detail screen, and animate the transition between them using a custom transition. import SwiftUI

struct CustomTransitionsView: View {
    @State private var showDetailView = false

    var body: some View {
        ZStack {
            if showDetailView {
                DetailView()
                    .transition(.move(edge: .trailing)) // Custom transition
                    .zIndex(1) // Ensure this view is in front during transition
            } else {
                HomeView()
                    .transition(.move(edge: .leading)) // Custom transition
            }
        }
        .animation(.easeInOut(duration: 0.5), value: showDetailView) // Smooth animation
        .onTapGesture {
            // Toggle between views on tap
            withAnimation {
                showDetailView.toggle()
            }
        }
    }
}

struct HomeView: View {
    var body: some View {
        VStack {
            Text("Home Screen")
                .font(.largeTitle)
                .fontWeight(.bold)

            Image(systemName: "house.fill")
                .font(.system(size: 80))
                .foregroundColor(.blue)
        }
    }
}

struct DetailView: View {
    var body: some View {
        VStack {
            Text("Detail Screen")
                .font(.largeTitle)
                .fontWeight(.bold)

            Image(systemName: "magnifyingglass")
                .font(.system(size: 80))
                .foregroundColor(.green)
        }
    }
} How are you going to use it? Let me know :) Happy Coding! Day 10: Smooth as Butter Transitions 🌀 Day 10: Smooth as Butter Transitions In the tenth post of the #30DaysOfSwift series, we’re diving into Custom Transitions and Animations to create seamless page/view transitions in SwiftUI. With SwiftUI’s built-in animation tools, you can give your app a smooth, polished look when users navigate between different views. Steps to Create Custom Transitions: Set Up the Views and Transitions: Start by making two views: a home screen and a detail screen, and animate the transition between them using a custom transition. import SwiftUI

struct CustomTransitionsView: View {
    @State private var showDetailView = false

    var body: some View {
        ZStack {
            if showDetailView {
                DetailView()
                    .transition(.move(edge: .trailing)) // Custom transition
                    .zIndex(1) // Ensure this view is in front during transition
            } else {
                HomeView()
                    .transition(.move(edge: .leading)) // Custom transition
            }
        }
        .animation(.easeInOut(duration: 0.5), value: showDetailView) // Smooth animation
        .onTapGesture {
            // Toggle between views on tap
            withAnimation {
                showDetailView.toggle()
            }
        }
    }
}

struct HomeView: View {
    var body: some View {
        VStack {
            Text("Home Screen")
                .font(.largeTitle)
                .fontWeight(.bold)

            Image(systemName: "house.fill")
                .font(.system(size: 80))
                .foregroundColor(.blue)
        }
    }
}

struct DetailView: View {
    var body: some View {
        VStack {
            Text("Detail Screen")
                .font(.largeTitle)
                .fontWeight(.bold)

            Image(systemName: "magnifyingglass")
                .font(.system(size: 80))
                .foregroundColor(.green)
        }
    }
} import SwiftUI

struct CustomTransitionsView: View {
    @State private var showDetailView = false

    var body: some View {
        ZStack {
            if showDetailView {
                DetailView()
                    .transition(.move(edge: .trailing)) // Custom transition
                    .zIndex(1) // Ensure this view is in front during transition
            } else {
                HomeView()
                    .transition(.move(edge: .leading)) // Custom transition
            }
        }
        .animation(.easeInOut(duration: 0.5), value: showDetailView) // Smooth animation
        .onTapGesture {
            // Toggle between views on tap
            withAnimation {
                showDetailView.toggle()
            }
        }
    }
}

struct HomeView: View {
    var body: some View {
        VStack {
            Text("Home Screen")
                .font(.largeTitle)
                .fontWeight(.bold)

            Image(systemName: "house.fill")
                .font(.system(size: 80))
                .foregroundColor(.blue)
        }
    }
}

struct DetailView: View {
    var body: some View {
        VStack {
            Text("Detail Screen")
                .font(.largeTitle)
                .fontWeight(.bold)

            Image(systemName: "magnifyingglass")
                .font(.system(size: 80))
                .foregroundColor(.green)
        }
    }
} How are you going to use it? Let me know :) Happy Coding! Happy Coding!

How to Create Custom Transitions in iOS 18 - #30DaysOfSwift

Popular Telegram-based clicker game Rocky Rabbit just announced its transition from its Tap-to-Earn gaming model to the Play-to-Earn model , a move likely inspired by the widespread distrust generated by the Hamster Kombat launch. To put it in proper context, Hamster Kombat (HMSTR)’s recent launch was quickly followed by a massive sell-off, with the native token dipping by 42% in the space of three days. As a result of this latest development, scores of social media users have begun to call out the developers behind the clicker game for allegedly scamming them or for what appears to be an “unfair distribution” of its native token. The majority of the critics are investors who poured several months into the clicker game with a great expectation of financial return at launch. As of this writing, data from TradingView reveal that the token is bound to slide further from its Sunday’s all-time low of $0.005613. The volume of decline witnessed within a little over 48 hours of the launch clearly points out that it was not the product of FOMO but rather a symptom of the massive decline in investors' confidence in the project. The token distribution is anything but fair to millions of users who participated in the month-long tapping frenzy. If anything, the Hamster distribution has caused disaffection among millions of its players around the world, raising a valid question not only about its future but also concerning the sustainability of Tap-To-Earn clicker games on Telegram. Nonetheless, it also reveals they mostly thrive on crypto cycle hype and have little or no intrinsic value to offer. Are Tap-To-Eo Earn Models Sustainable? An answer to the question of the long-term sustainability of Tap-To-Earn clicker games requires a comparative data analysis of this model. With millions of investors hyped into what appears to be a highly rewarding crypto investment, the growing presence of this model can not be ignored. However, Notcoin, TON's first clicker game with over $700 million market capitalization, remains the only case study for how to launch a Tap-To-Earn game on Telegram leveraging the first mover-advantage principle. Meanwhile, several others that have followed suit have either failed completely or are struggling to achieve success. For instance, TapSwap, a viral clicker game with millions of players on Telegram, has repeatedly postponed its launch dates to the utter disappointment of its investors, casting a shadow of doubt over the credibility of the developers and the future of the game itself. “Unfair Distribution” The Hamster Kombat launch adds to the catalog of challenges that have greeted the emergence of clicker games on Telegram: unfair distribution of tokens. It is bad enough that Telegram-powered clicker games are often criticized for the lack of utility, the unfairness in the distribution mechanism, as happened in the case of Hamster Kombat, is a blow to the reputation of Tap-To-Earn games. Without an iota of doubt, it's almost tempting to deduce unfair distribution in the criticism leveled against Hamster Kombat, with a total supply of 100 billion hamsters, by merely looking at the distribution data and the payouts that millions of investors received for investing several months of amassing millions of hamster into it. The screengrab below by a Nigerian crypto influencer is an example of how to measure the amount of anger and distrust Hamster Kombat's recent launch has generated on social media in the last couple of days. On X, another user @Mohsin_71 commented as follows: “#HamsterKombat Token Distribution: Unfair Distribution  People wasted 2-3 months to mine #Hamster_Kombat tokens. What did they get? ….. Few pennies? Retweet 🔃 Season 2 = Advance Failure due to bad distribution. People are not happy. You can destroy your whole empire.” @hamster_kombat” Predictions The Hamster Kombat's launch has further exposed the Tap-To-Earn model to criticism, and there is a strong likelihood that investors are beginning to grow wary of Telegram-based clicker games promising good returns. The impact of this distrust will also be felt by rival Tap-To-Earn games and may lead to them switching from Tap-To-Earn to Play-To-Earn model in the current cycle, forcing them to activate their survival mode and enabling the latter to take the center stage again. In the coming months, we may likely witness the resurgence of play to earn games on Telegram as the sustainability of the Tap-To-Earn model now hangs in the balance. Rocky Rabbit's Transition From Tap-To-Earn to Play-To-Earn Gaming Model Recently, Telegram-powered clicker game Rocky Rabbit announced its transition from a Tap-To-Earn to a Play-To-Earn gaming model to increase player engagement and enhance their earning potentials. This shift is focused on long term sustainability and a more rewarding user engagement which aligns with industry trends. The strategic shift is coming barely a week after it airdropped its RBTC token to millions of players and its listing on crypto exchanges. Initially, Rocky Rabbit, with over 29 million players, started as a Tap-to-Earn clicker game on Telegram based blockchain, TON, before switching to a gaming model that offers instant rewards and benefits to its players who participate in various in-game activities and tasks. Most importantly, this transition is a departure from the tapping frenzy to a utility-driven model offering financial rewards in real time and keeping users engaged in the long run through multiple gaming experiences that can be explored. Conclusion Notcoin’s successful launch early this year brought significant attention to Telegram’s innovative Tap-To-Earn model, inspiring similar projects like Hamster Kombat and TapSwap to join the trend. Today, Tap-To-Earn clickers games boast millions of players on Telegram and a combined market capitalization of over 1 billion dollars. Despite this figure, they continue to face significant challenges in their efforts to sustain investors' interest. The much-awaited launch of Hamster Kombat, which is now a hot topic in the crypto community, came as a rude shock to millions of players who participated in the game with a huge expectation of financial return, raising a valid question about the long-term sustainability of Telegram-based tap-to-earn platforms. Popular Telegram-based clicker game Rocky Rabbit just announced its transition from its Tap-to-Earn gaming model to the Play-to-Earn model , a move likely inspired by the widespread distrust generated by the Hamster Kombat launch. To put it in proper context, Hamster Kombat (HMSTR)’s recent launch was quickly followed by a massive sell-off, with the native token dipping by 42% in the space of three days. 42% As a result of this latest development, scores of social media users have begun to call out the developers behind the clicker game for allegedly scamming them or for what appears to be an “unfair distribution” of its native token. The majority of the critics are investors who poured several months into the clicker game with a great expectation of financial return at launch. As of this writing, data from TradingView reveal that the token is bound to slide further from its Sunday’s all-time low of $0.005613. The volume of decline witnessed within a little over 48 hours of the launch clearly points out that it was not the product of FOMO but rather a symptom of the massive decline in investors' confidence in the project. The token distribution is anything but fair to millions of users who participated in the month-long tapping frenzy. If anything, the Hamster distribution has caused disaffection among millions of its players around the world, raising a valid question not only about its future but also concerning the sustainability of Tap-To-Earn clicker games on Telegram. Nonetheless, it also reveals they mostly thrive on crypto cycle hype and have little or no intrinsic value to offer. Are Tap-To-Eo Earn Models Sustainable? An answer to the question of the long-term sustainability of Tap-To-Earn clicker games requires a comparative data analysis of this model. With millions of investors hyped into what appears to be a highly rewarding crypto investment, the growing presence of this model can not be ignored. However, Notcoin, TON's first clicker game with over $700 million market capitalization, remains the only case study for how to launch a Tap-To-Earn game on Telegram leveraging the first mover-advantage principle. Meanwhile, several others that have followed suit have either failed completely or are struggling to achieve success. For instance, TapSwap, a viral clicker game with millions of players on Telegram, has repeatedly postponed its launch dates to the utter disappointment of its investors, casting a shadow of doubt over the credibility of the developers and the future of the game itself. “Unfair Distribution” The Hamster Kombat launch adds to the catalog of challenges that have greeted the emergence of clicker games on Telegram: unfair distribution of tokens. It is bad enough that Telegram-powered clicker games are often criticized for the lack of utility, the unfairness in the distribution mechanism, as happened in the case of Hamster Kombat, is a blow to the reputation of Tap-To-Earn games. Without an iota of doubt, it's almost tempting to deduce unfair distribution in the criticism leveled against Hamster Kombat, with a total supply of 100 billion hamsters, by merely looking at the distribution data and the payouts that millions of investors received for investing several months of amassing millions of hamster into it. The screengrab below by a Nigerian crypto influencer is an example of how to measure the amount of anger and distrust Hamster Kombat's recent launch has generated on social media in the last couple of days. On X, another user @Mohsin_71 commented as follows: “#HamsterKombat Token Distribution: Unfair Distribution  People wasted 2-3 months to mine #Hamster_Kombat tokens. What did they get? ….. Few pennies? Retweet 🔃 Season 2 = Advance Failure due to bad distribution. People are not happy. You can destroy your whole empire.” @hamster_kombat” “#HamsterKombat Token Distribution: Unfair Distribution  People wasted 2-3 months to mine #Hamster_Kombat tokens. What did they get? ….. Few pennies? Retweet 🔃 Season 2 = Advance Failure due to bad distribution. People are not happy. You can destroy your whole empire.” @hamster_kombat” Predictions The Hamster Kombat's launch has further exposed the Tap-To-Earn model to criticism, and there is a strong likelihood that investors are beginning to grow wary of Telegram-based clicker games promising good returns. The impact of this distrust will also be felt by rival Tap-To-Earn games and may lead to them switching from Tap-To-Earn to Play-To-Earn model in the current cycle, forcing them to activate their survival mode and enabling the latter to take the center stage again. In the coming months, we may likely witness the resurgence of play to earn games on Telegram as the sustainability of the Tap-To-Earn model now hangs in the balance. Rocky Rabbit's Transition From Tap-To-Earn to Play-To-Earn Gaming Model Recently, Telegram-powered clicker game Rocky Rabbit announced its transition from a Tap-To-Earn to a Play-To-Earn gaming model to increase player engagement and enhance their earning potentials. This shift is focused on long term sustainability and a more rewarding user engagement which aligns with industry trends. The strategic shift is coming barely a week after it airdropped its RBTC token to millions of players and its listing on crypto exchanges. Initially, Rocky Rabbit, with over 29 million players, started as a Tap-to-Earn clicker game on Telegram based blockchain, TON, before switching to a gaming model that offers instant rewards and benefits to its players who participate in various in-game activities and tasks. Most importantly, this transition is a departure from the tapping frenzy to a utility-driven model offering financial rewards in real time and keeping users engaged in the long run through multiple gaming experiences that can be explored. Conclusion Notcoin’s successful launch early this year brought significant attention to Telegram’s innovative Tap-To-Earn model, inspiring similar projects like Hamster Kombat and TapSwap to join the trend. Today, Tap-To-Earn clickers games boast millions of players on Telegram and a combined market capitalization of over 1 billion dollars. Despite this figure, they continue to face significant challenges in their efforts to sustain investors' interest. The much-awaited launch of Hamster Kombat, which is now a hot topic in the crypto community, came as a rude shock to millions of players who participated in the game with a huge expectation of financial return, raising a valid question about the long-term sustainability of Telegram-based tap-to-earn platforms.

Rocky Rabbit's Transition: How Hamster Kombat Is Fueling The Play-To-Earn Switch

The corporate world is often compared to a marathon - steady, structured, and predictable. In contrast, start-ups can feel like a series of sprints, full of direction changes. Transitioning from the structured environment of the corporate world to the dynamic fast-paced start-up ecosystem can be daunting but incredibly rewarding. It requires a shift in mindset, a willingness to step out of your comfort zone, and the courage to embrace uncertainty. Gaby Haffner, currently the Head of Europe at Baret Scholars and former Founder of Ameli Health, has successfully navigated this transition. As a former Strategy Consultant and Investment Banker turned start-up founder. From her early roles at Bank of America Merrill Lynch to her time at Monitor Deloitte and EY, where she focused on tech and consumer companies, Gaby's experiences can offer lessons for aspiring entrepreneurs. Here, Gaby shares five actionable insights from her transition from corporate to entrepreneurship. Lesson 1: Focus on Execution Over Perfection In start-ups, speed and execution often matter more than meticulous planning. "Real-world feedback provides insights no amount of theoretical planning can match," Gaby notes. This lesson became especially clear when she founded Ameli Health, a luxury prescription skincare platform. Gaby launched a proprietary platform that integrated doctor-patient matching with pharmacy supply chains in a remarkably short timeframe. She moved fast, gathered feedback, and pivoted based on real-time market reactions. This experience contrasted sharply with her corporate experience at EY and Monitor Deloitte, where processes were more structured and detailed. "A good idea is only as valuable as the ability to execute it," Gaby emphasizes. This ability of hers has also been crucial at Baret Scholars, where she is part of the founding team who are building a pioneering education company. Lesson 2: Embrace Uncertainty Entrepreneurship demands a strong appetite for risk. "In corporate environments, things are often predictable, but in the start-up world, you need to be comfortable with uncertainty", Gaby explains. This shift means learning to thrive in ambiguity. As a founder, you're responsible for everything, from product development to finances, often pushing you well beyond your comfort zone. During her time at Ameli Health, Gaby had to quickly become proficient in areas outside her expertise, such as digital marketing and product management. This adaptability has been invaluable at Baret Scholars, where she successfully leads the digital marketing efforts. Her advice: “Growth happens in the unknown”. Lesson 3: Adopt a Growth Mindset Unlike the scarcity-driven, zero-sum thinking that often dominates corporate environments, start-ups require a growth mindset - the belief that abilities can be developed through dedication and effort. "A growth mindset allows you to embrace challenges and setbacks as opportunities for learning and growth," Gaby emphasizes. Gaby honed this mindset during her time at Farfetch, where she worked on improving revenue strategies for high-end luxury fashion clients. These experiences translated directly into her role at Baret Scholars, where she continues to apply growth-oriented strategies to drive business development. Lesson 4: Prepare for the Emotional Rollercoaster "Entrepreneurship is an emotional rollercoaster," Gaby admits. "There are extreme highs and crushing lows. You need a high pain threshold and a deep passion for what you're building to push through the tough times". In corporate roles, setbacks are often cushioned by larger organizations, but in start-ups, every challenge can feel personal. Her experience founding Ameli Health taught Gaby the resilience needed to endure the ups and downs of entrepreneurship. This emotional resilience has been crucial to her role at Baret Scholars, where she manages the pressures of scaling a start-up. Lesson 5: Constantly Seek Critique In start-ups, mediocrity is not an option. "Whatever you create must be far superior to what's already out there," Gaby emphasizes. Constantly seeking feedback from trusted sources and iterating based on that critique is key to refining a high-value product or service. At Baret Scholars, Gaby implemented a fast feedback loop early on, speaking directly to customers to refine the program’s structure. This adaptability has allowed the company to evolve its offering and offer a truly innovative product. “Listening to the market and improving based on feedback has been essential to our growth,” she notes. Gaby’s Thoughts on Entrepreneurship Gaby believes that start-ups are society’s true source of innovation and disruption. As a mentor at MassChallenge and for Fitzwilliam College, University of Cambridge’s entrepreneurship competition, she dedicates her time to supporting early-stage start-ups. The corporate world is often compared to a marathon - steady, structured, and predictable. In contrast, start-ups can feel like a series of sprints, full of direction changes. Transitioning from the structured environment of the corporate world to the dynamic fast-paced start-up ecosystem can be daunting but incredibly rewarding. It requires a shift in mindset, a willingness to step out of your comfort zone, and the courage to embrace uncertainty. Gaby Haffner , currently the Head of Europe at Baret Scholars and former Founder of Ameli Health, has successfully navigated this transition. As a former Strategy Consultant and Investment Banker turned start-up founder. From her early roles at Bank of America Merrill Lynch to her time at Monitor Deloitte and EY, where she focused on tech and consumer companies, Gaby's experiences can offer lessons for aspiring entrepreneurs. Gaby Haffner Gaby Haffner Here, Gaby shares five actionable insights from her transition from corporate to entrepreneurship. Lesson 1: Focus on Execution Over Perfection In start-ups, speed and execution often matter more than meticulous planning. "Real-world feedback provides insights no amount of theoretical planning can match," Gaby notes. This lesson became especially clear when she founded Ameli Health, a luxury prescription skincare platform. Gaby launched a proprietary platform that integrated doctor-patient matching with pharmacy supply chains in a remarkably short timeframe. She moved fast, gathered feedback, and pivoted based on real-time market reactions. This experience contrasted sharply with her corporate experience at EY and Monitor Deloitte, where processes were more structured and detailed. "A good idea is only as valuable as the ability to execute it," Gaby emphasizes. This ability of hers has also been crucial at Baret Scholars, where she is part of the founding team who are building a pioneering education company. Lesson 2: Embrace Uncertainty Entrepreneurship demands a strong appetite for risk. "In corporate environments, things are often predictable, but in the start-up world, you need to be comfortable with uncertainty", Gaby explains. This shift means learning to thrive in ambiguity. As a founder, you're responsible for everything, from product development to finances, often pushing you well beyond your comfort zone. During her time at Ameli Health, Gaby had to quickly become proficient in areas outside her expertise, such as digital marketing and product management. This adaptability has been invaluable at Baret Scholars, where she successfully leads the digital marketing efforts. Her advice: “Growth happens in the unknown”. Lesson 3: Adopt a Growth Mindset Unlike the scarcity-driven, zero-sum thinking that often dominates corporate environments, start-ups require a growth mindset - the belief that abilities can be developed through dedication and effort. "A growth mindset allows you to embrace challenges and setbacks as opportunities for learning and growth," Gaby emphasizes. Gaby honed this mindset during her time at Farfetch, where she worked on improving revenue strategies for high-end luxury fashion clients. These experiences translated directly into her role at Baret Scholars, where she continues to apply growth-oriented strategies to drive business development. Lesson 4: Prepare for the Emotional Rollercoaster "Entrepreneurship is an emotional rollercoaster," Gaby admits. "There are extreme highs and crushing lows. You need a high pain threshold and a deep passion for what you're building to push through the tough times". In corporate roles, setbacks are often cushioned by larger organizations, but in start-ups, every challenge can feel personal. Her experience founding Ameli Health taught Gaby the resilience needed to endure the ups and downs of entrepreneurship. This emotional resilience has been crucial to her role at Baret Scholars, where she manages the pressures of scaling a start-up. Lesson 5: Constantly Seek Critique In start-ups, mediocrity is not an option. "Whatever you create must be far superior to what's already out there," Gaby emphasizes. Constantly seeking feedback from trusted sources and iterating based on that critique is key to refining a high-value product or service. At Baret Scholars, Gaby implemented a fast feedback loop early on, speaking directly to customers to refine the program’s structure. This adaptability has allowed the company to evolve its offering and offer a truly innovative product. “Listening to the market and improving based on feedback has been essential to our growth,” she notes. Gaby’s Thoughts on Entrepreneurship Gaby believes that start-ups are society’s true source of innovation and disruption. As a mentor at MassChallenge and for Fitzwilliam College, University of Cambridge’s entrepreneurship competition, she dedicates her time to supporting early-stage start-ups.

Stories, News & Mentions about TRANSIT

Transit’s Stories on HackerNoon

Transit's News & Mentions