The Element platform is based on a microservices structure

Element

element

Enhance Your Code Architecture With SOLID Principles (with Swift Examples)

Building a UDP Server & Client in Swift with Network.framework

Do you know that feeling when you create your own component instead of improving the default HTML components? Your design team created something beautiful, but browsers won't support it out of the box, and fixing it everywhere becomes a nightmare. We all know this pain, but these challenges make our job interesting. Today, I wanted to talk about one pitfall that awaits us during this thrilling journey: the placement of dropdown elements, such as the select menus or the date pickers. Absolutely Wrong At first, it looks like position: absolute solves all our problems, and it does to some extent. But then, modal windows ruin everything. If the dropdown overflows, it gets cut off. Sure, you can scroll down and see it, but you’d better pray that your designer cannot reach you with a sharp object. That’s far from perfect—we can do better. Fix It With 'fixed' If we want to display the content over everything, we need position: fixed. The only problem is that we will lose the parent element coordinates: fixed elements are quite independent by nature. This means the only thing we need to do is determine the exact coordinates of the drop-down element in these situations: When we display it.
When its content is changed.
When we scroll the window and/or the scrollable parent.
When we resize the window and/or the scrollable parent. We also need to decide whether to display it above the toggler if it is too close to the bottom of the screen. Feels doable. I will use Vue.js, but it should be easy to follow even if you prefer React or Angular. Let’s Rock This Joint Here’s the structure we’ll use: export const useDropdownAttributes = () => {
  const dropdownWidth = ref('');
  const dropdownTop = ref('');
  const dropdownBottom = ref('');
  const dropdownLeft = ref('');
  const isDirectedUpwards = ref(false);
  const togglerRect = ref<DOMRect>();
  const dropdownRect = ref<DOMRect>();

  const autodetectPosition = (
    isDropdownDisplayed: Ref<boolean>,
    togglerElement: HTMLElement | null = null,
    dropdownElement: HTMLDivElement | null = null,
    dropdownContent: Ref<unknown> | ComputedRef<unknown> = ref([]),
    isUpwardPreferred = false,
  ) => {
    // ...
  }

  return {
    autodetectPosition,
    dropdownTop,
    dropdownBottom,
    dropdownLeft,
    dropdownWidth,
    isDirectedUpwards,
    togglerRect,
    dropdownRect,
  };
}; There are four variables for the dropdown position plus the isDirectedUpwards flag and a function that updates them all. We also return two variables for the toggler’s and dropdown’s Rects: this might be convenient, for example, for the tooltips that need to be aligned to the middle of the content. As you may remember, we also need to handle the scrolling and resizing of the scrollable parent, so let’s create a function to find it: const getFirstScrollableParent = (element: HTMLElement | null): HTMLElement => {
    const parentElement = element?.parentElement;
    if (!parentElement) return document.body;

    const overflowY = window.getComputedStyle(parentElement).overflowY;

    if (overflowY === 'scroll' || overflowY === 'auto') return parentElement;

    return getFirstScrollableParent(parentElement);
  }; Now, let’s add the main function: const autodetectPosition = (
    isDropdownDisplayed: Ref<boolean>,
    togglerElement: HTMLElement | null = null,
    dropdownElement: HTMLElement | null = null,
    dropdownContent: Ref<unknown> | ComputedRef<unknown> = ref([]),
    isUpwardPreferred = false,
  ) => {
    if (!togglerElement || !dropdownElement) return;

    const updateDropdownAttributes = () => {
      togglerRect.value = togglerElement.getBoundingClientRect();
      dropdownRect.value = dropdownElement.getBoundingClientRect();
      dropdownWidth.value = `${togglerRect.value.width}px`;
      dropdownBottom.value = `${window.innerHeight - togglerRect.value.top}px`;
      dropdownTop.value = `${
        window.innerHeight - togglerRect.value.bottom - dropdownRect.value.height
      }px`;
      dropdownLeft.value = `${togglerRect.value.left}px`;
    };

    const handleResize = () => {
      requestAnimationFrame(updateDropdownAttributes);
    };

    const handleScroll = () => {
      requestAnimationFrame(updateDropdownAttributes);
    };

    watch(
      [isDropdownDisplayed, dropdownContent],
      ([newVal, _]) => {
        const scrollableParent = getFirstScrollableParent(togglerElement);
        if (!newVal) {
          window.removeEventListener('resize', handleResize);
          window.removeEventListener('scroll', handleScroll);
          scrollableParent.removeEventListener('resize', handleResize);
          scrollableParent.removeEventListener('scroll', handleScroll);
          return;
        }

        requestAnimationFrame(() => {
          const distanceFromBottom =
            window.innerHeight - togglerElement.getBoundingClientRect().bottom;
          const distanceFromTop = togglerElement.getBoundingClientRect().top;
          const dropdownHeight = dropdownElement.offsetHeight;

          isDirectedUpwards.value = isUpwardPreferred
            ? distanceFromTop > dropdownHeight
            : distanceFromBottom < dropdownHeight &&
              distanceFromTop > dropdownHeight;

          updateDropdownAttributes();
          window.addEventListener('resize', handleResize);
          window.addEventListener('scroll', handleScroll);
          scrollableParent.addEventListener('resize', handleResize);
          scrollableParent.addEventListener('scroll', handleScroll);
        });
      },
      { deep: true },
    );
  }; We pass isDropdownDisplayed and dropdownContent so we can react to their updates. We also pass togglerElement and dropdownElementwhich we need to calculate the position. Finally, there’s isUpwardPreferred in case you want the dropdown above the toggler by default. Time to Relax and Enjoy In your component, you will need something like this (I assume you have added refs to your toggler and dropdown in the template): const {
  autodetectPosition,
  dropdownTop,
  dropdownBottom,
  dropdownLeft,
  dropdownWidth,
  isDirectedUpwards,
} = useDropdownAttributes();

const togglerRef = ref<HTMLElement>();
const dropdownRef = ref<HTMLElement>();

const isDropdownShown = ref(false);

onMounted(() => {
  autodetectPosition(isDropdownShown, togglerRef.value?.$el, dropdownRef.value?.$el);
}); And the CSS will look like this: .dropdown {
  position: fixed;
  bottom: v-bind('isDirectedUpwards ? dropdownBottom : dropdownTop');
  left: v-bind('dropdownLeft');

  width: v-bind('dropdownWidth');
  min-width: 0;
} Voilà. The dropdown is displayed properly even when overflowing and moves above the toggler if there isn’t enough space below. And since we’re at the end of the article, I’d love to leave you with something cheerful—but I’m out of ideas. So, I'm afraid "good luck" is all I have this time. Good luck. 👋 You can find the complete code on GitHub. Do you know that feeling when you create your own component instead of improving the default HTML components? Your design team created something beautiful, but browsers won't support it out of the box, and fixing it everywhere becomes a nightmare. We all know this pain, but these challenges make our job interesting. Today, I wanted to talk about one pitfall that awaits us during this thrilling journey: the placement of dropdown elements, such as the select menus or the date pickers. Absolutely Wrong At first, it looks like position: absolute solves all our problems, and it does to some extent. But then, modal windows ruin everything. position: absolute If the dropdown overflows, it gets cut off. Sure, you can scroll down and see it, but you’d better pray that your designer cannot reach you with a sharp object. That’s far from perfect—we can do better. Fix It With 'fixed' 'fixed' If we want to display the content over everything, we need position: fixed . The only problem is that we will lose the parent element coordinates: fixed elements are quite independent by nature. This means the only thing we need to do is determine the exact coordinates of the drop-down element in these situations: position: fixed When we display it. When its content is changed. When we scroll the window and/or the scrollable parent. When we resize the window and/or the scrollable parent. When we display it. When its content is changed. When we scroll the window and/or the scrollable parent. When we resize the window and/or the scrollable parent. We also need to decide whether to display it above the toggler if it is too close to the bottom of the screen. Feels doable. I will use Vue.js, but it should be easy to follow even if you prefer React or Angular. Let’s Rock This Joint Here’s the structure we’ll use: export const useDropdownAttributes = () => {
  const dropdownWidth = ref('');
  const dropdownTop = ref('');
  const dropdownBottom = ref('');
  const dropdownLeft = ref('');
  const isDirectedUpwards = ref(false);
  const togglerRect = ref<DOMRect>();
  const dropdownRect = ref<DOMRect>();

  const autodetectPosition = (
    isDropdownDisplayed: Ref<boolean>,
    togglerElement: HTMLElement | null = null,
    dropdownElement: HTMLDivElement | null = null,
    dropdownContent: Ref<unknown> | ComputedRef<unknown> = ref([]),
    isUpwardPreferred = false,
  ) => {
    // ...
  }

  return {
    autodetectPosition,
    dropdownTop,
    dropdownBottom,
    dropdownLeft,
    dropdownWidth,
    isDirectedUpwards,
    togglerRect,
    dropdownRect,
  };
}; export const useDropdownAttributes = () => {
  const dropdownWidth = ref('');
  const dropdownTop = ref('');
  const dropdownBottom = ref('');
  const dropdownLeft = ref('');
  const isDirectedUpwards = ref(false);
  const togglerRect = ref<DOMRect>();
  const dropdownRect = ref<DOMRect>();

  const autodetectPosition = (
    isDropdownDisplayed: Ref<boolean>,
    togglerElement: HTMLElement | null = null,
    dropdownElement: HTMLDivElement | null = null,
    dropdownContent: Ref<unknown> | ComputedRef<unknown> = ref([]),
    isUpwardPreferred = false,
  ) => {
    // ...
  }

  return {
    autodetectPosition,
    dropdownTop,
    dropdownBottom,
    dropdownLeft,
    dropdownWidth,
    isDirectedUpwards,
    togglerRect,
    dropdownRect,
  };
}; There are four variables for the dropdown position plus the isDirectedUpwards flag and a function that updates them all. We also return two variables for the toggler’s and dropdown’s Rects: this might be convenient, for example, for the tooltips that need to be aligned to the middle of the content. isDirectedUpwards As you may remember, we also need to handle the scrolling and resizing of the scrollable parent, so let’s create a function to find it: const getFirstScrollableParent = (element: HTMLElement | null): HTMLElement => {
    const parentElement = element?.parentElement;
    if (!parentElement) return document.body;

    const overflowY = window.getComputedStyle(parentElement).overflowY;

    if (overflowY === 'scroll' || overflowY === 'auto') return parentElement;

    return getFirstScrollableParent(parentElement);
  }; const getFirstScrollableParent = (element: HTMLElement | null): HTMLElement => {
    const parentElement = element?.parentElement;
    if (!parentElement) return document.body;

    const overflowY = window.getComputedStyle(parentElement).overflowY;

    if (overflowY === 'scroll' || overflowY === 'auto') return parentElement;

    return getFirstScrollableParent(parentElement);
  }; Now, let’s add the main function: const autodetectPosition = (
    isDropdownDisplayed: Ref<boolean>,
    togglerElement: HTMLElement | null = null,
    dropdownElement: HTMLElement | null = null,
    dropdownContent: Ref<unknown> | ComputedRef<unknown> = ref([]),
    isUpwardPreferred = false,
  ) => {
    if (!togglerElement || !dropdownElement) return;

    const updateDropdownAttributes = () => {
      togglerRect.value = togglerElement.getBoundingClientRect();
      dropdownRect.value = dropdownElement.getBoundingClientRect();
      dropdownWidth.value = `${togglerRect.value.width}px`;
      dropdownBottom.value = `${window.innerHeight - togglerRect.value.top}px`;
      dropdownTop.value = `${
        window.innerHeight - togglerRect.value.bottom - dropdownRect.value.height
      }px`;
      dropdownLeft.value = `${togglerRect.value.left}px`;
    };

    const handleResize = () => {
      requestAnimationFrame(updateDropdownAttributes);
    };

    const handleScroll = () => {
      requestAnimationFrame(updateDropdownAttributes);
    };

    watch(
      [isDropdownDisplayed, dropdownContent],
      ([newVal, _]) => {
        const scrollableParent = getFirstScrollableParent(togglerElement);
        if (!newVal) {
          window.removeEventListener('resize', handleResize);
          window.removeEventListener('scroll', handleScroll);
          scrollableParent.removeEventListener('resize', handleResize);
          scrollableParent.removeEventListener('scroll', handleScroll);
          return;
        }

        requestAnimationFrame(() => {
          const distanceFromBottom =
            window.innerHeight - togglerElement.getBoundingClientRect().bottom;
          const distanceFromTop = togglerElement.getBoundingClientRect().top;
          const dropdownHeight = dropdownElement.offsetHeight;

          isDirectedUpwards.value = isUpwardPreferred
            ? distanceFromTop > dropdownHeight
            : distanceFromBottom < dropdownHeight &&
              distanceFromTop > dropdownHeight;

          updateDropdownAttributes();
          window.addEventListener('resize', handleResize);
          window.addEventListener('scroll', handleScroll);
          scrollableParent.addEventListener('resize', handleResize);
          scrollableParent.addEventListener('scroll', handleScroll);
        });
      },
      { deep: true },
    );
  }; const autodetectPosition = (
    isDropdownDisplayed: Ref<boolean>,
    togglerElement: HTMLElement | null = null,
    dropdownElement: HTMLElement | null = null,
    dropdownContent: Ref<unknown> | ComputedRef<unknown> = ref([]),
    isUpwardPreferred = false,
  ) => {
    if (!togglerElement || !dropdownElement) return;

    const updateDropdownAttributes = () => {
      togglerRect.value = togglerElement.getBoundingClientRect();
      dropdownRect.value = dropdownElement.getBoundingClientRect();
      dropdownWidth.value = `${togglerRect.value.width}px`;
      dropdownBottom.value = `${window.innerHeight - togglerRect.value.top}px`;
      dropdownTop.value = `${
        window.innerHeight - togglerRect.value.bottom - dropdownRect.value.height
      }px`;
      dropdownLeft.value = `${togglerRect.value.left}px`;
    };

    const handleResize = () => {
      requestAnimationFrame(updateDropdownAttributes);
    };

    const handleScroll = () => {
      requestAnimationFrame(updateDropdownAttributes);
    };

    watch(
      [isDropdownDisplayed, dropdownContent],
      ([newVal, _]) => {
        const scrollableParent = getFirstScrollableParent(togglerElement);
        if (!newVal) {
          window.removeEventListener('resize', handleResize);
          window.removeEventListener('scroll', handleScroll);
          scrollableParent.removeEventListener('resize', handleResize);
          scrollableParent.removeEventListener('scroll', handleScroll);
          return;
        }

        requestAnimationFrame(() => {
          const distanceFromBottom =
            window.innerHeight - togglerElement.getBoundingClientRect().bottom;
          const distanceFromTop = togglerElement.getBoundingClientRect().top;
          const dropdownHeight = dropdownElement.offsetHeight;

          isDirectedUpwards.value = isUpwardPreferred
            ? distanceFromTop > dropdownHeight
            : distanceFromBottom < dropdownHeight &&
              distanceFromTop > dropdownHeight;

          updateDropdownAttributes();
          window.addEventListener('resize', handleResize);
          window.addEventListener('scroll', handleScroll);
          scrollableParent.addEventListener('resize', handleResize);
          scrollableParent.addEventListener('scroll', handleScroll);
        });
      },
      { deep: true },
    );
  }; We pass isDropdownDisplayed and dropdownContent so we can react to their updates. isDropdownDisplayed dropdownContent We also pass togglerElement and dropdownElement which we need to calculate the position. togglerElement dropdownElement Finally, there’s isUpwardPreferred in case you want the dropdown above the toggler by default. isUpwardPreferred Time to Relax and Enjoy In your component, you will need something like this (I assume you have added refs to your toggler and dropdown in the template): const {
  autodetectPosition,
  dropdownTop,
  dropdownBottom,
  dropdownLeft,
  dropdownWidth,
  isDirectedUpwards,
} = useDropdownAttributes();

const togglerRef = ref<HTMLElement>();
const dropdownRef = ref<HTMLElement>();

const isDropdownShown = ref(false);

onMounted(() => {
  autodetectPosition(isDropdownShown, togglerRef.value?.$el, dropdownRef.value?.$el);
}); const {
  autodetectPosition,
  dropdownTop,
  dropdownBottom,
  dropdownLeft,
  dropdownWidth,
  isDirectedUpwards,
} = useDropdownAttributes();

const togglerRef = ref<HTMLElement>();
const dropdownRef = ref<HTMLElement>();

const isDropdownShown = ref(false);

onMounted(() => {
  autodetectPosition(isDropdownShown, togglerRef.value?.$el, dropdownRef.value?.$el);
}); And the CSS will look like this: .dropdown {
  position: fixed;
  bottom: v-bind('isDirectedUpwards ? dropdownBottom : dropdownTop');
  left: v-bind('dropdownLeft');

  width: v-bind('dropdownWidth');
  min-width: 0;
} .dropdown {
  position: fixed;
  bottom: v-bind('isDirectedUpwards ? dropdownBottom : dropdownTop');
  left: v-bind('dropdownLeft');

  width: v-bind('dropdownWidth');
  min-width: 0;
} Voilà. The dropdown is displayed properly even when overflowing and moves above the toggler if there isn’t enough space below. And since we’re at the end of the article, I’d love to leave you with something cheerful—but I’m out of ideas. So, I'm afraid "good luck" is all I have this time. Good luck. 👋 You can find the complete code on GitHub. You can find the complete code on GitHub . GitHub

Proper Display of Custom Dropdown Elements: A How-to Guide

العرض الصحيح لعناصر القائمة المنسدلة المخصصة: دليل إرشادي

Σωστή εμφάνιση προσαρμοσμένων αναπτυσσόμενων στοιχείων: Οδηγός πώς να το κάνετε

Presentación correcta de elementos de descarga personalizados: una guía de cómo

カスタム ドロップダウン要素の適切な表示: ハウツー ガイド

사용자 정의 드롭다운 요소의 적절한 표시: 방법 가이드

Правилно прикажување на приспособени паѓачки елементи: Водич како да се

Pontšo ya maleba ya Dielemente tša go Theoga tša Tlwaelo: Tlhahlo ya Tsela ya go Dira

Prawidłowe wyświetlanie niestandardowych elementów rozwijania: przewodnik

Одговарајући приказ прилагођених падајућих елемената: водич са упутствима

Özel Açılır Öğelerin Doğru Görüntülenmesi: Nasıl Yapılır Kılavuzu

حسب ضرورت ڈراپ ڈاؤن عناصر کا مناسب ڈسپلے: ایک گائیڈ

Developers’ Insights on Game Design Elements: Pros and Cons

Authors:
(1) Clauvin Almeida, Pontifical Catholic University of Rio de Janeiro (PUC-Rio), Rio de Janeiro, Brazil;
(2) Marcos Kalinowski, Pontifical Catholic University of Rio de Janeiro (PUC-Rio), Rio de Janeiro, Brazil;
(3) Anderson Uchoa, Federal University of Ceara (UFC), Itapaje, Brazil;
(4) Bruno Feijo, Pontifical Catholic University of Rio de Janeiro (PUC-Rio), Rio de Janeiro, Brazil. Table of Links Abstract and 1 Introduction 2. Background and Related Work and 2.1. Gamification 2.2. Game Design Elements and 2.3. Gamification Effects 2.4. Related Work on Gamification Negative Effects 3. Systematic Mapping and 3.1. The Research Questions 3.2. Search Strategy and 3.3. Inclusion and Exclusion Criteria 3.4. Applying the Search Strategy 3.5. Data Extraction 4. Systematic Mapping Results 5. Focus Group: Developer Perception on the Negative Effects of Game Design Elements 5.1. Context and Participant Characterization 5.2. Focus Group Design 5.3. The Developers’ Perception on The Negative Effects 5.4. On the Perceived Usefulness, Ease of use and Intent of Adoption of Mapped Negative Effects 5.5. Participant Feedback 6. Limitations 7. Concluding Remarks 7.1. Future Research Directions Acknowledgements and References 5.2. Focus Group Design We carefully designed and performed our focus group by following the guideline proposed by Kontio et al. [107]. Figure 6 depicts the steps adopted throughout the focus group. We organized these steps in three major phases: (1) Preparation for the focus group session; (2) Discussion by group of game design elements; and (3) Discussion on the perception of the mapped negative effects. We describe each phase and step hereafter. Phase 1: Preparation for the focus group session – This phase consists of the collection of preliminary resources for supporting the execution of the focus group session. For this purpose, we follow two steps. Step 1 consisted of recruiting developers with experience in gamification to engage in discussions. As mentioned in Section 5.1, we contacted developers of the VazaZika development team for participating in our study. We obtained the acceptance of four developers via Consent Form in which we explain our research goals, information about the waiver statements, and that the information provided by each participant will be treated confidentially and used for study purposes only. Step 2 aimed to collecting basic information to characterize the participants via the Participant Characterization Form. Our major goal was profiling each developer, so we could better interpret our study results. We opted for asking short and simple questions in order to prevent participants from being tired or discouraged to participate in discussions right after filling out the form. More specifically, we collected data on the education level, years of experience with software development (academy and industry), the number of software projects they participated, and the level of knowledge about gamification and game design elements (see Table 16). Due to the geographic distribution of our participants, we used an online environment to promote discussions on the negative effects of game design elements. Figure 7 illustrates the virtual template that we designed using the MURAL online tool[2]. In practice, by using this tool, we were able to build an interactive mural to facilitate the conduction of the focus group session. Our mural has eight well-defined sections. Sections A to G aimed at driving the discussion regarding the negative effects of game design elements. In order to facilitate discussions, we have semantically grouped the game design elements by section as follow: (A) Badges and Rewards; (B) Competitions, Challenges, and Goals; (C) Leaderboards and Rankings; (D) Points, XPs, and Virtual Currencies; Feedback and Achievements; (E) Avatars; and (F) Quizzes. Finally, Section G aimed at driving the discussion and capturing the level of agreement on the usefulness, ease to use, and intention to use the information on potential negative effects of game design elements. Figure 8 illustrates the template that we have defined for each aforementioned section. A section is composed of four parts (1, 2, 3, and 4). Part 1 contains a short description of the involved game design elements and the identified negative effects based on the literature. Part 2 is designed for capturing votes on the awareness degree concern the negative effects based on a four-point scale: completely unaware, mostly unaware, mostly aware, and completely aware. Finally, parts 3 and 4 were designed for participants to add notes on the Pros and Cons of using the game design elements, respectively. Phase 2: Discussion by game design elements – This phase consists in collecting data regarding the developer’s perception of the negative effects identified in the literature. As aforementioned, we have divide the game design elements in groups to facilitate the discussions and used a Mural discussion canvas. Thus, each group of game design elements is discussed in isolation. We defined three steps as follows. Step 1 aimed at introducing each group of game design elements, and the negative effects. For this purpose, the moderator of the session read this information out loud (part 1 of Figure 8). Next, in Step 2, we asked each participant to assign one vote to the awareness degree of the group of game design elements according to the four-point scale depicted in part 2 of Figure 8. Each participant voted individually, without knowing the votes of his colleagues. At the end, the moderator showed the number of votes per awareness agree. Finally, in Step 3, we asked the participants to discuss and elicit Pros and Cons of using the game design elements. In this step, each comment should be documented as a note in the appropriate part: part 3 for positive comments and part 4 for negative ones, as shown in Figure 8. The note was just a brief summary of a Pro or a Con, typically taken within seconds, and we constantly asked participants to share knowledge and experiences surrounding the use of each game design element, to enrich the discussions and understandings. Additionally, whenever the moderator felt that a note is poorly written, he asked the participants to provide further considerations on the note. Phase 3: Discussion about the perception of the mapped negative effects – After discussing all groups of game design elements, the focus group session ended with a final discussion about the perceptions regarding the mapped negative effects. This phase has two steps described as follows. In Step 1, based on the main constructs of the Technology Acceptance Model (TAM) [113], we asked each participant to assign one vote to their agreement with each of the following statements (as illustrated in Section G of Figure 7): (1) I find the information on potential negative effects of game design elements useful to support game design element adoption decisions; (2) I find the information on potential negative effects of game design element easy to use to support game design element adoption decisions; and (3) I intend to use the information on potential negative effects of game design element to support game design element adoption decisions. We have used the five-point scale depicted in Figure 7 (G). Finally, Step 2 aimed at collecting data about the participant’s experience with the focus group session. Thus, by the end of the focus group session, we asked participants to fill out a Follow-up Form. We aimed at assuring that each developer felt confident and comfortable to discuss the negative effect of game design elements. We emphasize that the focus group session was conducted online via a Zoom Meeting. Additionally, we kept video and audio records of the session to support the data analysis. We often accessed the video and audio records for understanding what developers meant with each note. The focus group session was conducted in January 24, 2022 lasting one and a half hours. This paper is available on arxiv under CC BY 4.0 DEED license. [2] https://www.mural.co/ Authors: (1) Clauvin Almeida, Pontifical Catholic University of Rio de Janeiro (PUC-Rio), Rio de Janeiro, Brazil; (2) Marcos Kalinowski, Pontifical Catholic University of Rio de Janeiro (PUC-Rio), Rio de Janeiro, Brazil; (3) Anderson Uchoa, Federal University of Ceara (UFC), Itapaje, Brazil; (4) Bruno Feijo, Pontifical Catholic University of Rio de Janeiro (PUC-Rio), Rio de Janeiro, Brazil. Authors: Authors: (1) Clauvin Almeida, Pontifical Catholic University of Rio de Janeiro (PUC-Rio), Rio de Janeiro, Brazil; (2) Marcos Kalinowski, Pontifical Catholic University of Rio de Janeiro (PUC-Rio), Rio de Janeiro, Brazil; (3) Anderson Uchoa, Federal University of Ceara (UFC), Itapaje, Brazil; (4) Bruno Feijo, Pontifical Catholic University of Rio de Janeiro (PUC-Rio), Rio de Janeiro, Brazil. Table of Links Abstract and 1 Introduction Abstract and 1 Introduction 2. Background and Related Work and 2.1. Gamification 2. Background and Related Work and 2.1. Gamification 2.2. Game Design Elements and 2.3. Gamification Effects 2.2. Game Design Elements and 2.3. Gamification Effects 2.4. Related Work on Gamification Negative Effects 2.4. Related Work on Gamification Negative Effects 3. Systematic Mapping and 3.1. The Research Questions 3. Systematic Mapping and 3.1. The Research Questions 3.2. Search Strategy and 3.3. Inclusion and Exclusion Criteria 3.2. Search Strategy and 3.3. Inclusion and Exclusion Criteria 3.4. Applying the Search Strategy 3.4. Applying the Search Strategy 3.5. Data Extraction 3.5. Data Extraction 4. Systematic Mapping Results 4. Systematic Mapping Results 5. Focus Group: Developer Perception on the Negative Effects of Game Design Elements 5. Focus Group: Developer Perception on the Negative Effects of Game Design Elements 5.1. Context and Participant Characterization 5.1. Context and Participant Characterization 5.2. Focus Group Design 5.2. Focus Group Design 5.3. The Developers’ Perception on The Negative Effects 5.3. The Developers’ Perception on The Negative Effects 5.4. On the Perceived Usefulness, Ease of use and Intent of Adoption of Mapped Negative Effects 5.4. On the Perceived Usefulness, Ease of use and Intent of Adoption of Mapped Negative Effects 5.5. Participant Feedback 5.5. Participant Feedback 6. Limitations 6. Limitations 7. Concluding Remarks 7. Concluding Remarks 7.1. Future Research Directions 7.1. Future Research Directions Acknowledgements and References Acknowledgements and References 5.2. Focus Group Design We carefully designed and performed our focus group by following the guideline proposed by Kontio et al. [107]. Figure 6 depicts the steps adopted throughout the focus group. We organized these steps in three major phases: (1) Preparation for the focus group session; (2) Discussion by group of game design elements; and (3) Discussion on the perception of the mapped negative effects. We describe each phase and step hereafter. Phase 1: Preparation for the focus group session – This phase consists of the collection of preliminary resources for supporting the execution of the focus group session. For this purpose, we follow two steps. Step 1 consisted of recruiting developers with experience in gamification to engage in discussions. As mentioned in Section 5.1, we contacted developers of the VazaZika development team for participating in our study. We obtained the acceptance of four developers via Consent Form in which we explain our research goals, information about the waiver statements, and that the information provided by each participant will be treated confidentially and used for study purposes only. Step 2 aimed to collecting basic information to characterize the participants via the Participant Characterization Form. Our major goal was profiling each developer, so we could better interpret our study results. We opted for asking short and simple questions in order to prevent participants from being tired or discouraged to participate in discussions right after filling out the form. More specifically, we collected data on the education level, years of experience with software development (academy and industry), the number of software projects they participated, and the level of knowledge about gamification and game design elements (see Table 16). Phase 1: Preparation for the focus group session Step 1 Step 2 Due to the geographic distribution of our participants, we used an online environment to promote discussions on the negative effects of game design elements. Figure 7 illustrates the virtual template that we designed using the MURAL online tool[2]. In practice, by using this tool, we were able to build an interactive mural to facilitate the conduction of the focus group session. Our mural has eight well-defined sections. Sections A to G aimed at driving the discussion regarding the negative effects of game design elements. In order to facilitate discussions, we have semantically grouped the game design elements by section as follow: (A) Badges and Rewards; (B) Competitions, Challenges, and Goals; (C) Leaderboards and Rankings; (D) Points, XPs, and Virtual Currencies; Feedback and Achievements; (E) Avatars; and (F) Quizzes. Finally, Section G aimed at driving the discussion and capturing the level of agreement on the usefulness, ease to use, and intention to use the information on potential negative effects of game design elements. Figure 8 illustrates the template that we have defined for each aforementioned section. A section is composed of four parts (1, 2, 3, and 4). Part 1 contains a short description of the involved game design elements and the identified negative effects based on the literature. Part 2 is designed for capturing votes on the awareness degree concern the negative effects based on a four-point scale: completely unaware, mostly unaware, mostly aware, and completely aware. Finally, parts 3 and 4 were designed for participants to add notes on the Pros and Cons of using the game design elements, respectively. Phase 2: Discussion by game design elements – This phase consists in collecting data regarding the developer’s perception of the negative effects identified in the literature. As aforementioned, we have divide the game design elements in groups to facilitate the discussions and used a Mural discussion canvas. Thus, each group of game design elements is discussed in isolation. We Phase 2: Discussion by game design elements defined three steps as follows. Step 1 aimed at introducing each group of game design elements, and the negative effects. For this purpose, the moderator of the session read this information out loud (part 1 of Figure 8). Next, in Step 2 , we asked each participant to assign one vote to the awareness degree of the group of game design elements according to the four-point scale depicted in part 2 of Figure 8. Each participant voted individually, without knowing the votes of his colleagues. At the end, the moderator showed the number of votes per awareness agree. Finally, in Step 3 , we asked the participants to discuss and elicit Pros and Cons of using the game design elements. In this step, each comment should be documented as a note in the appropriate part: part 3 for positive comments and part 4 for negative ones, as shown in Figure 8. The note was just a brief summary of a Pro or a Con, typically taken within seconds, and we constantly asked participants to share knowledge and experiences surrounding the use of each game design element, to enrich the discussions and understandings. Additionally, whenever the moderator felt that a note is poorly written, he asked the participants to provide further considerations on the note. Step 1 Step 2 Step 3 Phase 3: Discussion about the perception of the mapped negative effects – After discussing all groups of game design elements, the focus group session ended with a final discussion about the perceptions regarding the mapped negative effects. This phase has two steps described as follows. In Step 1 , based on the main constructs of the Technology Acceptance Model (TAM) [113], we asked each participant to assign one vote to their agreement with each of the following statements (as illustrated in Section G of Figure 7): (1) I find the information on potential negative effects of game design elements useful to support game design element adoption decisions; (2) I find the information on potential negative effects of game design element easy to use to support game design element adoption decisions; and (3) I intend to use the information on potential negative effects of game design element to support game design element adoption decisions. We have used the five-point scale depicted in Figure 7 (G). Finally, Step 2 aimed at collecting data about the participant’s experience with the focus group session. Thus, by the end of the focus group session, we asked participants to fill out a Follow-up Form. We aimed at assuring that each developer felt confident and comfortable to discuss the negative effect of game design elements. Phase 3: Discussion about the perception of the mapped negative effects Step 1 Step 2 We emphasize that the focus group session was conducted online via a Zoom Meeting. Additionally, we kept video and audio records of the session to support the data analysis. We often accessed the video and audio records for understanding what developers meant with each note. The focus group session was conducted in January 24, 2022 lasting one and a half hours. This paper is available on arxiv under CC BY 4.0 DEED license. This paper is available on arxiv under CC BY 4.0 DEED license. available on arxiv [2] https://www.mural.co/

Focus Group Insights on Game Design Elements

What to Watch for: 5 Must-Have Elements in Crypto Whitepapers

Kunas uñjañasa: 5 Elementos Must-Have en Cripto Janq’u qillqatanaka

За какво да внимавате: 5 задължителни елемента в крипто белите книги

Na šta treba obratiti pažnju: 5 obaveznih elemenata u kripto bijelim papirima

Worauf Sie achten sollten: 5 unverzichtbare Elemente in Krypto-Whitepapers

Qué tener en cuenta: 5 elementos imprescindibles en los documentos técnicos sobre criptomonedas

Zer ikusi: 5 elementu ezinbestekoak Crypto Whitepapers

O que hai que ter en conta: 5 elementos imprescindibles nos documentos brancos de cripto

למה לצפות: 5 אלמנטים חובה במסמכי קריפטו

注目すべき点: 暗号通貨のホワイトペーパーに必須の 5 つの要素

Kam jāpievērš uzmanība: 5 obligātie elementi kriptogrāfijās

สิ่งที่ต้องจับตามอง: 5 องค์ประกอบที่ต้องมีใน Crypto Whitepapers

Nämä tomaşa etmeli: Kripto sahypalarynda 5 element bolmaly

If you’ve been writing Go code for a while, you’ve probably come across range loops. They’re elegant, concise, and incredibly handy for iterating over slices, maps, and channels. But did you know that their behavior can sometimes be counterintuitive, leading to subtle bugs in your code? In this article, I’ll break down the mechanics of range loops, explain why these quirks occur, and share actionable tips to avoid common pitfalls. By the end, you’ll have a deeper understanding of Go and be better equipped to write reliable, bug-free code. 🚀 What Makes Range Loops Tricky? At first glance, range loops in Go appear straightforward. Here’s an example you’ve likely seen: codenumbers := []int{1, 2, 3, 4, 5}  
for index, value := range numbers {  
    fmt.Printf("Index: %d, Value: %d\n", index, value)  
} This prints the index and value for each element in the slice. Simple, right? But here’s where things get interesting (and potentially frustrating). The Underlying Mechanics of Range When you use range, Go creates a copy of the value you’re iterating over. For slices, this means you’re not directly accessing the elements but working with their copies. This subtle detail can lead to unexpected behavior. Take this example: codewords := []string{"Go", "is", "awesome"}  
wordPointers := []*string{}  

for _, word := range words {  
    wordPointers = append(wordPointers, &word)  
}  

for _, pointer := range wordPointers {  
    fmt.Println(*pointer)  
} You might expect this to print: Go  
is  
awesome But instead, you’ll see: awesome  
awesome  
awesome Why? Because word is a single variable reused in every iteration. The loop appends the same variable’s address each time, and by the end of the loop, word holds the value of the last element. Avoiding Common Pitfalls Here are some tips to keep your range loops bug-free: Understand Copying Behavior:If you’re modifying elements, remember thatrange loops work with copies for slices and arrays. Use index-based access if you need to modify the original elements.
for i := range numbers {  
    numbers[i] *= 2  
}  




Be Cautious with Pointers:If you need to capture references to elements, use the index instead of the loop variable.
for i := range words {  
    wordPointers = append(wordPointers, &words[i])  
}  




Debug Complex Loops:Usefmt.Printf to inspect variables and their memory addresses. This helps identify if you’re unintentionally working with shared references. Why This Matters Understanding these quirks isn’t just about avoiding bugs—it’s about mastering Go. As you tackle more complex projects, these small details can have significant impacts on performance, correctness, and maintainability. This article is part of a series I’m writing to explore common mistakes in Go programming. The first topic, range loops, is something many developers encounter but don’t fully understand until they’ve run into a bug. Final Thoughts Range loops are one of Go’s most powerful tools, but like any tool, they come with nuances. By understanding how they evaluate and iterate over elements, you can write cleaner, more reliable code. If you’ve ever been bitten by a range loop bug—or have tips of your own—I’d love to hear from you! Let’s share knowledge and grow as a community. 🔗 Read the full article on my LinkedIn For more insights like this, follow my journey in exploring the intricacies of Go programming. 🚀 If you’ve been writing Go code for a while, you’ve probably come across range loops. They’re elegant, concise, and incredibly handy for iterating over slices, maps, and channels. But did you know that their behavior can sometimes be counterintuitive, leading to subtle bugs in your code? range In this article, I’ll break down the mechanics of range loops, explain why these quirks occur, and share actionable tips to avoid common pitfalls. By the end, you’ll have a deeper understanding of Go and be better equipped to write reliable, bug-free code. 🚀 range What Makes Range Loops Tricky? What Makes Range At first glance, range loops in Go appear straightforward. Here’s an example you’ve likely seen: range codenumbers := []int{1, 2, 3, 4, 5}  
for index, value := range numbers {  
    fmt.Printf("Index: %d, Value: %d\n", index, value)  
} codenumbers := []int{1, 2, 3, 4, 5}  
for index, value := range numbers {  
    fmt.Printf("Index: %d, Value: %d\n", index, value)  
} This prints the index and value for each element in the slice. Simple, right? But here’s where things get interesting (and potentially frustrating). The Underlying Mechanics of Range The Underlying Mechanics of Range When you use range , Go creates a copy of the value you’re iterating over. For slices, this means you’re not directly accessing the elements but working with their copies. This subtle detail can lead to unexpected behavior. range Take this example: codewords := []string{"Go", "is", "awesome"}  
wordPointers := []*string{}  

for _, word := range words {  
    wordPointers = append(wordPointers, &word)  
}  

for _, pointer := range wordPointers {  
    fmt.Println(*pointer)  
} codewords := []string{"Go", "is", "awesome"}  
wordPointers := []*string{}  

for _, word := range words {  
    wordPointers = append(wordPointers, &word)  
}  

for _, pointer := range wordPointers {  
    fmt.Println(*pointer)  
} You might expect this to print: Go  
is  
awesome Go  
is  
awesome But instead, you’ll see: awesome  
awesome  
awesome awesome  
awesome  
awesome Why? Because word is a single variable reused in every iteration. The loop appends the same variable’s address each time, and by the end of the loop, word holds the value of the last element. word word Avoiding Common Pitfalls Avoiding Common Pitfalls Here are some tips to keep your range loops bug-free: range Understand Copying Behavior:If you’re modifying elements, remember thatrange loops work with copies for slices and arrays. Use index-based access if you need to modify the original elements.
for i := range numbers {  
    numbers[i] *= 2  
} Be Cautious with Pointers:If you need to capture references to elements, use the index instead of the loop variable.
for i := range words {  
    wordPointers = append(wordPointers, &words[i])  
} Debug Complex Loops:Usefmt.Printf to inspect variables and their memory addresses. This helps identify if you’re unintentionally working with shared references. Understand Copying Behavior:If you’re modifying elements, remember thatrange loops work with copies for slices and arrays. Use index-based access if you need to modify the original elements. for i := range numbers {  
    numbers[i] *= 2  
} Understand Copying Behavior : If you’re modifying elements, remember that range loops work with copies for slices and arrays. Use index-based access if you need to modify the original elements. Understand Copying Behavior range for i := range numbers {  
    numbers[i] *= 2  
} for i := range numbers {  
    numbers[i] *= 2  
} Be Cautious with Pointers:If you need to capture references to elements, use the index instead of the loop variable. for i := range words {  
    wordPointers = append(wordPointers, &words[i])  
} Be Cautious with Pointers : If you need to capture references to elements, use the index instead of the loop variable. Be Cautious with Pointers for i := range words {  
    wordPointers = append(wordPointers, &words[i])  
} for i := range words {  
    wordPointers = append(wordPointers, &words[i])  
} Debug Complex Loops:Usefmt.Printf to inspect variables and their memory addresses. This helps identify if you’re unintentionally working with shared references. Debug Complex Loops : Use fmt.Printf to inspect variables and their memory addresses. This helps identify if you’re unintentionally working with shared references. Debug Complex Loops fmt.Printf Why This Matters Why This Matters Understanding these quirks isn’t just about avoiding bugs—it’s about mastering Go. As you tackle more complex projects, these small details can have significant impacts on performance, correctness, and maintainability. This article is part of a series I’m writing to explore common mistakes in Go programming. The first topic, range loops, is something many developers encounter but don’t fully understand until they’ve run into a bug. range Final Thoughts Final Thoughts Range loops are one of Go’s most powerful tools, but like any tool, they come with nuances. By understanding how they evaluate and iterate over elements, you can write cleaner, more reliable code. Range If you’ve ever been bitten by a range loop bug—or have tips of your own—I’d love to hear from you! Let’s share knowledge and grow as a community. range 🔗 Read the full article on my LinkedIn Read the full article on my LinkedIn For more insights like this, follow my journey in exploring the intricacies of Go programming. 🚀

Unlock the Secrets of Range Loops: How Element Evaluation Affects Your Go Code

Recently came an interesting task, changing custom SVG, to a Webflow project for the animation. I thought it was no big deal, opened a Figma, took the source code of the SVG, threw it in and .... didn't work 😔 Researching the problem, it turned out that the library that animates SVG works directly with rect elements inside the same SVG. Well again no problem I thought :), let's just rename all layers to Rect and we'll be happy. Renamed, I looked at the SVG source code and I don't see rect :( Then, I sat down much more comfortably in my chair and started researching more efficiently. It turned out that for SVG to understand the elements we want to animate as recr we need to draw them.... drum roll - through Frames. Started testing, and everything works. But now there is another problem: How to automate this process? We already have a lot of drawn illustrations, and we don't want to redo them. Well, since we are working in Frames, we have found a way out, need to create the plugin that will wrap all elements in frames. The source code of the Plugin: const selectedNodes = figma.currentPage.selection;

if (selectedNodes.length === 0) {
  figma.notify("Please select at least one layer.");
} else {
  selectedNodes.forEach(node => {
    const frame = figma.createFrame();
    frame.resize(node.width, node.height);
    frame.x = node.x;
    frame.y = node.y;
    frame.appendChild(node);
    node.x = 0;
    node.y = 0;
  });

  figma.notify("All selected layers are wrapped in frames!");
}

figma.closePlugin(); or download the project on GitHub :-) Result: 30 minutes of code and all animations work, work for the future is done. Conclusion: if you can't find interesting tasks, they will find you themselves. Automate everything :) Recently came an interesting task, changing custom SVG, to a Webflow project for the animation. I thought it was no big deal, opened a Figma, took the source code of the SVG, threw it in and .... didn't work 😔 didn't work didn't work Researching the problem, it turned out that the library that animates SVG works directly with rect elements inside the same SVG. Well again no problem I thought :), let's just rename all layers to Rect and we'll be happy. rect Renamed, I looked at the SVG source code and I don't see rect :( rect Then, I sat down much more comfortably in my chair and started researching more efficiently. It turned out that for SVG to understand the elements we want to animate as recr we need to draw them.... drum roll - through Frames. recr Started testing, and everything works. But now there is another problem: How to automate this process? How to automate this process? We already have a lot of drawn illustrations, and we don't want to redo them. Well, since we are working in Frames, we have found a way out, need to create the plugin that will wrap all elements in frames. plugin The source code of the Plugin: const selectedNodes = figma.currentPage.selection;

if (selectedNodes.length === 0) {
  figma.notify("Please select at least one layer.");
} else {
  selectedNodes.forEach(node => {
    const frame = figma.createFrame();
    frame.resize(node.width, node.height);
    frame.x = node.x;
    frame.y = node.y;
    frame.appendChild(node);
    node.x = 0;
    node.y = 0;
  });

  figma.notify("All selected layers are wrapped in frames!");
}

figma.closePlugin(); const selectedNodes = figma.currentPage.selection;

if (selectedNodes.length === 0) {
  figma.notify("Please select at least one layer.");
} else {
  selectedNodes.forEach(node => {
    const frame = figma.createFrame();
    frame.resize(node.width, node.height);
    frame.x = node.x;
    frame.y = node.y;
    frame.appendChild(node);
    node.x = 0;
    node.y = 0;
  });

  figma.notify("All selected layers are wrapped in frames!");
}

figma.closePlugin(); or download the project on GitHub :-) GitHub Result: 30 minutes of code and all animations work, work for the future is done. Conclusion: if you can't find interesting tasks, they will find you themselves. Automate everything :)

Tutorial: How to Turn Figma Files to SVG with Rect Elements

Падручнік: як ператварыць файлы Figma у SVG з элементамі Rect

Урок: Как да превърнете Figma файлове в SVG с Rect елементи

Tutorial: Cómo convertir archivos Figma a SVG con elementos Rect

آموزش: نحوه تبدیل فایل های Figma به SVG با عناصر Rect

Tutorial: Ki jan yo vire fichye Figma nan SVG ak eleman Rect

Tutorial: come trasformare i file Figma in SVG con elementi Rect

מדריך: כיצד להפוך קבצי Figma ל-SVG עם רכיבי Rect

チュートリアル: Figma ファイルを Rect 要素付きの SVG に変換する方法

Упатство: Како да ги претворите Figma-датотеките во SVG со Rect Elements

Samouczek: Jak przekształcić pliki Figma do formatu SVG za pomocą elementów Rect

Tutorial: Si t'i ktheni skedarët Figma në SVG me Elemente Rect

Qo'llanma: Figma fayllarini to'g'ri elementlar bilan SVGga qanday aylantirish mumkin

How to Convert Videos to HLS for Web & Mobile Streaming With AWS Elemental MediaConvert

Πώς να μετατρέψετε βίντεο σε HLS για ροή ιστού και κινητών με το AWS Elemental MediaConvert

Cómo convertir vídeos a HLS para transmisión web y móvil con AWS Elemental MediaConvert

Videoiden muuntaminen HLS:ksi verkko- ja mobiilisuoratoistoa varten AWS Elemental MediaConvertin avulla

AWS Elemental MediaConvert を使用してビデオを HLS に変換し、ウェブおよびモバイルストリーミングに配信する方法

Kā konvertēt videoklipus uz HLS straumēšanai tīmeklī un mobilajās ierīcēs, izmantojot AWS Elemental MediaConvert

AWS Elemental MediaConvert ашиглан вэб болон гар утасны урсгалд зориулсан видеог хэрхэн HLS болгон хөрвүүлэх вэ

Hoe u video's naar HLS kunt converteren voor web- en mobiele streaming met AWS Elemental MediaConvert

Maitiro ekushandura Vhidhiyo kuita HLS yeWebhu & Nhare Kutenderera NeAWS Elemental MediaConvert

AWS எலிமெண்டல் மீடியா கன்வெர்ட் மூலம் இணையம் மற்றும் மொபைல் ஸ்ட்ரீமிங்கிற்கான வீடியோக்களை HLS ஆக மாற்றுவது எப்படி

Paano Mag-convert ng Mga Video sa HLS para sa Web at Mobile Streaming Gamit ang AWS Elemental MediaConvert

AWS Elemental MediaConvert ile Web ve Mobil Yayın için Videoları HLS'ye Nasıl Dönüştürebilirsiniz

Як конвертувати відео в HLS для потокового передавання через Інтернет і мобільні пристрої за допомогою AWS Elemental MediaConvert

Identity Lifecycle Management (ILM), is a crucial component of enterprise Identity and Access Management (IAM) architecture, it also sometimes referred to as joiner-mover-leaver process. The goal of ILM is to minimize security risks by avoiding over-provisioning and under-provisioning of access rights. This is more important for companies that heavily depend on third party (3p) SaaS applications and allows personal devices (concept known as bring your own devices or BYOD) to access them. If provisioning access takes too long, the productivity of the employee is impacted, and if deprovisioning of access also takes too long, damage beyond repair can be done by the same employee knowingly or not. This article explains why Single Sign On (SSO) cannot solve all of it, and provides details about a companion, System for Cross-domain Identity Management (SCIM) to complete the picture. Identity Lifecycle Management To build a robust ILM system, various departments within the company work together, starting with Human Resources (HR). Onboarding of an employee starts with HR, then supported by the Information Security team until the employee's termination via a set of tools and procedures. Companies, irrespective of size, establish processes to hire, manage internal transfers and terminate employees. These vary from one to another based on size, from entirely manual and ticketing steps to automated workflows. At smaller to medium sized companies, processes involve direct interaction between teams, one informs another about a new hire, requests hardware and network credentials, and similarly notifies when an account should be removed upon termination. Larger companies with dedicated technology teams, ILM process is typically semi or fully automated. They are often supported by HR IT onboarding systems that create accounts, trigger notifications for hardware and credential creation, and support termination, access revocation through similar systems. Single Sign On We enforce Single Sign On (SSO), it will take care of automating access to applications, correct? Wrong. SSO is an important piece of the IAM ecosystem, but it alone does not automate access management. It is much evident during employee offboarding without a stronger ILM process to complement SSO. Many that work in technology, particularly those that are not familiar with all the ins and outs of IAM processes, assume that SSO automatically handles access revocation when an employee leaves. However, the effectiveness of SSO in this context depends on several factors. Companies with strict SSO policies prohibiting access to applications from non-employer-managed devices and can immediately disable access upon employment termination may have better control. If the company allows BYOD, revoking access becomes more challenging without an automated mechanism. In cases where SaaS applications create their own user sessions and do not frequently verify the state with an SSO provider (through OAuth refresh tokens for example), will continue to honor the session. Some third-party SaaS applications also offer SSO bypass ability, allowing users to log in with application-specific credentials, circumventing SSO-based controls. Welcome to SCIM For comprehensive access management, especially in environments supporting BYOD model, automated access revocation processes are critical. SCIM, or System for Cross-domain Identity Management, is a standard designed to manage user identity information across multiple domains and applications, cloud or otherwise. SCIM's design and development are guided by several RFCs, including 7643, 7644, and 7642. SCIM 2.0, the latest version of the protocol supports more attributes, operations and strict security requirements such as mandatory TLS 1.2. SCIM automates the process of approving and revoking user accounts in applications that support the protocol no matter where they are deployed. By using standardized protocols like REST and data formats such as JSON, SCIM enables seamless and secure communication of identity data between both identity (IdP) and service providers (SP). This reduces the burden on IT departments, minimizes human errors, and enhances security by ensuring that access is promptly updated or revoked as needed. Getting into technical details, SCIM supports two important endpoints: /users and /groups. Users endpoint is used for managing users and attributes such as email via various operations (create, patch, delete, etc.,). Groups allow membership updates which can be used for authorization policies on the SP. Customers can create integration to these endpoints with their entitlement management systems (e.g., an IdP managed group membership) and sync the changes automatically. This not only helps with deprovisioning of users when they leave but also helps with internal role changes. Most of the Identity as a Service (IDaaS) solutions available on the market support SSO and SCIM as part of the same application setup process making it easy to implement. Conclusion Per one of the well-known IDaaS with largest collection of SaaS integrations that I am aware of, less than 25% of the apps that support SSO via SAML and OIDC also support SCIM. I would like to conclude this article with requests to SPs and enterprise IAM teams to increase SCIM adoption. SPs should go beyond SSO and must consider supporting SCIM as part of their product (free of charge!) for their customers. IAM teams must enable SCIM for existing SPs if supported and push the remaining to support. Opinions expressed in this article are solely the Author's own and do not express the views or opinions of the Author's employer. Identity Lifecycle Management (ILM), is a crucial component of enterprise Identity and Access Management (IAM) architecture, it also sometimes referred to as joiner-mover-leaver process. The goal of ILM is to minimize security risks by avoiding over-provisioning and under-provisioning of access rights. This is more important for companies that heavily depend on third party (3p) SaaS applications and allows personal devices (concept known as bring your own devices or BYOD) to access them. If provisioning access takes too long, the productivity of the employee is impacted, and if deprovisioning of access also takes too long, damage beyond repair can be done by the same employee knowingly or not. This article explains why Single Sign On (SSO) cannot solve all of it, and provides details about a companion, System for Cross-domain Identity Management (SCIM) to complete the picture. Identity Lifecycle Management To build a robust ILM system, various departments within the company work together, starting with Human Resources (HR). Onboarding of an employee starts with HR, then supported by the Information Security team until the employee's termination via a set of tools and procedures. Companies, irrespective of size, establish processes to hire, manage internal transfers and terminate employees. These vary from one to another based on size, from entirely manual and ticketing steps to automated workflows. At smaller to medium sized companies, processes involve direct interaction between teams, one informs another about a new hire, requests hardware and network credentials, and similarly notifies when an account should be removed upon termination. Larger companies with dedicated technology teams, ILM process is typically semi or fully automated. They are often supported by HR IT onboarding systems that create accounts, trigger notifications for hardware and credential creation, and support termination, access revocation through similar systems. Single Sign On We enforce Single Sign On (SSO), it will take care of automating access to applications, correct? Wrong. SSO is an important piece of the IAM ecosystem, but it alone does not automate access management. It is much evident during employee offboarding without a stronger ILM process to complement SSO. Many that work in technology, particularly those that are not familiar with all the ins and outs of IAM processes, assume that SSO automatically handles access revocation when an employee leaves. However, the effectiveness of SSO in this context depends on several factors. Companies with strict SSO policies prohibiting access to applications from non-employer-managed devices and can immediately disable access upon employment termination may have better control. If the company allows BYOD, revoking access becomes more challenging without an automated mechanism. In cases where SaaS applications create their own user sessions and do not frequently verify the state with an SSO provider (through OAuth refresh tokens for example), will continue to honor the session. Some third-party SaaS applications also offer SSO bypass ability, allowing users to log in with application-specific credentials, circumventing SSO-based controls. Welcome to SCIM For comprehensive access management, especially in environments supporting BYOD model, automated access revocation processes are critical. SCIM, or System for Cross-domain Identity Management, is a standard designed to manage user identity information across multiple domains and applications, cloud or otherwise. SCIM's design and development are guided by several RFCs, including 7643, 7644, and 7642. SCIM 2.0, the latest version of the protocol supports more attributes, operations and strict security requirements such as mandatory TLS 1.2. SCIM automates the process of approving and revoking user accounts in applications that support the protocol no matter where they are deployed. By using standardized protocols like REST and data formats such as JSON, SCIM enables seamless and secure communication of identity data between both identity (IdP) and service providers (SP). This reduces the burden on IT departments, minimizes human errors, and enhances security by ensuring that access is promptly updated or revoked as needed. Getting into technical details, SCIM supports two important endpoints: /users and /groups. Users endpoint is used for managing users and attributes such as email via various operations (create, patch, delete, etc.,). Groups allow membership updates which can be used for authorization policies on the SP. Customers can create integration to these endpoints with their entitlement management systems (e.g., an IdP managed group membership) and sync the changes automatically. This not only helps with deprovisioning of users when they leave but also helps with internal role changes. Most of the Identity as a Service (IDaaS) solutions available on the market support SSO and SCIM as part of the same application setup process making it easy to implement. Conclusion Per one of the well-known IDaaS with largest collection of SaaS integrations that I am aware of, less than 25% of the apps that support SSO via SAML and OIDC also support SCIM. I would like to conclude this article with requests to SPs and enterprise IAM teams to increase SCIM adoption. SPs should go beyond SSO and must consider supporting SCIM as part of their product (free of charge!) for their customers. IAM teams must enable SCIM for existing SPs if supported and push the remaining to support. Opinions expressed in this article are solely the Author's own and do not express the views or opinions of the Author's employer. Opinions expressed in this article are solely the Author's own and do not express the views or opinions of the Author's employer.

SCIM: A Critical Yet Underappreciated Element in Enterprise IAM

Shared Element Transition in Jetpack Compose: A Guide

Comprehensive Guide to JavaScript Arrays: Adding, Removing, and Iterating Elements

The current decade will always remain etched in the annals of tech history for the unprecedented advent of artificial intelligence. It wouldn’t be farfetched to say that AI is making an indelible mark on almost every aspect of human life. Tech pundits and gurus are already predicting its far-reaching transformative effects and the occupations it will render obsolete. A potent question is whether the cybersecurity landscape is slated to incur ramifications from this onslaught. Is AI going to edge out humans, or is it likely to augment human roles? What do the industry trends tell us about it? The Ever-evolving World of Cyber Threats According to Forbes, the share impact of AI is likely to affect 15% of the global workforce. However, the Cybersecurity realm will remain immune to it because of a few key points. First is the ever-evolving nature of cyber threats. What was once considered a bane for cyber security specialists has become a blessing in disguise. AI models are adept at identifying threats and risks, but they depend on pattern feed, allowing them to pinpoint deviations. AI lacks the intuition and critical thinking to cope with anomalies falling outside the jurisdiction of the feed. In this particular scenario, AI would be incapable of formulating timely countermeasures, resulting in the compromise of organizational infrastructure. A human brain, on the other hand, is capable of rational thinking and contextual understanding, making it more adaptable, superior, and capable of interpreting previously unencountered threats and security lapses. It can also devise on-the-spot inventive measures to safeguard digital assets. After such an instance, the AI feed pattern will likely be updated with the latest information to improve and enhance its threat detection by a human engineer! Ethical and Legal Considerations Traversing ethical and legal considerations is still not the forte of artificial intelligence. When it comes to cybersecurity, these ethics and considerations become very convoluted with human behavior added to the mix. For instance, how can privacy violations of an individual’s data be curbed in a way that doesn’t infringe any rights? Regulation of surveillance and monitoring in a non-pervasive manner and, lastly, drawing a boundary between user responsibility and organizational security protocols. In broad-spectrum, AI can be taught to discern these factors but it can't substitute for human judgment and decisiveness to reach decisions that are majorly aligned with implemented standards and practices. Incident Response and Management Incident response and management capability of AI and ML algorithms have been a much-debated topic. Some proponents deem it indispensable, and some opponents are quick to point out various proverbial chinks in the armor. Though the autonomous response of cybersecurity-based AI systems operates on containment, remediation, and recovery, but again they rely on historical security and threat analysis data points. The delegation of tasks according to the criticality of threat level and undertaking adaptive strategies are better deployed when relying on the collective cognitive prowess of a human-led response team. Who is Protecting the Protector? Lastly, the AI system, which an organization might trust to shield itself, is prone to attacks. In the absence of human oversight and supervision, miscreants find inventive ways to manipulate the AI and achieve their nefarious objectives. This includes intentional and subtle data manipulation to hoodwink the AI. The technical moniker of this is “adversarial attacks”. Adversarial attacks dupe the AI into misclassifying or failing to detect a threat. Hackers might also keenly and zealously observe the AI model and record its behavior when given certain inputs. This allows them to deduce the model’s behavior, response time, and preventive measures and then develop ways to bypass it. Conclusion In conclusion, it is safe to assume that in the near future, AI will play a pivotal role in cybersecurity, but it still hasn’t attained the level of maturity, refinement, and dependability to circumvent the human element. Cybersecurity specialists will remain crucial for nurturing, training, and refining these systems for peak performance. The current decade will always remain etched in the annals of tech history for the unprecedented advent of artificial intelligence. It wouldn’t be farfetched to say that AI is making an indelible mark on almost every aspect of human life. Tech pundits and gurus are already predicting its far-reaching transformative effects and the occupations it will render obsolete. A potent question is whether the cybersecurity landscape is slated to incur ramifications from this onslaught. Is AI going to edge out humans, or is it likely to augment human roles? What do the industry trend s tell us about it? industry trend The Ever-evolving World of Cyber Threats According to Forbes, the share impact of AI is likely to affect 15% of the global workforce. However, the Cybersecurity realm will remain immune to it because of a few key points. First is the ever-evolving nature of cyber threats. What was once considered a bane for cyber security specialists has become a blessing in disguise. AI models are adept at identifying threats and risks, but they depend on pattern feed, allowing them to pinpoint deviations. Forbes , Forbes AI lacks the intuition and critical thinking to cope with anomalies falling outside the jurisdiction of the feed. In this particular scenario, AI would be incapable of formulating timely countermeasures, resulting in the compromise of organizational infrastructure. A human brain, on the other hand, is capable of rational thinking and contextual understanding, making it more adaptable, superior, and capable of interpreting previously unencountered threats and security lapses. It can also devise on-the-spot inventive measures to safeguard digital assets. After such an instance, the AI feed pattern will likely be updated with the latest information to improve and enhance its threat detection by a human engineer! Ethical and Legal Considerations Traversing ethical and legal considerations is still not the forte of artificial intelligence. When it comes to cybersecurity, these ethics and considerations become very convoluted with human behavior added to the mix. For instance, how can privacy violations of an individual’s data be curbed in a way that doesn’t infringe any rights? Regulation of surveillance and monitoring in a non-pervasive manner and, lastly, drawing a boundary between user responsibility and organizational security protocols. In broad-spectrum, AI can be taught to discern these factors but it can't substitute for human judgment and decisiveness to reach decisions that are majorly aligned with implemented standards and practices. Incident Response and Management Incident response and management capability of AI and ML algorithms have been a much-debated topic. Some proponents deem it indispensable, and some opponents are quick to point out various proverbial chinks in the armor. Though the autonomous response of cybersecurity-based AI systems operates on containment, remediation, and recovery, but again they rely on historical security and threat analysis data points. The delegation of tasks according to the criticality of threat level and undertaking adaptive strategies are better deployed when relying on the collective cognitive prowess of a human-led response team. cybersecurity-based AI systems cybersecurity-based AI systems Who is Protecting the Protector? Lastly, the AI system , which an organization might trust to shield itself, is prone to attacks. In the absence of human oversight and supervision, miscreants find inventive ways to manipulate the AI and achieve their nefarious objectives. This includes intentional and subtle data manipulation to hoodwink the AI. The technical moniker of this is “adversarial attacks”. the AI system the AI system Adversarial attacks dupe the AI into misclassifying or failing to detect a threat. Hackers might also keenly and zealously observe the AI model and record its behavior when given certain inputs. This allows them to deduce the model’s behavior, response time, and preventive measures and then develop ways to bypass it. Adversarial attacks Adversarial attacks Conclusion In conclusion, it is safe to assume that in the near future, AI will play a pivotal role in cybersecurity, but it still hasn’t attained the level of maturity, refinement, and dependability to circumvent the human element. Cybersecurity specialists will remain crucial for nurturing, training, and refining these systems for peak performance.

The Persistent Human Element in the Future of Cybersecurity

Authors:
(1) Fabiano Villan, Universidade Luterana do Brasil (ULBRA), Curso de Licenciatura em Física;
(2) Renato P. dos Santos, Universidade Luterana do Brasil (ULBRA), PPG em Ensino de Ciências e Matemática (PPGECIM). Table of Links Abstract Introduction Theoretical Framework The ZPD and Chat GPT as a Co-Advisor in Scientific Guidance Methodology Results and Analysis Conclusions, Acknowledgements, Author's Contribution Statement, Data Availability Statement References APÊNDICE A APÊNDICE B ABSTRACT Background: In the contemporary educational landscape, technology has the power to drive innovative pedagogical practices. Overcoming the resistance of teachers and students to adopting new methods and technologies is a challenge that needs to be addressed. Objectives: To evaluate the effectiveness of ChatGPT as a co-advisor in research projects and its influence on the implementation of Project-Based Learning (PBL), as well as overcoming resistance to the use of new pedagogical methodologies. Design: An action-research methodology was employed, including unstructured interviews and the application of questionnaires via Google Forms. Setting and Participants: The research was conducted in an elementary school, involving 353 students and 16 teachers. Data Collection and Analysis: Data were gathered through observations and notes in meetings and interviews, complemented by electronic questionnaires, with quantitative and qualitative analyses performed via Microsoft Excel and Google Forms. Results: The introduction of ChatGPT as a pedagogical tool led to increased student engagement and decreased teacher resistance, reflected in recognition at local science fairs. Conclusion: The study confirmed the utility of ChatGPT in school research co-orientation, highlighting its role in facilitating PBL and promoting cultural changes in educational practice, with proactive school management identified as a catalysing element in adapting to educational innovations. Keywords: ChatGPT as Co-advisor, Scientific Initiation, Elementary School, Project-Based Learning, Action Research. This paper is available on arxiv under CC BY-NC-ND 4.0 DEED license. Authors: (1) Fabiano Villan, Universidade Luterana do Brasil (ULBRA), Curso de Licenciatura em Física; (2) Renato P. dos Santos, Universidade Luterana do Brasil (ULBRA), PPG em Ensino de Ciências e Matemática (PPGECIM). Authors: Authors: (1) Fabiano Villan, Universidade Luterana do Brasil (ULBRA), Curso de Licenciatura em Física; (2) Renato P. dos Santos, Universidade Luterana do Brasil (ULBRA), PPG em Ensino de Ciências e Matemática (PPGECIM). Table of Links Abstract Abstract Introduction Introduction Theoretical Framework Theoretical Framework The ZPD and Chat GPT as a Co-Advisor in Scientific Guidance The ZPD and Chat GPT as a Co-Advisor in Scientific Guidance Methodology Methodology Results and Analysis Results and Analysis Conclusions, Acknowledgements, Author's Contribution Statement, Data Availability Statement Conclusions, Acknowledgements, Author's Contribution Statement, Data Availability Statement References References APÊNDICE A APÊNDICE A APÊNDICE B APÊNDICE B ABSTRACT Background : In the contemporary educational landscape, technology has the power to drive innovative pedagogical practices. Overcoming the resistance of teachers and students to adopting new methods and technologies is a challenge that needs to be addressed. Objectives : To evaluate the effectiveness of ChatGPT as a co-advisor in research projects and its influence on the implementation of Project-Based Learning (PBL), as well as overcoming resistance to the use of new pedagogical methodologies. Design : An action-research methodology was employed, including unstructured interviews and the application of questionnaires via Google Forms. Setting and Participants : The research was conducted in an elementary school, involving 353 students and 16 teachers. Data Collection and Analysis : Data were gathered through observations and notes in meetings and interviews, complemented by electronic questionnaires, with quantitative and qualitative analyses performed via Microsoft Excel and Google Forms. Results : The introduction of ChatGPT as a pedagogical tool led to increased student engagement and decreased teacher resistance, reflected in recognition at local science fairs. Conclusion : The study confirmed the utility of ChatGPT in school research co-orientation, highlighting its role in facilitating PBL and promoting cultural changes in educational practice, with proactive school management identified as a catalysing element in adapting to educational innovations. Background Objectives Design Setting and Participants Data Collection and Analysis Results Conclusion Keywords : ChatGPT as Co-advisor, Scientific Initiation, Elementary School, Project-Based Learning, Action Research. Keywords This paper is available on arxiv under CC BY-NC-ND 4.0 DEED license. This paper is available on arxiv under CC BY-NC-ND 4.0 DEED license. available on arxiv

ChatGPT as Co-Advisor in Scientific Initiation: Action Research in Elementary Education

Authors:
(1) Philipp Straubinger, University of Passau, Passau, Germany;
(2) Gordon Fraser, University of Passau, Passau, Germany. Table of Links Abstract and Introduction
Gamification Elements of Gamekins
Intellij Plugin for Gamekins
Conclusions
Acknowledgement and References 2 GAMIFICATION ELEMENTS OF GAMEKINS 2.1 Challenges Gamekins offers a variety of different challenges, which are test and quality-oriented tasks for the developer to solve. There are currently eight different types of challenges available[2]: • Build Challenge: This challenge shows the developer that the build on the CI failed and has to be fixed. • Test Challenge: This generic challenge shows that the developer has to write a new test. • Class Coverage Challenge: This challenge tasks the developer to cover more lines in a specific class. • Method Coverage Challenge: This challenge focuses on improving the coverage of a specific method. • Line Coverage Challenge: This challenge assigns the developer an uncovered line that they have to cover. • Branch Coverage Challenge: This challenge focuses on the improvement of branch coverage of a covered line. • Mutation Challenge: This challenge tasks the developer to detect a mutant generated by PIT[3] by writing a new test. • Smell Challenge: This challenge focuses on the removal of code and test smell with the help of SonarLint[4]. 2.2 Quests Since the original inception as described in prior work [3, 4], the way quests are implemented has changed. Instead of having multiple challenges solved after each other, quests are now test- and qualityrelated tasks that involve making multiple quality improvements and interacting with gamification elements. It is therefore not bound to challenges anymore, but rather on improving different test and quality-related metrics. The following types of quests are available: • Add Tests Quest: This quest tasks the developer to add a specified number of tests to the existing test suite. • Cover Branches Quest: This quest focuses on covering an additional specified number of branches with new tests. • Cover Lines Quest: This quest focuses on covering an additional specified number of lines with new tests. • Receive Challenges Quest: This quest promotes interaction with other developers by receiving a challenge from another developer. • Send Challenges Quest: This quest promotes interaction with other developers by sending a challenge to them. • Solve Achievements Quest: This quest focuses on the completion of a new achievement. • Solve Challenges Quest: This quest tasks the developer to solve a specified number of new challenges of one type. • Solve Challenges Without Rejection Quest: This quest focuses on solving a specified number of challenges regardless of their types without rejecting one in between. 2.3 Achievements Developers are rewarded based on their testing accomplishments, encompassing various achievements of differing difficulty levels. These achievements range from simple tasks like adding a test to a project to more challenging objectives such as achieving 100% coverage. Certain achievements remain hidden until they are completed and are tied to individual actions, like the addition of new tests. Achievements are triggered when users commit to the project repository. There are two main types of achievements: individual achievements, which involve completing a specific number of challenges, and project-level achievements, which are linked to reaching a particular threshold within the project. This paper is available on arxiv under CC BY-SA 4.0 DEED license. [2] Detailed information can be found in prior work [3, 4] [3] https://pitest.org/ [4] https://www.sonarsource.com/products/sonarlint/ Authors: (1) Philipp Straubinger, University of Passau, Passau, Germany; (2) Gordon Fraser, University of Passau, Passau, Germany. Authors: Authors: (1) Philipp Straubinger, University of Passau, Passau, Germany; (2) Gordon Fraser, University of Passau, Passau, Germany. Table of Links Abstract and Introduction Gamification Elements of Gamekins Intellij Plugin for Gamekins Conclusions Acknowledgement and References Abstract and Introduction Abstract and Introduction Gamification Elements of Gamekins Gamification Elements of Gamekins Intellij Plugin for Gamekins Intellij Plugin for Gamekins Conclusions Conclusions Acknowledgement and References Acknowledgement and References 2 GAMIFICATION ELEMENTS OF GAMEKINS 2.1 Challenges Gamekins offers a variety of different challenges, which are test and quality-oriented tasks for the developer to solve. There are currently eight different types of challenges available[2]: • Build Challenge: This challenge shows the developer that the build on the CI failed and has to be fixed. • Test Challenge: This generic challenge shows that the developer has to write a new test. • Build Challenge: • Class Coverage Challenge: This challenge tasks the developer to cover more lines in a specific class. • Class Coverage Challenge: • Method Coverage Challenge: This challenge focuses on improving the coverage of a specific method. • Method Coverage Challenge: • Line Coverage Challenge: This challenge assigns the developer an uncovered line that they have to cover. • Line Coverage Challenge: • Branch Coverage Challenge: This challenge focuses on the improvement of branch coverage of a covered line. • Branch Coverage Challenge: • Mutation Challenge: This challenge tasks the developer to detect a mutant generated by PIT[3] by writing a new test. • Mutation Challenge: • Smell Challenge : This challenge focuses on the removal of code and test smell with the help of SonarLint[4]. • Smell Challenge 2.2 Quests Since the original inception as described in prior work [3, 4], the way quests are implemented has changed. Instead of having multiple challenges solved after each other, quests are now test- and qualityrelated tasks that involve making multiple quality improvements and interacting with gamification elements. It is therefore not bound to challenges anymore, but rather on improving different test and quality-related metrics. The following types of quests are available: • Add Tests Quest: This quest tasks the developer to add a specified number of tests to the existing test suite. • Add Tests Quest: • Cover Branches Quest: This quest focuses on covering an additional specified number of branches with new tests. • Cover Branches Quest: • Cover Lines Quest: This quest focuses on covering an additional specified number of lines with new tests. • Receive Challenges Quest: This quest promotes interaction with other developers by receiving a challenge from another developer. • Send Challenges Quest: This quest promotes interaction with other developers by sending a challenge to them. • Send Challenges Quest: • Solve Achievements Quest: This quest focuses on the completion of a new achievement. • Solve Achievements Quest: • Solve Challenges Quest: This quest tasks the developer to solve a specified number of new challenges of one type. • Solve Challenges Quest: • Solve Challenges Without Rejection Quest: This quest focuses on solving a specified number of challenges regardless of their types without rejecting one in between. • Solve Challenges Without Rejection Quest: 2.3 Achievements Developers are rewarded based on their testing accomplishments, encompassing various achievements of differing difficulty levels. These achievements range from simple tasks like adding a test to a project to more challenging objectives such as achieving 100% coverage. Certain achievements remain hidden until they are completed and are tied to individual actions, like the addition of new tests. Achievements are triggered when users commit to the project repository. There are two main types of achievements: individual achievements, which involve completing a specific number of challenges, and project-level achievements, which are linked to reaching a particular threshold within the project. This paper is available on arxiv under CC BY-SA 4.0 DEED license. This paper is available on arxiv under CC BY-SA 4.0 DEED license. available on arxiv [2] Detailed information can be found in prior work [3, 4] [3] https://pitest.org/ [4] https://www.sonarsource.com/products/sonarlint/

An IDE Plugin for Gamified Continuous Integration: Gamification Elements of Gamekins

We now have a new search element in HTML. It should be used when adding any sort of search functionality within a website or web app. Its purpose is to provide the proper semantics for search functionality within the browser. In this post, I’ll show you how to use it in a couple of common search scenarios. Ok, let’s get to it. https://youtu.be/gi1sAH7DZQw?embedable=true The need for the HTML search element With , it’s important to use the best tag for the job. We want the browser or assistive technology to be able to understand as much as it can about the context surrounding the portions of our applications. Search is no different. HTML There is a concept for what is known as landmark roles in the ARIA specification for HTML to help do this. They are: Banner Complementary Contentinfo Form Main Navigation Region Search All of these landmarks could be added implicitly using the proper HTML element, except for search, until the element was added in early 2023. And now, we have an element for this as well. So now that we have it, we need to understand when and how to use it. Let’s take a look at an example. How to Use the HTML Search Element With a Common Submittable Search Form Here, we have some pretty standard search form markup. <form action="./search/" role="search">
    <label for="search">Search Players</label>
    <input type="search" id="search" autocomplete="off" [(ngModel)]="searchText" placeholder="Search by entering a player name" />
    <button type="submit">Go</button>
</form> We have a form element with the proper ARIA landmark role attribute of search. Then we have the label for our search textbox, then the search textbox, and then the button that will submit our search query. This will post to some backend and then give us a filtered list to display below our search form. Well, in this case, where we have a button to submit the search, we simply need to wrap our form in the new search element. And after that, we can remove the role attribute since the search element will provide the same semantic meaning. <search>
    <form action="./search/">
        <label for="search">Search Players</label>
        <input type="search" id="search" autocomplete="off" [(ngModel)]="searchText" placeholder="Search by entering a player name" />
        <button type="submit">Search</button>
    </form>
</search> And that’s it; it’s just that easy. The ARIA Landmark Search Role vs. the HTML Search Element One important item to note here is that we are essentially replacing the ARIA role attribute with the new HTML search element. We could leave it as it was with the landmark role attribute and no search element instead, but the ARIA spec is clear on the fact that we should always use the element that provides the appropriate semantics when one exists. And in this case, the search element now exists, so we should use it instead of the role attribute. How to use the HTML search element with a more modern filterable search controlled with JavaScript So, we’ve seen a more traditional search configuration, but what about something more modern like a web app search where the search is implemented with JavaScript and no form is actually submitted for our query? Well, let’s take another look at our example. For this demo, it’s actually built using angular, so the search functionality can easily happen all right here within the client. I won’t get into the specifics of how we perform the search in angular since that would be a bit off-topic, but just know that’s what’s happening here. <form action="./search/">
    <label for="search">Search Players</label>
    <input type="search" id="search" autocomplete="off" [(ngModel)]="searchText" placeholder="Search by entering a player name" />
    <button type="submit">Search</button>
</form>

@for (player of players | filter: searchText; track player.name) {
    <app-player [player]="player"></app-player>
} @empty {
    <p>Sorry, we couldn't find any players with the name you entered</p>
} So, in this case, we actually want to wrap the results in the search element as well since it should be used to contain all of the search capabilities. In this case, we also no longer need a button because the search will be bound to the textbox value change. So, as we type, the results will be filtered without needing to hit the button. And, since we aren’t submitting the form and no longer have a submit button, we no longer need the form element either. <search>
  <label for="search">Search Players</label>
  <input type="search" id="search" autocomplete="off" [(ngModel)]="searchText" placeholder="Search by entering a player name" />

  @for (player of players | filter: searchText; track player.name) {
    <app-player [player]="player"></app-player>
  } @empty {
    <p>Sorry, we couldn't find any players with the name you entered</p>
  }
</search> And that’s it. As simple as that. When and Where the HTML Search Element Should be Used So now you should be able to add the search element where appropriate for the things you’re building. It’s also important to understand what types of search regions are appropriate to be placed within the search element. It should be used for any type of search or filtering functionality, really. Whether you’re adding search or filtering for a website or app, or a specific portion of a website or app, or even when searching externally to other sites or even the web as a whole. Equally important to note here that it is perfectly acceptable to have more than one search element within a website or app. Ok, so now you should be good to go to use the search element. Want to See It in Action? Check out the demo code and examples of these techniques in the stack blitz example below. If you have any questions or thoughts, don’t hesitate to leave a comment. https://stackblitz.com/edit/stackblitz-starters-yg18rq?embed=1&file=src%2Fapp.component.html&embedable=true Also published . here

Using The New HTML Search Element: Enhancing Semantics for Search Functionality 🔎

You can jump to any section of the National Aeronautics Science & Technology Priorities here. Definitions of Key Framework Elements The Grand Pathways Framework is constructed to be conscious of (and responsive to) the contextdependent nature of and the variety of actors that must work together to build resilient communities. The Grand Pathways Framework also identifies systemic factors that increase vulnerabilities in segments of a community and thereby reduce resilience overall, and seeks to highlight opportunities where science and technology can inform communities and support equity and resilience across societal dimensions. community Different communities have different responsibilities when it comes to building resilience. For example, Federal and Tribal governments may have more responsibility for policy and funding. State/Territory and local governments typically have greater focus on emergency response exercises and implementation. Individuals and families may take their own steps to plan and prepare. Nongovernmental organizations, academia, and private sector organizations often drive science and technology innovation. These roles, however, are fluid; local governments may create policy and both the Federal and Tribal governments, and private sector organizations certainly conduct exercises to evaluate their own resilience. These roles and responsibilities illustrate the requirements for specific actions at and across each level to build more resilient communities. The intent of the Grand Pathways Framework is to identify and advance resilience science and technology capabilities that are broader than the single-service capabilities. is the study, research, engaged scholarship, analysis, experimentation, innovation, coproduction of knowledge, and other activities and applications that contribute to society’s ability to anticipate, avoid, adapt to, withstand, and build back better from acute shocks and chronic stresses. This means that any ideal solution identified informs multiple societal dimensions and could be used in the context of multiple key functions and cross-cutting enablers. Resilience science and technology This was originally published in March 2023 on It has been broken-up into bite sized sections, each with unique headlines and AI-generated lead images, in line with the provisions of whitehouse.gov. Creative Commons 3.0.

Decoding Key Elements of the Grand Pathways Framework

On the 1st day of 2022, I took a giant leap into a new career. Against limitations, I secured a job by the 10th month. The key to my success? Goal setting. It was the first time I stepped into a new year with daylight clarity on what I wanted to achieve and a roadmap for achieving it. But guess what? I didn't realize this until last December when I was reflecting on how I spent 2023. Despite achieving some feats, seeing how I shot my arrows aimlessly made me know I would've done better if I had a goal. With 2024 in sight, goal setting became a no-brainer. To do this, I demystified my 2022 goal to find the elements that made it work. I also drew inspiration from some successful entrepreneurs. All of which I'm excited to share with you in this article. So, keep reading if, like me, you believe 2023 would've been better with a clearer focus, and you're ready to rewrite the narrative in 2024. 9 Elements of an Effective New Year Goal 1. Choose the Right Goal Choosing a goal is the first and fundamental step in goal setting. And so, deserves more thought than it often gets. This is because the wrong goal will collapse any hard work you build on it. Just as the Bible states, "If the foundations be destroyed, what shall the righteous do?". The telltale sign of a wrong goal is when you choose it based on necessity. Such goals stem from the "I can't be left out/I can't appear unserious" mindset. They're fueled by societal expectations rather than intrinsic motivation. As such, it will make it hard for you to stay resolute when the journey gets murky. The best way to choose a goal is based on—Needs. Because they emanate from genuine reason, which increases your likelihood of committing to them. 4 Steps to Choosing a New Year Goal Based on Needs: Identify your Most Crucial Needs (MCN) Step 1: If you already know what they are/it is, skip to the next step. Assign them a mark on a scale of 10 to identify the parts of your life you're performing the least. And prioritizing the ones with the most significant impact on your current stage in life. Choosing your MCN is important to ensure focus and optimum results. In 2022, my MCN was building a career that would give me creative expression and a high income. List out possible solutions to your crucial needs Step 2: If the solutions you already know don't seem good enough, research more. In my case, baking was the only solution I knew. I had to talk to someone who introduced me to skills like Google quality rating and content writing. Identify your Low-Hanging Solution (LHS) Step 3: Your LHS is the solution with the highest probability of meeting your needs using your existing resources (skill, money, people, energy, time). This involves choosing a solution not just based on its chance for success but also considering whether you have the resources to implement it. In my case, I went with content writing because it gave me the highest chance of creative expression and high income. For resources, I already had a basic knowledge in writing and I could commit the time needed to advance the skill. Note: If none of your listed solutions are low-hanging, be open-minded and do more research to discover better ideas. Define your goal Step 4: Match your most crucial need with your lowest-hanging solution to define your goal. Simply put: MCN + LHS = Goal My goal was—to gain creative expression and increase my income through content writing. 2. Assign Specific Timeframe The benefit of having a new year goal is that it gives you a natural start and end time. But that doesn't mean it must start on January 1st and run through the year. It's ok to know what you want to do and not be ready to start it till later in the year. Only ensure you set a specific start and end date to keep you accountable. When setting your end time, ensure it's neither overstretched nor too short and leave a margin of error. How do you leave a margin of error? Set a deadline earlier than the year's end to accommodate unforeseen situations. This increases your chance of achieving your goal before the year ends. For example, I set my 2024 goals to end in the 3rd quarter of the year. This way, I can handle spillovers in the last quarter. In the absence of any spillover, evaluate your goals and plan for the next year. 3. Set Specific Outcome The truth is that setting a specific outcome can be intimidating because it leaves you no choice but to succeed. But the flexibility of vague goals makes it hard to stay committed and focused, which increases the chance of failure. So, which do you choose? If you go with specificity, keep reading to learn how to set it. Renowned entrepreneur , recommends expressing clear outcomes in absolute numbers devoid of signs like - +>/ Vusi Thembekwayo This means you should be wary of expressions that make your goal appear vague and uncertain. Such expressions often appear as phrases like: Between X and Y I'm trying to I'd like to at least more Or Here are some examples of how to take your goals from vague and uncertain to specific and confident. ❌ I'd like to improve my presentation skills. ✅ I'll enhance my presentation skills by completing a public speaking course within the next two months. ❌ I plan to learn between 2 to 5 languages this year. ✅ I'll learn Spanish and Arabic by taking online language lessons 3x a week. ❌ Maintain at least a 90% customer satisfaction rate. ✅ Achieve a customer satisfaction rate of 90% by addressing feedback and implementing improvements. ❌ I want to visit more countries. ✅ I'll visit three new countries every two months starting in April to broaden my cultural experiences. Still need a reason to set specific outcomes? According to Vusi, it enables you to give a straightforward yes or no answer when evaluating the success of your goal. This makes it easy to know the next step to take. More about it in element 9 (goal evaluation). 4. Create an Action Plan If you know your destination but don't know the route that leads there, it’s certain you'll never get there. Your goal is the destination. Your action plan is the route to achieving it. To create an action plan, identify the elements you need to achieve the goal. These elements include resources, habits, milestones, contingency plans, and scheduling. If, for instance, you have the goal of reading 15 books in various genres over the next six months, an action plan example for you will be: A list of book names, highlighter, and jotter. Resources: Process: Find book recommendations on Amazon Buy them Read them Read 20 pages daily before going to bed, except on Sunday. Habit: Complete one book every month. Milestone: If I miss a day, I'll make it up the next day by reading 40 pages. Contingency plan: Block 1 hour before bedtime on my calendar. Scheduling: Note: Before creating an action plan, conduct adequate research to know what's achievable. For instance, in the example above, it's essential to check the total pages of your book to determine the daily reading target required to meet your deadline. 5. Make it Ambitious An ambitious goal stretches you beyond your limit and makes you feel more fulfilled. For instance, you usually save $50k annually, but this year, you decided to save $100k by streamlining your expenses. But, be careful not to mistake overambitious for ambitious goals. Over-ambitious goals are impossible to achieve. E.g. Aiming to become the CEO of a Fortune 500 company within one year of starting your career. OK. This clearly looks over-ambitious, but sometimes they're not that easy to recognize. This is why you need a framework to determine the ambitiousness of your goal. The framework requires you to answer these three questions: Do you need to step out of your comfort zone or establish limits to achieve it? Yes - ambitious No - under-ambitious Despite difficulties, do you have a clear roadmap for achieving it? Yes - ambitious No - overambitious Is the reward worth the risk? Yes - ambitious No - overambitious Kindly note that the effectiveness of this framework is reliant on how well you did your research and the sincerity of your answers. 6. Develop an Adaptable Mindset After setting my 2024 career goal, I discussed it with an expert who found faults in my process and offered suggestions. It was a hard pill to swallow initially because I believed in my process. But after two days of thinking through it, I became convinced that adhering to her advice was the best decision. This underscores the importance of approaching your goal with an adaptable mindset. Certain things could distort the direction of your goal, such as: Expert advice, like in my case Unforeseen situations during implementation. Government regulations Environmental factors like the COVID pandemic It may be difficult to change your original idea if you have an affinity for it, invested efforts/resources in it, or the process of changing it is challenging. To make a rational decision, Don't settle for the first choice that comes to your mind. Instead, ponder on it. Weigh the risk of sticking with your existing plan and the advantages of adjusting it. If it's advice, like in my case, consider the person's experience and understand the reason for their suggestion. Get the opinion of a third party. Check in with your intuition. Does adaptability negate the importance of setting a specific timeframe and outcome for your goal? No! They complement each other. While the latter helps you stay committed and focused, the former keeps you attuned to reality. 7. Define Your "Why" Two months into my content writing career, I felt trapped in muddy ground. I hadn’t made a dime. I was feeling intimidated by other people's work. My family thought I was wasting my time. But I remained steadfast, and this is because I had a “why,” which is this: Writing gives me the joy of seeing my ideas breathe life. And it has the highest chance of giving me the money I need to live the life I want and make a social impact. This thought kept me motivated. This is the power of having a “why.” It motivates you to keep going, especially when the journey gets tough. Like kinetic energy is required to set an object in motion and sustain it, your "why" gives you the intrinsic energy to kick start your goal and keep the momentum. What is your "why"? It's the strongest benefit of achieving your goal. Emphasis on the word "strongest" because the stronger it is, the more steadfast you’ll be. If you choose your goal based on need, it'll be easy for you to define your "why.” When you do, keep it handy (in your subconscious mind or writing) so that you can easily refer to it when it's needed. 8. Keep it in Sight Out of sight is out of mind, they say. If you can't see your goals, there's a high chance of forgetting them. This goes beyond writing them down but embracing systems that make it easy to remember them. Tools for Keeping Your Goals in Sight: Design vision boards and hang them on prominent walls in your office or bedroom to provide motivation and help you maintain focus. Block dates in your calendar to remember what you plan to do at certain times. Establish review rituals, e.g., dedicate a day of the week or month to evaluate your progress. Write on sticky notes and place them in prominent places, such as your workspace or mirror, to serve as reminders. Share with others like friends, family, or colleagues who can provide support and hold you accountable. Use goal-tracking apps like Goals Wizard, Hatch, and Goalify for easy access, keeping track of your progress, setting reminders, and enriching your evaluation with analytics insight. 9. Evaluate Your Goal In the last quarter of the year, ask yourself this question: Did I achieve my goal? If you set a precise outcome, you should be able to answer… Yes or No If your answer is No. Don't feel bad, especially if you did your best. Rather, identify the milestones you achieved and celebrate them. And go further to assess why you couldn't hit the intended outcome. Did you choose the wrong goal? Was it overambitious? Was your action plan flawed? Were you not adaptive? Were you lazy? Did you procrastinate? Did you lose motivation? Did you forget it? I understand that it could involve a more nuanced problem. The point is for you to probe your process thoroughly to uncover mistakes and draw insights to set better goals for the next year. But if you achieved your goal, bravo 👏👏 So… What Next? There are three things you can do: Set another goal: If, after reaching this new height, you feel unsatisfied and believe there's a better chance of achieving more if you keep the momentum, set another goal. Just so you know, this is why I should have set a goal for 2023. Focus on another bucket: You can pick another bucket of your life that needs some love and set a goal for it. Don't set a goal at all: I understand that continuous goal setting can feel like an unending rat race. It's the reason the start of this article encourages you not to set goals based on necessity but on needs. So, if you feel satisfied with your current state in life, there is no pressure. Live unbound 🕊️ And know that you can always set a goal within the year if you find a need to do so.

From Failed to Achieved: 9 Proven Elements For Setting New Year Goals

Stories, News & Mentions about ELEMENT

Element’s Stories on HackerNoon