BetterFeedback

betterfeedback

I have been writing code professionally for more than five years now. For the first four years, I never cared about the size of my pull requests (PRs). However, in the last year, I transitioned from submitting massive PRs with thousands of lines of changes to breaking them down into smaller, more manageable ones. The benefits of this shift have been immense, and in this blog, I’ll share those advantages. According to GitHub, a pull request is: A pull request is a proposal to merge a set of changes from one branch into another. In a pull request, collaborators can review and discuss the proposed set of changes before they integrate the changes into the main codebase. Essentially, a pull request is a way of collaborating; we should do everything possible to enhance this collaboration. One effective method to improve this collaboration is to keep PRs small. There is no universal definition to differentiate between a small and a large PR. Relying solely on the number of lines changed is insufficient, as auto-generated code and tests can inflate line counts. When I refer to small PRs in this article, I mean dividing a larger PR into multiple smaller, logically coherent PRs. Each smaller PR should be standalone, mergeable, and deployable. I do not advocate artificial splitting like splitting a PR into two, one containing all the code and another with just the tests, as this approach fails to yield any benefits I share below. Efficient Reviews: Ask a programmer to review 10 lines of code, he’ll find 10 issues. Ask him to do 500 lines and he’ll say it looks good. While humorous, this quote carries truth. Everyone is busy with their own work, and when you ask someone to review a PR, you are essentially requesting their time. Reviewing a PR requires the reviewer to switch context from their own work, and if the review takes a considerable amount of time, it can be challenging for them to return back to their work, potentially affecting their motivation and commitment to the review. Smaller PRs, which only take about 20–30 minutes to review, are much easier to tackle compared to those that can take 2–3 hours. Plus, larger PRs often lead to oversights because our attention spans can only handle so much, and jumping between lots of changes in a single PR can be confusing. From my experience, smaller PRs tend to get better feedback and lead to more meaningful design conversations. Faster Reviews: At this point, I’m thinking of adding my PR to my will in case it’s still in review after I’m gone. Longer PRs require a significant time commitment from reviewers, making them less likely to get attention — especially if they’re not tied to high-impact features. Small PRs on the other hand are reviewed quickly, as they demand less of the reviewer’s time and are less intrusive. This speed of reviews can be crucial for meeting project deadlines; I’ve seen projects getting delayed because senior reviewers couldn’t allocate time for massive PRs (though this can happen with small PRs, the risk is inherently higher with large ones). Lesser Rework: Reworking a big PR after design changes is like rearranging deck chairs on a ship you just finished building… and then sinking it. We have all experienced situations where someone realizes during PR review that a different design would have been more maintainable and future-proof, and we need to spend additional time reworking the PR based on the new design (not to say that they were completely on board with the design that was initially implemented :p). This is very natural because sometimes things become clearer once you see them written in code, and you start noticing aspects you might have missed during the design phase. With large PRs, this can be a significant issue because you have to rework a lot of elements, but with smaller PRs, it is easier to make changes. More importantly, there is a lower chance of rework because reviewers are more likely to identify issues early on and address them in the initial PRs, allowing subsequent PRs to be based on the new designs. Better Testing: Smaller PRs also benefit you as the author of the PR. They help in testing smaller changes incrementally rather than testing the whole project in one go. Testing smaller changes results in more exhaustive testing of each component of the system, thus leading to fewer production bugs. This applies to both automated tests and manual testing performed by you or dedicated QA engineers. Moreover, smaller PRs reduce the likelihood of missed test cases, as you can focus on a limited scope rather than the entire system. Writing tests? That sounds like Future Me’s problem. I have seen developers (including myself in the past) hesitate to write automation tests due to the perceived time investment without immediate, “visible” value to the feature/product. Smaller PRs reduce this friction by limiting the number of tests required and the time spent writing them. Easier Debugging: No matter how thorough your testing is, production bugs will happen! Being able to debug a bug in production is crucial since production bugs directly impact users, the business, or both. With large PRs, the surface area of change is also large, making it time-consuming and difficult to find the root cause of issues. On the other hand, smaller PRs contain less code and thus make debugging much faster. Debugging small changes is like finding a typo; debugging big changes is like proofreading an encyclopedia. Phased Feature Deployment: Last but not least, smaller PRs are also helpful to your product manager and users. By using small PRs, you can continuously push parts of the system to production, which helps in obtaining early feedback from users and allows for early course corrections if needed. Skipping early feedback is like cooking a five-course meal without tasting anything — you’re just hoping it’s not a disaster. The benefits of small PRs are numerous, and the points outlined above are among the most impactful I’ve experienced personally. If you have encountered other advantages of small PRs or challenges with larger ones that I haven’t covered, do comment with your insights. I hope this article motivates you to embrace smaller PRs. If you’re already on board, I hope it reinforces the value of this practice. Thanks for reading, until next time, keep coding and stay curious! I have been writing code professionally for more than five years now. For the first four years, I never cared about the size of my pull requests (PRs). However, in the last year, I transitioned from submitting massive PRs with thousands of lines of changes to breaking them down into smaller, more manageable ones. The benefits of this shift have been immense, and in this blog, I’ll share those advantages. According to GitHub , a pull request is: GitHub A pull request is a proposal to merge a set of changes from one branch into another. In a pull request, collaborators can review and discuss the proposed set of changes before they integrate the changes into the main codebase. A pull request is a proposal to merge a set of changes from one branch into another. In a pull request, collaborators can review and discuss the proposed set of changes before they integrate the changes into the main codebase. A pull request is a proposal to merge a set of changes from one branch into another. In a pull request, collaborators can review and discuss the proposed set of changes before they integrate the changes into the main codebase. Essentially, a pull request is a way of collaborating; we should do everything possible to enhance this collaboration. One effective method to improve this collaboration is to keep PRs small. There is no universal definition to differentiate between a small and a large PR. Relying solely on the number of lines changed is insufficient, as auto-generated code and tests can inflate line counts. When I refer to small PRs in this article, I mean dividing a larger PR into multiple smaller, logically coherent PRs. Each smaller PR should be standalone, mergeable, and deployable. I do not advocate artificial splitting like splitting a PR into two, one containing all the code and another with just the tests, as this approach fails to yield any benefits I share below. Efficient Reviews: Efficient Reviews: Ask a programmer to review 10 lines of code, he’ll find 10 issues. Ask him to do 500 lines and he’ll say it looks good. Ask a programmer to review 10 lines of code, he’ll find 10 issues. Ask him to do 500 lines and he’ll say it looks good. Ask a programmer to review 10 lines of code, he’ll find 10 issues. Ask him to do 500 lines and he’ll say it looks good. While humorous, this quote carries truth. Everyone is busy with their own work, and when you ask someone to review a PR, you are essentially requesting their time. Reviewing a PR requires the reviewer to switch context from their own work, and if the review takes a considerable amount of time, it can be challenging for them to return back to their work, potentially affecting their motivation and commitment to the review. Smaller PRs, which only take about 20–30 minutes to review, are much easier to tackle compared to those that can take 2–3 hours. Plus, larger PRs often lead to oversights because our attention spans can only handle so much, and jumping between lots of changes in a single PR can be confusing. From my experience, smaller PRs tend to get better feedback and lead to more meaningful design conversations. Faster Reviews: Faster Reviews: At this point, I’m thinking of adding my PR to my will in case it’s still in review after I’m gone. At this point, I’m thinking of adding my PR to my will in case it’s still in review after I’m gone. At this point, I’m thinking of adding my PR to my will in case it’s still in review after I’m gone. Longer PRs require a significant time commitment from reviewers, making them less likely to get attention — especially if they’re not tied to high-impact features. Small PRs on the other hand are reviewed quickly, as they demand less of the reviewer’s time and are less intrusive. This speed of reviews can be crucial for meeting project deadlines; I’ve seen projects getting delayed because senior reviewers couldn’t allocate time for massive PRs (though this can happen with small PRs, the risk is inherently higher with large ones). Lesser Rework: Lesser Rework: Reworking a big PR after design changes is like rearranging deck chairs on a ship you just finished building… and then sinking it. Reworking a big PR after design changes is like rearranging deck chairs on a ship you just finished building… and then sinking it. Reworking a big PR after design changes is like rearranging deck chairs on a ship you just finished building… and then sinking it. We have all experienced situations where someone realizes during PR review that a different design would have been more maintainable and future-proof, and we need to spend additional time reworking the PR based on the new design (not to say that they were completely on board with the design that was initially implemented :p). This is very natural because sometimes things become clearer once you see them written in code, and you start noticing aspects you might have missed during the design phase. With large PRs, this can be a significant issue because you have to rework a lot of elements, but with smaller PRs, it is easier to make changes. More importantly, there is a lower chance of rework because reviewers are more likely to identify issues early on and address them in the initial PRs, allowing subsequent PRs to be based on the new designs. Better Testing: Better Testing: Smaller PRs also benefit you as the author of the PR. They help in testing smaller changes incrementally rather than testing the whole project in one go. Testing smaller changes results in more exhaustive testing of each component of the system, thus leading to fewer production bugs. This applies to both automated tests and manual testing performed by you or dedicated QA engineers. Moreover, smaller PRs reduce the likelihood of missed test cases, as you can focus on a limited scope rather than the entire system. Writing tests? That sounds like Future Me’s problem. Writing tests? That sounds like Future Me’s problem. Writing tests? That sounds like Future Me’s problem. I have seen developers (including myself in the past) hesitate to write automation tests due to the perceived time investment without immediate, “visible” value to the feature/product. Smaller PRs reduce this friction by limiting the number of tests required and the time spent writing them. Easier Debugging: Easier Debugging: No matter how thorough your testing is, production bugs will happen! Being able to debug a bug in production is crucial since production bugs directly impact users, the business, or both. With large PRs, the surface area of change is also large, making it time-consuming and difficult to find the root cause of issues. On the other hand, smaller PRs contain less code and thus make debugging much faster. Debugging small changes is like finding a typo; debugging big changes is like proofreading an encyclopedia. Debugging small changes is like finding a typo; debugging big changes is like proofreading an encyclopedia. Debugging small changes is like finding a typo; debugging big changes is like proofreading an encyclopedia. Phased Feature Deployment: Phased Feature Deployment: Last but not least, smaller PRs are also helpful to your product manager and users. By using small PRs, you can continuously push parts of the system to production, which helps in obtaining early feedback from users and allows for early course corrections if needed. Skipping early feedback is like cooking a five-course meal without tasting anything — you’re just hoping it’s not a disaster. Skipping early feedback is like cooking a five-course meal without tasting anything — you’re just hoping it’s not a disaster. Skipping early feedback is like cooking a five-course meal without tasting anything — you’re just hoping it’s not a disaster. The benefits of small PRs are numerous, and the points outlined above are among the most impactful I’ve experienced personally. If you have encountered other advantages of small PRs or challenges with larger ones that I haven’t covered, do comment with your insights. I hope this article motivates you to embrace smaller PRs. If you’re already on board, I hope it reinforces the value of this practice. Thanks for reading, until next time, keep coding and stay curious!

The Big Power of Small Pull Requests: How They Improve Reviews and Speed Up Development

El gran poder de las pequeñas solicitudes de incorporación de cambios: cómo mejoran las revisiones y aceleran el desarrollo

小さなプルリクエストの大きな力: レビューを改善し、開発をスピードアップする方法

Nguya monene ya masengi ya kobenda ya mike: Ndenge nini kobongisaka botali mpe kosala ete bokoli ya mbangu

ພະລັງອັນໃຫຍ່ຫຼວງຂອງການຮ້ອງຂໍດຶງຂະຫນາດນ້ອຍ: ເຮັດແນວໃດພວກເຂົາປັບປຸງການທົບທວນຄືນແລະເລັ່ງການພັດທະນາ

Nelielu pieprasījumu lielais spēks: kā tie uzlabo pārskatus un paātrina attīstību

Ny Hery lehibe amin'ny fangatahan'ny fisintonana kely: ny fomba hanatsarana ny hevitra sy ny fanafainganana ny fampandrosoana

सानो पुल अनुरोधहरूको ठूलो शक्ति: कसरी तिनीहरूले समीक्षाहरू सुधार गर्छन् र विकासलाई गति दिन्छ

Wielka moc małych żądań ściągnięcia: jak usprawniają przeglądy i przyspieszają rozwój

Fuqia e madhe e kërkesave për tërheqje të vogla: Si përmirësojnë rishikimet dhe përshpejtojnë zhvillimin

The Big Power of Small Pull Requests: Hur de förbättrar recensioner och påskyndar utvecklingen

พลังอันยิ่งใหญ่ของคำขอ Pull Request ขนาดเล็ก: วิธีปรับปรุงบทวิจารณ์และเร่งการพัฒนา

小型 Pull 请求的巨大威力：它们如何改善评审并加快开发速度

HTML radio buttons are a staple of web forms, but their default appearance leaves much to be desired. In this blog post, we'll walk through one of my favorite methods to customize the look of radio buttons using CSS, creating a more user-friendly and visually appealing experience. https://youtu.be/PlldXyuTnUw?embedable=true Let's Begin by Hiding the Radio Buttons! We need to start by acknowledging the limitations of cross-browser styling for radio buttons. While it's frustrating that we can't style them directly, we can use workarounds. In this example, the first step is to hide the actual radio button input. I know this sounds odd, but we know that we can't style them, so we just need to take them out of the equation. However, this should be done in an accessible manner, ensuring that it remains functional for all users. This can be achieved by using the following set of styles that visually hide the content while retaining its usability: input[type="radio"] {
  border: 0 !important;
  clip: rect(1px, 1px, 1px, 1px);
  height: 1px !important;
  overflow: hidden;
  padding: 0 !important;
  position: absolute !important;
  width: 1px !important;
} Creating the Custom Radio Buttons To create the custom appearance of the radio button, we'll leverage the pseudo-element on our label along with some simple CSS to create the look we're looking for. ::before For our example, the HTML looks like this: <form>
    <h1>Can We Style HTML Radio Buttons?</h1>
    <ul>
        <li>
            <input type="radio" value="yes" name="option" id="yes" />
            <label for="yes">Yes</label>
        </li>
        <li>
            <input type="radio" value="no" name="option" id="no" />
            <label for="no">No</label>
        </li>
        <li>
            <input type="radio" value="maybe" name="option" id="maybe" />
            <label for="maybe">Maybe</label>
        </li>
      </ul>
</form> To start, we'll add the following styles to our label element: label {
  display: inline-flex;
  align-items: center;
} This will ensure that once we add our radio button styles, it will be properly vertically aligned with the label text. Now, we'll add our mock radio buttons using the pseudo-element: ::before label::before {
  content: '';
  display: block;
  height: 1.25em;
  width: 1.25em;
  border: solid 1px #ccc;
  border-radius: 50%;
  margin-right: 0.5em;
} At this point, we have something that is starting to resemble a radio button list, but if we click on the radios, we will see that nothing is happening. Although the pseudo-element visually resembles a radio button, it lacks interactivity because we have not yet handled the checked state. Handling Interaction and States We can handle the checked state with the pseudo-class and adjacent sibling selector on our label: :checked input[type="radio"]:checked + label {
  color: black;
} For the inner dot, we can leverage a radial gradient on our pseudo-element: input[type="radio"]:checked + label::before {
  background: radial-gradient(0.75em circle at center, currentColor 50%, transparent 55%);
  box-shadow: 0 0 1em 0 rgba(10, 150, 255, 0.75);
  border-color: currentColor;
} There, now when we click on these, they function much like native radio buttons. And we can enhance the interactions by adding some transition effects: label::before {
  ...
  transition: border ease-in 150ms, box-shadow ease-in 150ms;
} Let's Not Forget About Focus To improve accessibility, we will also need to address the focused state of the mock radio buttons. This time we will need to utilize the pseudo-class and the adjacent sibling selector with the label: :focus input[type="radio"]:checked + label,
input[type="radio"]:focus + label {
  color: black;
}

input[type="radio"]:focus + label::before {
  box-shadow: 0 0 1em 0 rgba(10, 150, 255, 0.75);
  border-color: currentColor;
} Conclusion By following this method, we can create stylish and accessible custom radio buttons that greatly enhance the user experience. These customized radio buttons not only look better than the standard ones but can also provide better feedback and interaction when implemented properly. This was a pretty simple example that may not even really look much different than the native browser styles but the key is, with this setup, we can pretty much do whatever we want. So, feel free to experiment with the styles and adapt them to your project's design. Want to See It in Action? Check out the demo code and examples of this technique in the code pen example below. If you have any questions or thoughts, don't hesitate to leave a comment. Remember that with a little creativity and some CSS, you can transform the appearance of HTML radio buttons to match your design while maintaining accessibility and usability! https://codepen.io/brianmtreese/pen/bGOGeBJ?embedable=true

How to Style HTML Radio Buttons: A Step-by-Step Guide

এইচটিএমএল রেডিও বোতামগুলি কীভাবে স্টাইল করবেন: একটি ধাপে ধাপে নির্দেশিকা

So gestalten Sie HTML-Radiobuttons: Eine Schritt-für-Schritt-Anleitung

Cómo diseñar botones de opción HTML: una guía paso a paso

Comment styliser les boutons radio HTML : un guide étape par étape

HTML रेडियो बटन को कैसे स्टाइल करें: एक चरण-दर-चरण मार्गदर्शिका

HTML ラジオ ボタンのスタイルを設定する方法: ステップバイステップ ガイド

HTML 라디오 버튼 스타일 지정 방법: 단계별 가이드

Como estilizar botões de opção HTML: um guia passo a passo

Как оформить HTML-переключатели: пошаговое руководство

HTML Radyo Düğmelerine Nasıl Stil Verilir: Adım Adım Kılavuz

Cách tạo kiểu cho các nút radio HTML: Hướng dẫn từng bước

如何设置 HTML 单选按钮的样式：分步指南

Startups of The Year 2023 Winners: Europe

Have you ever felt utterly stumped trying to fix a bug in your mobile app? As an app developer, debugging is an inevitable part of the job. But rather than seeing it as a frustrating roadblock, adopt a debugging mindset. A debugging mindset is about building your resilience and problem-solving skills to overcome any issue. With the right mindset, you'll start to see bugs as puzzles to solve rather than obstacles stopping you in your tracks. You'll become a troubleshooting ninja, able to isolate issues and test solutions with a logical and methodical approach. Having a debugging mindset will make you a better developer, able to keep a cool head under pressure. Read on to level up your debugging skills and build unstoppable resilience in the face of digital disaster. This article will show you how to cultivate a debugging mindset to conquer any challenge in your mobile app dev journey. Developing a Growth Mindset To become a great mobile app developer, you need to develop a growth mindset. That means believing you can improve and get better at your craft through hard work and persistence. that you’ll face obstacles and challenges. Building apps is complicated, and things will go wrong. Expect failures and see them as learning opportunities rather than defeats. Accept View . When users report bugs or give low ratings, don’t get defensive. Listen with an open mind and look for ways to improve. Every piece of feedback makes you and your apps better. feedback as a gift and expanding your skills. Mobile technologies change fast, so you need to keep up with the latest languages, frameworks, and tools. Take online courses, read books, and practice every day. Growth comes from continuous progress, not perfection. Keep learning along the way. Share what you’ve learned by writing blog posts, recording video tutorials, speaking at conferences, or mentoring new developers. Helping others reinforces your own understanding and benefits the community. Help others Developing a growth mindset is key to resilience and success as a mobile app developer. With hard work and the right mindset, you can achieve great things. Every small win and every failure along the way will make you stronger and smarter. So, get out there and build some apps! The more you do, the more you’ll grow. Facing Challenges With Courage and Resilience Facing challenges is inevitable in app development, but how you respond makes all the difference. Do you see bugs and errors as failures, or as opportunities to build mental toughness? Adopting a debugging mindset, where you approach problems with courage and resilience, will serve you well. When issues arise, stay calm and focused. Panicking will only make the situation worse. Take a few deep breaths to avoid frustration and look at the issue objectively. Try to see problems as puzzles to solve rather than obstacles blocking your progress. With an open and curious mindset, you'll find solutions. Break down complex problems into smaller steps. Don't feel overwhelmed by the scale of the challenge. Deal with one part at a time, solving what you can and making progress. Celebrate small wins along the way to stay motivated for the next milestone. Learn from your mistakes and failures. They are inevitable in app development, so view them as learning opportunities. Ask yourself what went wrong and how you can avoid or handle similar issues in the future. Share your experiences with colleagues so they can also benefit from them. With practice, facing and overcoming challenges will become second nature. You'll build true resilience and confidence in your ability to debug any issue. So the next time a bug rears its head, take a breath and dive in. Your debugging mindset will guide you to the solution. Debugging Is Problem-Solving - Adopt a Systematic Approach Debugging an app is like solving a puzzle—you have to be methodical. Don’t just dive in and start changing code willy-nilly. That will likely create more issues than it fixes! Instead, adopt a systematic approach to debugging. The first step is confirming how to reliably reproduce the problem. Make note of the exact steps that lead to the error or unintended behavior. Reproduce the issue. . Review your code and logs to identify where the issue is occurring. Use breakpoints or print statements to narrow down the problematic area. Look for anything that seems off or unexpected. Narrow down the location Come up with a theory as to what might be causing the issue. Maybe a variable has an incorrect value, or a conditional logic statement is flawed. Develop a hypothesis, then test it. Form a hypothesis. . Make small, incremental changes to your code to test your theory. After each change, re-run your app to see if the issue is resolved. If not, revise your hypothesis, and try again. Test your hypothesis . Once you’ve fixed the issue, look for ways to simplify and strengthen your code. Remove any unnecessary complexity that could lead to future bugs. Solve and simplify Run through the scenario that was causing the issue one more time to ensure it’s truly resolved before moving on. It’s easy to miss something, so double-check your work! Double check. With practice, debugging will become second nature. But always remember—slow down, be methodical, and think like a problem solver. That’s the key to mastering the debugging mindset. Learn From Your Mistakes - Don't Repeat Them Twice We all make mistakes - it's part of being human. The key is to learn from them so you can avoid repeating the same errors. When debugging your mobile app, pay close attention to the issues you encounter and the solutions you devise. . Keep a running list of bugs, errors, crashes, and other issues you come across, along with the solutions and workarounds you develop. Refer to this list often as you build and test your app to avoid duplicating mistakes. Document the problems and fixes . Examine your list of issues to identify any trends in the types of problems you're facing or sections of code that seem particularly prone to bugs. Once you spot the patterns, you can take steps to address them proactively. Look for patterns . Have friends, family members, or colleagues test your app on their own devices. They may encounter problems you haven't seen yet on your own phone or emulator. Pay attention to any feedback they provide about their experience using your app. Ask others to test Check the logs generated by your IDE, emulator, and any beta testing services you use. Look for crash reports, warnings, exceptions, and other red flags. Even if your app seems to be working fine, these logs can point out issues under the surface that you need to fix. Review error logs. If you find you're continually fixing bugs in the same sections of code, it may be time for a rewrite. Refactoring lets you restructure your code to be cleaner, simpler, and less prone to errors. Take what you've learned from debugging, and apply it to strengthening your code. Refactor problematic code. By adopting a debugging mindset, you'll build up your resilience and problem-solving skills. Over time, you'll get better at anticipating issues, spotting them faster, and resolving them more efficiently. Your users will appreciate an app that just works, without bugs or frustrations! Continuous Learning - Stay Up to Date With New Technologies and Best Practices To stay at the top of your game as a mobile app developer, you need to commit to continuous learning. New languages, frameworks, and best practices are introduced all the time, so make learning a habit. with new technologies by following industry leaders and resources. Check sites like , , and regularly for new courses. Stay up to date Codecademy Udacity Coursera a new programming language or framework each year. Even if you don’t use it professionally, it will expand your mind and make you a better problem-solver. Learn books on mobile development, design, and project management. Some highly-rated options include by Eric Ries, by Alan Cooper, and by Gayle Laakmann McDowell. Read “The Lean Startup” “About Face” “Cracking the Coding Interview” with changes in the iOS and Android platforms. Both Apple and Google introduce new features and guidelines with each software update, so keep tabs on the latest releases. Stay up to date Consider getting additional certifications to strengthen your skills. For example, becoming an or Apple Certified iOS Developer Google Certified Android Developer. Continuous learning is key to overcoming obstacles, solving problems efficiently, and building more innovative apps. While the mobile landscape is constantly changing, a dedication to lifelong learning will ensure you have the knowledge and skills to adapt and thrive. Keep your debugging mindset sharp by always seeking to expand your understanding and expertise. The time you invest in learning today will pay off in the long run through a successful and fulfilling career. Conclusion So, there you have it. Developing a debugging mindset is absolutely essential for success as a mobile app developer. With the constant changes in technology, frameworks, and languages, problems will inevitably arise. But by embracing challenges, learning to persevere, and strengthening your problem-solving skills, you'll build the resilience you need to overcome any obstacle. Stay curious, keep practicing, and remember that every bug you fix makes you a better developer. Note: I am not a mobile app developer, I am a web developer, but I think the process of learning new things and stuff related to coding and tech is on the same road. Thanks for Reading. Must Read on Debugging and App Development on Hackernoon How to debug any Problem Charging your debugging skills Debugging UI issues in mobile Apps

The Debugging Mindset: Building Resilience and Problem-Solving Skills in Development

Product visualization on classifieds plays a crucial role in a consumers’ decision-making process. According to Etsy, say the quality of photos are “extremely important” or “very important” to their purchase decision. Embedding interactive 3D product images into a marketplace is an effective way to improve product perception and increase the time a customer spends in a shopping environment, leading to higher conversion rates. Yet, until recently, immersive content was unavailable to most classifieds as it’s difficult to produce. 90% of shoppers Now, app developers can use Mertsy SDK, the solution for classifieds that allows them not only to embed immersive content displaying into a mobile app, but also to create 3D content using a smartphone camera. For the first time, an end-to-end 3D/360 product imaging solution is available as an SDK. What Is Mertsy SDK and How Does It Work? There are several scenarios how a classified can integrate into their mobile app. The most popular one is to modify the ad creation mode. A classified adds a “Create 3D photo” button next to buttons for uploading product photos. Mertsy SDK When the user taps this button, the 3D shooting mode will start. The user will be able to shoot an item in 3D and attach the resulting 3D image to their ad. It’s pretty easy to create a 3D image — the user simply circles an item as if they are shooting a video. The app, meanwhile, uses a range of computer vision and AI technologies to create a 3D image in Cappasity’s proprietary format which is called “3D View”. Mertsy SDK helps classifieds push the boundaries of the online shopping experience. It will be continuously enhanced with new features, since its developers plan to provide not only 3D product imaging, but also other helpful solutions for customer experience improvement and conversion rate growth. The solution allows sellers to shoot anything in the 3D View format, from a ring to a car or even a house. There are multiple 3D capturing modes that can be integrated into a classified’s mobile app, including shooting of any size, digitizing in 3D, and creating of real estate. objects vehicles panoramas Unlike flat images, the 3D View format offers a variety of interactions for consumers: they can rotate items, zoom in, estimate the product’s quality and materials, and check every tiny detail. With high-quality and interactive 3D content, merchants can quickly and easily draw attention to their offerings on marketplaces and classifieds and customers will be able to appreciate the true quality of products. Shooting a car in the 3D View format: How Immersive Content Impacts Sales on Classifieds After embedding immersive content, classifieds observe in conversion action: ads with 3D Views receive better feedback (calls, messages). The ability to estimate the desired item from all angles is especially important for used car buyers. at least a 12% increase found that a whopping 87% of customers find 360-degree photos indispensable when shopping for vehicles online. What’s more, are more likely to consider a vehicle with a 360-degree spin image compared to a vehicle without one. While 3D visualization of a car can’t replace a history report, it creates confidence about the condition of the vehicle, builds trust with the seller and is necessary when purchasing partially or fully online. Autotrader 78% of shoppers For example, CarSwitch, a used car marketplace in UAE and KSA, has integrated with Cappasity’s solution for classifieds to allow their consumers to examine vehicles as they would offline from the comfort of their homes. To digitize a car in 3D, CarSwitch specialists use 3DShot app, a standalone application based on the Mertsy SDK. If visual content for ads is created by a classified’s employees, it’s more convenient to use the 3DShot app and reduce the time for the integration into a classified’s app. After providing immersive content shooting functionality, CarSwitch noticed that cars with 3D Views garner a much higher engagement and interest from buyers. For more info about the solution, follow Cappasity on , , or . Twitter Instagram Facebook

How Online Classifieds Can Innovate With Immersive Technologies

Cómo los anuncios clasificados en línea pueden innovar con tecnologías inmersivas

Comment les petites annonces en ligne peuvent innover avec les technologies immersives

कैसे ऑनलाइन क्लासीफाइड इमर्सिव टेक्नोलॉजीज के साथ नया कर सकते हैं

没入型テクノロジーを使用してオンライン広告がどのように革新できるか

Como os classificados online podem inovar com tecnologias imersivas

Rao vặt trực tuyến có thể đổi mới như thế nào với các công nghệ nhập vai

在线分类广告如何利用沉浸式技术进行创新

Educational technology (edtech) has transformed the field of education. The internet provides unparalleled access to knowledge and useful digital tools, and both college students and professors use it to improve their classroom experience. Why Is Edtech Important? Educational technology allows students to learn in diverse ways. By 2026, experts predict the global digital learning market to in value. Edtech encompasses the use of computer hardware and software that facilitate teaching. Here are some of its benefits: reach nearly $400 billion Students can learn by taking digital notes, using audio recording software, drawing on a tablet or watching videos on a topic. Having a blend of teaching methods helps ensure everyone absorbs the material. Promoting different learning methods: Edtech can prepare students to get a job when they graduate, and as the most important aspect of their success. Improving career readiness: 80% of students see this Digital tools allow students to give their professors feedback during or immediately after a lesson. Providing better feedback: Students can access textbooks and coursework online, saving paper and making it easier for professors to stay organized. Lowering costs and material use: Edtech Tools to Use in College These digital resources make it easier to study, take notes and learn new material. Google Drive Most people are familiar with Google Drive. It’s a valuable edtech tool for securely storing up to two terabytes of documents, photos and videos in one convenient location in the cloud. Google Drive’s AI features allow students to look up files using natural language or by describing the content of photos. Students can change the privacy settings on individual documents to enable file sharing, allowing for collaborative editing on group projects. Drops Language learning can feel like a chore, but the Drops app turns it into a game. Unlike many other apps that focus on translations or grammar skills, Drops only teaches vocabulary, and it uses drawings to convey each subject. Students can choose from numerous topics to learn about what interests them the most. This feature helps the app integrate seamlessly into lessons about biology, math, beginner phrases and more. Drops also features spelling and pronunciation lessons. Coursera Many high-level universities and companies offer their classes online through Coursera. Anyone can take classes on the site and learn topics like digital marketing, contact tracing, fashion or biology. Coursera even offers complete master’s degree programs in innovation and entrepreneurship, accounting, computer science and business administration. It also has courses that lead to professional certifications. Because most of its courses are on-demand, students can complete them at whatever pace fits their schedule. Microsoft Lens Copying notes from a textbook — even when typing — can be a tedious process. Microsoft Lens allows users to take a photo of handwritten or typed text and convert it into a digital document, saving students’ time and hand muscles. Microsoft Lens currently only supports English text, but it can translate converted documents into over 30 languages. It can also convert files to PDFs and other formats, allow annotations and let users change the layout of their documents. Khan Academy Covering , Khan Academy offers courses and practice exams from K-12 to early college curricula. Students can go over the material at their own pace. over 5,000 diverse topics Khan Academy works great even as a standalone learning platform, but it really shines when it comes to supplementing a college student’s classes. Users can fill in the gaps in their knowledge or start learning about a subject before class starts. Thanks to donations, the site is free to use and has no ads. TED Talks A staple of college courses, TED Talks — which students can access on YouTube, podcast platforms or the TED website — cover every topic imaginable. Experts deliver bite-sized speeches on engineering, social skills, medicine, psychology and more. The best part is that the presentations are free for anyone to enjoy. They make a great adjunct to college lectures and reading textbooks. Microsoft OneNote Taking notes is a central part of attending college. OneNote lets students build checklists, record audio, create drawings and sort their notes into sections and pages. It has an annotation feature compatible with a drawing stylus or finger. Plus, students can share their notes with other people, which is useful when somebody misses class or needs a different perspective on a lecture. OneNote also lets students add files like PDFs and PowerPoint presentations directly into their notes. Blueprint Test Preparation, LLC For students preparing for the MCAT, LSAT or other medical and law school exams, Blueprint is a great resource. It features over 100 online classes, tutoring and test prep content to help students excel in their chosen field. Blueprint screens its professors to ensure they’re experts on the subject matter. The company also updates its material constantly to keep up with the latest changes. Edtech Is the Future of Learning Classrooms aren’t switching back to chalkboards any time soon. Digital tools have given students and teachers newfound abilities, allowing for easier learning while using fewer resources. Educational technology will continue to play a pivotal role in the classroom setting for students of all ages.

The Best EdTech for College Students

Customer education is a win-win for customers and businesses. The customer gets more pleasure from the product (because he or she understands it better), and the business gets more profit due to better feedback, outreach, and purchases. Many companies use customer education as a tool. growth marketing A prime example of how customer education helps businesses and customers is Slack. Workplace, launched in 2013, has shown tremendous growth over the years. At the , Kristen Swanson (VP of Customer Insights at Slack) discussed how customer education at Slack works. Here are some interesting quotes from her story: Bay Area Customer Success meetup Education was the core of Slack as a product. If you're just getting started with customer education, find one ticklish problem of your customers and try to remove it. Feel the rush of energy, create the solution and see how it takes root. I see customer education as the jet fuel for CSM. We do what we can to help build better and faster customer relationships. What about sales: as customers move from a free product to a paid product, the more mature they become in their use, the more likely they are to say, "Yeah, let's invest [in the paid version]. That's why it's natural to support educational programs for sales and marketing departments. Of course, customer education isn't just crucial for big SaaS companies like Slack, Checkr, Box, and Optimizely. Here we can even discuss whether they would be big customer education... WITHOUT But that's a topic for another discussion. The fact is that customer education is important and necessary for companies of any profile and size. What companies need customer education? Customer education is content designed to attract, engage and retain new and existing customers. It is delivered programmatically through in-person and on-demand channels. : Businesses should invest in customer education if they have Complex product that users need to learn to understand the value Product that requires users to change existing behaviors, processes, or workflows Diverse user base in terms of needs and roles Products that are regularly updated with new features and functionality Assortment of pre-sales and cross-sales products Products that require extensive support For all these cases, customer education is crucial. How to create a customer education strategy for your company? Working on customer education involves several steps: Auditing the current state of customer education Searching for problems Selection of tools Allocation of resources Developing and testing solutions Let's discuss each in more detail. An audit of the current state of customer education One way or another, you're already talking about your product and how to use it somehow, even if that process isn't formally called customer education. Before you create something new, it's important to delve into what's already happening. Focus on these questions: So, how do you audit the current state of customer education in your company? What educational resources do users have right now? Where are users finding answers to their questions right now? What tools do you use for customer education? Do you provide on-demand guides? How is the learning process structured at each stage of the customer journey? Regarding the last question, write everything, step by step, from the first email you send after signing up (step 1) and beyond. Then look even further back to step 0: how is the training built for users who haven't yet become customers? How do you inform them about the product? How do you explain that this is the right product for them? At this point, it's clear that customer education involves a lot of company resources. Which teams are involved in customer education? These are tech support, the sales department, and the marketing department. Talk to these teams and find out what they do for customer education: What tools are used to educate customers? Is there a training management system and/or customer support center? What information do users come in for, and how does it happen? The most important thing at this stage is to put all the information on two shelves: What we already have and how it works What we don't have and whether we need it Calculate each tool you have and determine its impact on customer success. At this stage, you'll probably have a pile of information: records of support calls, lists of questions from online chats, statistics on the most viewed articles and guides in the blog and knowledge base, and personal opinions after interviews with marketers and sales managers. Identification of problems in customer education As you gather information, you will notice some patterns, repetitive phrases from different specialists, and typical questions in documentation and conversation records. Usually, at this stage, it becomes apparent that there are problems in the customer journey that need to be solved. For this, it's important to capture the results of your research. First, simply collect in one file all the problems you can identify. Next, you will need to analyze, prioritize, perform risk management, and plan the implementation. But for now, we're at the identification stage, so... Examples of typical problems in customer education: : high churn rate 3-7 days after signup (it can mean users are not adapting due to onboarding issues) For SaaS : low percentage of cross-sales and pre-sales (it can mean users are not aware of other products offered (for smartphone - adapter, protective case, speaker) or services (reflashing, software installation)). For eCommerce : a high level of support requests after using a product or individual feature. For any product The goal at this point is to find problems in your specific product (or part of it). When you have a list of problems, it's time to develop an action plan to solve them. To do this, you can use a special matrix: it divides users into segments based on the audience volume (for how many users it is relevant) and risks (how critical the problem is). The result is 4 segments: Large audience and high risk Large audience and low risk Small audience and high risk Small audience and low risk Based on this segmentation, you can understand what type of customer education is needed and prioritize the work on it. . High volume, high risk - it is when you have a lot of end users in a regulated environment. Options for customer onboarding with customer education: Case 1 Training with a certified program, for example, as in Google products - Google Ads, Google Analytics, etc Constantly available knowledge base for refresher training as people use your product Training led by a virtual instructor to explain more complex topics in a more interactive format Customer onboarding is one of the most challenging aspects of the path to purchase. . High volume, low risk - it is when you have a high volume of end users, and the end goal is broad product adoption. Options for customer onboarding with customer education: Case 2 Series of training led by a virtual instructor, which is especially useful when the geography is wide Step-by-step guide inside the product (with pop-ups or other types of prompts) without separate customer onboarding content (as a knowledge base) Short videos with micro-tips and tips for individual tasks and situations, easily consumable and digestible You can develop effective training by carefully analyzing your user base and determining their position in the matrix. . Low volume, high risk - it is when you have professional users whose mistakes are very risky for the brand. Options for customer onboarding with customer education: Case 3 Online calls or mini-conferences to model situations and solve specific problems Webinars with experts with narrow custom training (for example, how to use solution X specifically for online stores with an assortment of 500-1000 items or for of car dealers) corporate websites Certification programs with specifications (Google Advertising training is a great example). Effective training will work for your business and solve current problems. . Low volume, low risk - it is when you have a narrow segment of users with custom queries but not critical to the brand (for example, users who use SEO tools for PPC). Options for customer onboarding with customer education: Case 4 A knowledge base with a section for custom tool use Segmentation and subsequent training through an email course specialized exclusively on the demands of the audience Documentation for technical support to quickly resolve current issues Practical training can not only solve current problems but prevent new ones. Choosing tools for customer education When you know your customers' pain points, it's time to develop a plan to help them overcome them. To do this, you'll need the right tools and resources. Customer education tools you may need: Learning Management System (LMS) Blog In-product guides In-product notifications Email newsletters Knowledge base outside the LMS Customer success team Metaverse learning The format of content for customer education will depend on the goals, audience, complexity of the product, and level of user knowledge: - great for getting familiar with the product interface or when it would be helpful to ask a person to explain a complex topic Webinars - ideal for sharing step-by-step instructions for complex customizations or interfaces Recorded screen demonstrations - an opportunity to rework existing marketing content for high-level overviews or quick facts Infographics (PDF) - an opportunity to upload previously used content during in-person training Presentations (slides) - they help measure comprehension and help engage and retain users in the training content. Tests and surveys For example, SaaS customer education might include: - initial navigation about what the service can do, how it can help, and where to find more information Post-registration email - step-by-step prompts in the interface when the user first opens it In-product tooltips with the most common questions and articles on effective use In-product knowledge base via email newsletter a few days after signing up Regular live webinars or sending webinar recordings with more in-depth customer onboarding and reminders of where to go for support Follow-up email Visible and fast in-product support Chatbot Now let’s discuss the resources you need to implement your customer education strategy. Resource allocation for customer education You can start designing future customer training when you've figured out the possible tools and formats. And that's where the problem begins... Where to get the resources for implementing a customer education strategy? The most common (and understandable and natural) problem in any company is limited human, time, and financial resources. Where to get the money and time to design and develop your own learning management system (LMS) from scratch? You need a project manager, a business analyst, a learning specialist, a designer, a content creator, a frontend developer, a backend developer, a QA expert... The answer, as usual, is simple. Find the point where you can get the most out of your efforts. This is one case where you don't have to hit hard but know where to hit. For example, if you're losing a significant number of clients in the first few weeks, develop a set of adaptation courses that address those problems in the first place. Or, if you notice the same recurring support request, develop documents for agents to respond to it directly, and put it in a prominent place on your FAQ or blog. That is, you should develop and that first solves customer education's biggest problem. That problem will be different for each company. Still, an expert with business analysis skills will help you find the best point to effectively use company resources while getting the best return on customer education. promote content Create, test, and repeat! Customer education is not a program you create, run and never touch again. It's an iterative process that repeats in cycles, capturing and optimizing new processes each time. It should be seen as a living, dynamic part of the company that needs to be constantly improved, updated, and reevaluated. Just like marketing, sales, and other processes. To work on customer education, you can use any convenient framework already implemented in your project management and involves iterative processes. For example, the is the simplest example of cyclical work on improvement implementation. PDCA model Like all agile methodologies, the PDCA model is based on lean philosophy. So in terms of resource-intensive for the company, it's a fairly advantageous model: Step 1: Analyze and draw up requirements. Step 2. Make a plan for the first iteration. Step 3. Launch and test, detect errors and weak points. Step 4: Correct errors and adjust requirements and workflow if necessary. And repeat! Project management for customer education follows the same principles as project management in any other area and uses the appropriate approaches. I also recommend reading: Why Network Security is an Integral Part of Any Internet-Connected Business How Russian Games Propagated the War The Life and Times of Adobe Flash Player Gaming The 7 Craziest Financial Stories of 2021: Investing in Nothing How Russia is Creating a New "Great Patriotic War (WWII)" With Ukraine

Customer Education: How to Educate Customers Profitable for Business

When you get promoted to a new manager, there are lots of questions in your mind. How do I make sure I am good to my people? How do I get to be successful? What if I screw up? What if others find me incapable? Who can I trust? Who can I ask for help? How should I prioritize? What will be the impact of saying no to someone? With so many questions unanswered, it’s completely natural to feel unprepared. Your struggles are real. When you started as an individual contributor and got to a leadership position, you thought you made it. But now as a manager, you are back to square one. Many people will tell you that you can do better as a manager if you get formal training. But management doesn’t work that way. You can’t learn how to be an effective manager through a few days of training. Yes, knowledge can help you separate right from wrong. But without practicing it yourself, it’s just theory. There are hundreds of books, videos, and podcasts on the topic. Information on what makes an effective manager isn’t the problem. Most of what looks good in theory doesn’t work out in practice. Every decision you make will be different. Every situation you face will be unique. When faced with a difficult situation, it’s likely you’ll forget everything that you have learned. Unless you make mistakes and face the unpleasantness of your failures, unless you feel the brunt of your decisions, and unless you receive criticism, you can’t get better. You’ll need to acquire a set of skills that can only come through practice. Ultimately, it’s your commitment to the process that will determine your progress - James Clear In other words, your process will determine where you end up. Here are the 3 strategies to be effective in your role as a new manager. 3 strategies to be effective as a new manager Let go of your old identity The skills that made you successful as an individual contributor aren’t going to help you as a new manager. They’re in your comfort zone. They make you feel safe. When going gets tough, your natural instinct will be to run to safety, to latch onto behaviors you have come to rely on for so long. But the more you do it, the more they hurt you and your team. Consider this example. You’re a highly regarded coder who recently got promoted to manager. One of your team members is struggling with a piece of code. The deadline to deliver the project is due tomorrow. One option is to guide the team member and help them find a solution on their own. But this risks the deadline and you might have to push it by a day or two. Another is to take over for now, fix the problem yourself, and show them how to do it later. What would you do? Most managers opt for the latter - pressure to meet the deadline takes precedence over enabling coaching and learning for the team. You think you’re making an exception. Just this instance because it was important for you to intervene. In reality, you find it more and more difficult to resist your old habits. Instead of learning the new skills that will help you and your team, you fall back to your old behaviors to save the day. Your role as a manager is not to do the work yourself, even if you are the best at it, because that will only take you so far. Your role is to improve the purpose, people, and process of your team to get as high a multiplier effect on your collective outcome as you can - Julie Zhuo You have to let go of your old identity to give space to a new one. You have to be willing to embrace discomfort. You have to learn to override your default setting. All of this is hard work and requires patience and practice. When tempted to shift to old behaviors, ask yourself these questions: What would an effective manager do in this situation? What skills do they have that would help them deal with this situation? How can I build these skills? What fear is getting in the way of making an effective decision? Building a new identity isn’t about a new title. It involves adopting a new set of beliefs. It requires making changes to how you think about yourself. It requires taking the steps to align that identity with the manager you wish to become. Stop trying too hard As a new manager, there’s this constant pressure to prove yourself. You don’t want anyone questioning your promotion. You want them to know that you deserve to be in this position. But all of these expectations. This desire for flawless execution. The need to prove your worth. It’s nothing but self-induced pressure. Your team members and even your boss don’t expect you to do great from day one. They don’t expect you to not make mistakes. They expect you to learn. They know you’ll not have all the answers. They trust you to find them. They don’t want you to hide your shortcomings. They want to see you’re human. Being vulnerable as a new manager is not a weakness. Embrace it right and it will be your most important strength. Vulnerability is not weakness, and the uncertainty, risk, and emotional exposure we face every day are not optional. Our only choice is a question of engagement. Our willingness to own and engage with our vulnerability determines the depth of our courage and the clarity of our purpose; the level to which we protect ourselves from being vulnerable is a measure of our fear and disconnection - Brené Brown Instead of trying too hard to seek external validation: Spend that time and energy in building new skills and mastering new behaviors. Identify where you’re falling short and what steps you need to take to do better. Seek advice from trusted mentors. Observe seniors you respect in how they make decisions. Ask questions instead of making assumptions. Seek extensive feedback. Asking for help when you need it, and learning from others around you does not reflect on your inadequacies or lack of competence. It only shows that you’re self-aware of your limitations (which by the way also makes you human) and are willing to learn. The two most important traits to become an effective manager. Focus on the inputs Your job is to produce outcomes, no doubt. But focusing solely on the outputs without looking at the inputs that make them possible creates two types of problems: You can’t separate what works from what doesn’t work. You can’t make improvements as you continue to rely on old models of execution even though a better process can lead to significantly better outcomes. When communication breaks down in the team, when decisions turn out wrong when a project misses a deadline, and when a shipped product faces criticism due to quality concerns, spend time on the process. Bring the team together. Share your input and seek theirs. Engage in collaborative inquiry to find answers together. Accountability is important, but no one should be blamed. This has another advantage. Relying on inputs makes your team feel in control. They develop an experimentation mindset. They are forced to think creatively. When something doesn’t work, that’s no reason to give up. When they make a mistake, there’s no reason to hide. It’s an opportunity to tweak their inputs, come up with new solutions and put their abilities to test. It’s also an opportunity to build new skills and learn from the process. As a new manager, it’s hard not to obsess about the outcomes. You want to have an impact. You want to meet targets. You want to be part of growth. You can do that and even more when you base your decisions on inputs. Making good decisions requires excellent thinking. You need to pause, and reevaluate the situation instead of making assumptions, passing judgment, or jumping to conclusions. When doing this with your team, ask these questions: Did we miss a step in the process? How do we know this outcome is the result of wrong inputs? What can we change about our strategy or tactics? Remember this though: you can control your inputs. But you cannot control your outputs. Despite your best efforts, you won’t always get the desired results. Things will fall through the cracks. More than one thing may go wrong. They will all get better eventually if you just focus on the inputs. Your journey into management is just getting started. It can be fulfilling if you embrace it well and painful if you make it so. Developing a performance mindset by obsessing about the outcomes, and doing work to prove your smartness to others will limit your potential. You will be less willing to take on challenging opportunities that require taking a risk. Committing to a learning mindset on the other hand is less about one outcome and more about performance over time. Becoming the best, most capable person you can be, rather than proving that you already are. Your energy will be directed toward acquiring knowledge or skill and the progress you’re making. How much you’re improving. What you’re learning. Adopting a learning mindset changes the meaning of failure - failure is no longer a threat, something to avoid, or something that brings negative emotions. It's evidence of a need for change - rewrite your assumptions, try out a new strategy, put in more effort, and implement a different practice, or a better process. As a new manager, even when it seems like your world is falling apart, remember this: it’s all temporary. It doesn't get easier. Only you get better. All the best! Summary New manager struggles are real. Without the experience to do the job well, it’s hard not to feel overwhelmed. Unlike popular belief, management can’t be learned through training. More than information, of which there’s plenty, you need the willingness to practice and learn from your situation. The desire to do well in your role combined with the lack of experience makes you fall back to old habits that got you promoted but now won’t serve you well. You need to ditch your old identity as an individual contributor to make space for a new one as a manager. Instead of trying too hard to deliver a flawless performance, embrace your imperfections. No one expects you to be an exceptional manager from day one. Mistakes are inevitable. Reach out to mentors, seek advice and demonstrate your willingness to learn. It may seem like your job performance rests on delivering specific outcomes. But, what’s more important than outcomes is the process you use to get there. A single-minded focus on achieving outcomes will hurt your performance. Adopting the attitude of a learner and focusing on the progress you’re making will help you achieve the goals you desire. Previously published . here

How to be Effective as a New Manager?

Artificial intelligence (AI) is a collection of technologies that work alongside each other to allow robots to detect, interpret, act, and learn with human-like intelligence. One area that can see major benefits from artificial intelligence is Healthcare Behavioural Management (HBM). AI helps healthcare providers to understand the regular routines and needs of the people under their care. This enables them to provide better feedback, guidance and support for their patients, helping them to maintain good health. In this post we’ll look at how AI is changing the healthcare industry as well as Healthcare Behavioural Management (HBM). How is Artificial Intelligence (AI) being used in the healthcare industry? Artificial intelligence is already being used to diagnose diseases more precisely and early on, such as cancer. According to the , a significant number of mammograms provide false findings, resulting in one out of every two healthy women being diagnosed with cancer. American Cancer Society AI is allowing mammograms to be reviewed and translated with 99% accuracy, decreasing the need for unneeded biopsies. 30 times faster Wearable technology and other medical equipment are being utilised in conjunction with AI to monitor and diagnose potentially fatal events in early-stage heart disease. This allows doctors and other caregivers to better monitor and detect potentially life-threatening episodes at an earlier, more treatable stage. Predictive analytics are also being used to help clinical decision-making and actions, as well as prioritize administrative activities. This is done to improve treatment by aligning massive health data with suitable and timely judgments. The use of pattern recognition to identify patients who are at risk of getting an illness – or seeing one get worse – as a consequence of lifestyle, environmental, genetic, or other variables is another area where artificial intelligence is beginning to take root in the healthcare industry. AI is being used to help clinicians take a more comprehensive approach to disease management, better coordinate care plans, and help patients better manage and comply with their long-term treatment programmes. In addition to the above, artificial intelligence is being used to scan health data to assist caregivers in identifying seriously unwell patients who may be at risk of an adverse episode. Artificial Intelligence In Health Behaviour Management Health plans spend a lot of money maintaining their members' health in order to enhance their outcomes. Suboptimal health behaviour, in addition to higher operating costs, raises the probability of poor health outcomes among members dramatically. The factors influencing people's health decisions are more complicated than ever before, thanks to technology advancements and increased access to healthcare information and services. Existing engagement solutions are limited in their ability to recognise people's concerns at a large scale. Furthermore, their techniques are primarily focused on communications, which can be unpleasant and negatively impact the member experience. is one software company that has been working on AI-based solutions for Health Behaviour Management. MedOrion Their Health Behaviour Management (HBM) solution enables health plans to transition away from outsourced member-engagement services and toward an end-to-end self-service software solution that focuses on long-term behavioural change. This gives health plans more control over their processes, priorities, and full visibility into their members' experiences. This also makes it possible for them to immediately change course when necessary to ensure positive changes in their members' health and relationships. The system examines each member's claims, clinical, and demographic data, combining social determinants of health (SDoH) to uncover members' worries about a number of measures, such as drugs, immunizations, and cancer screening. The platform also won the , setup by which sought creative ways to both patient education and vaccination access. Vaccines Global Innovation Challenge Pfizer The most relevant barriers to action are then identified using behavioural science and AI. Once determined, HBM creates a persuasive communication approach that is regarded best appropriate for each individual member. Member level health behaviour insights collect and grow more accurately over time as more member data and response patterns are analyzed by HBM monitoring technologies. Leading tactics and products may then be better tailored to the preferences of members. This enables health plans to build deeper member relationships, be more helpful in real time, and stay on top of the ever-changing healthcare landscape. As trust and involvement with members improve, so does adherence to prescribed courses of action. As a result, health plans operate more effectively, increasing overall revenues and outperforming rival health plans in terms of quality. Final Thoughts Due to its crucial role in a productive, healthy society, healthcare is one of the most important areas in the larger landscape of big data. AI in healthcare may improve patient outcomes through improving preventative care and quality of life, as well as producing more accurate diagnosis and treatment regimens. By analyzing data from the government, healthcare, and other sources, AI can help anticipate and track the spread of contagious illnesses. Due to the above, artificial intelligence has the potential to be a crucial tool in the global public health fight against diseases and pandemics. The content is this story is provided by an independent contributor and does not represent the views of Hacker Noon. Disclaimer:

The Impact of Artificial Intelligence on Health Behaviour Management

HackerNoon Reporter: Please tell us briefly about your background. My name is Faustino Fernandez, and I’m the Founder & CEO of STAYmyway, a technology-based company born in Murcia in 2014. We are specialized in developing intelligent solutions for the automation of processes in hotels and vacation rental accommodations. From the beginning, our vision was to digitize the daily operations ( ) of hotels and tourist apartments, offering a technology that brings value to both management and the guests. mobile key, smart locks, check-in online, etc. For the first ones, these solutions provide time savings and agility, thus reducing costs, while tourists enjoy a much more flexible and comfortable experience before, during, and after their stay. What's your startup called? And in a sentence or two, what does it do? The startup is named STAYmyway, and we are committed to digitizing the hospitality industry and automating daily operations, especially check-ins and check-outs, of hotels and tourist apartments. Our solutions optimize time and costs while providing an excellent and flexible stay to the guest. What is the origin story? I am an industrial engineer, and seeing the evolution and implementation of smartphones in our daily lives made me think about how comfortable it would be to stop carrying traditional keys and open any door from our cell phones. With this idea, we started working on the project to realize soon that a sector that could benefit from digitizing the entry process with a mobile key was the hospitality industry. In my experience, I have always found it a waste of time to arrive at the hotel front desk and wait in line to pick up the key and hand over your details. The same thing happened when I rented an apartment; I had to go through the agency to check in or wait in the street until someone arrived with the key. So we started to develop technology solutions to facilitate the check-in and check-out processes in hotels and vacation rental apartments that would be beneficial and bring value to both the owner and the guest. What do you love about your team, and why are you the ones to solve this problem? I love the passion of the STAYmyway team, how they are involved and committed to developing and evolving both our technology solutions and the company's growth. A genuine passion for mobile technology that adds value to hotels and short-term rentals properties. Well, maybe it is a little pretentious to say we are the ones, but definitely, we are the most to . Our works with any hotel from the smallest one to the global chains, and it is the same with the vacation rental properties. Why are we the ones to solve this problem? flexible and cost-effective automate check-in and check-out processes Mobile Key And the most significant difference is that our technology can convert almost any traditional lock into a digital lock in a few minutes. These solutions are compatible with most lock manufacturers on the market without the need to change them. If you weren’t building your startup, what would you be doing? The audiovisual world is very attractive for me, so if I were not running the STAYmyway project, I would like to think I'd go into video or filmmaking. Something completely different, more creative storytelling from any discipline related to this field. At the moment, how do you measure success? What are your core metrics? Our success is measured by the need of the market and the users. We want to digitize the hospitality industry, offer new tools to guests to save time, and maintain safety protocols. We are a company that believes that the most important metric is our customer retention. That means that customers are happy with the products and services we provide for them. There is no better feedback than knowing your customers are satisfied with what you've created to succeed. What milestones have Staymyway achieved so far? STAYmyway was born to provide a solution for the hospitality industry that at that time did not exist.  To offer the possibility for hotels and short-term rental accommodation to digitize their locks without the need to change the ones they already had installed for new ones and offer the guest remote access to the hotel room or apartment. Another significant milestone was the beginning of the international expansion two years after our birth, with our office opening in the USA to meet the demand of the North American and LATAM markets. This year we have achieved another critical milestone by reaching an agreement to be the sole global supplier of the mobile key for the Accor chain, the 3rd largest hotel chain in the world with more than 5000 properties in 110 countries. Finally, considering that the last year has been exceptional for tourism worldwide, due to the travel restrictions caused by the pandemic, we have achieved good figures in our leading products already deployed in Europe and America. What’s most exciting about your traction to date? There have been two critical moments in the history of STAYmyway. The first was when we decided to pivot and focus solely on hospitality, and the second was the signing of the contract as the sole supplier of Accor Mobile Key last year. What has been the funniest anecdote since its foundation? The company was founded as Lock-Up in 2014, and then, when we opened our subsidiary in the United States, we were Lock-Up America.  At the first show we exhibited in the United States, they put a giant sign in our booth with the company's name Lock-Up America. We were the joke on the show because people were saying... "There are some Spanish out there who say they are going to imprison America." What drew you to get published on HackerNoon? What do you like most about our platform? We appreciate having a platform focussed on tech-related news that creates a community where you can find the latest innovations and trends by knowledgeable writers, and we wanted to be part of it. Being nominated for Startup Of The Year lets us know better about this community. What is something surprising you've learned this year that your contemporaries would benefit from knowing? The tourism industry has proven to be one of the most resilient during this last year and a half with the pandemic. I believe that sector digitalization is key to improve the competitiveness of the hotel or short term rentals accommodation and to achieve greater guest loyalty: A Mobile Key system increases the guest' satisfaction scores up to 7%. A Digital Check-in process can reduce the guest waiting time by up to 70%. Don’t forget to vote for as STAYmyway Startup of the Year in Murcia

Mobile Keys: Visiting Made Easy

Stories, News & Mentions about BETTERFEEDBACK

Betterfeedback’s Stories on HackerNoon