The research on Real-Time Interaction Management Software Market Perspective, Comprehensive Analysis, and Major Segments and Forecast, 2023-2030. The Real-Time Interaction Management Software ...

Real-Time Interaction Management Software Market Size, Business Segments, Innovative Strategies and Outlook by 2030 with ACTITO, Certona, TIBCO

Marketing platforms software refers to a set of tools and technologies that enable businesses to plan, execute, and analyze their marketing campaigns across various channels and platforms.

Marketing Platforms Software Market Research Report Unlocks Analysis on the Market Financial Status, Market Size, and Market Revenue upto 2030

“Ella realmente no sigue estos temas si no hay un actito o algo que festejar. Entonces, estamos seguros de que ella no sabía nada hasta que no lo ha leído”, afirma. Así pues, el popular considera que “lo normal” hubiera sido que la máxima ...

Quevedo replica a Moh sobre el agua: «Ella no sigue estos temas si no hay un actito o algo que festejar»

In the insurance industry, establishing consumer trust is a significant challenge faced by every insurance agency. Surveys reveal alarmingly low levels of confidence, with only a mere 20% of ...

Building Trust in the Insurance Industry: The Power of Personalized and Automated Customer Relationships

In today's competitive business landscape, effectively managing leads is crucial for driving growth and maximizing conversion rates. Manual lead management processes can be time-consuming and ...

Streamlining Lead Management with Marketing Automation: Unlocking Growth Potential

Why Actito? 🚀 The Actito platform has been designed to help marketers easily capture, analyse and activate data to drive meaningful engagement between brand and customers.

🤔How to design your first-party data strategy 🤔

Qualifio se une al grupo escandinavo QNTM, reforzando su ecosistema europeo único en lo referente al MarTech. ¡Descubre más aquí!

Qualifio se une al grupo escandinavo QNTM

Esta adquisición, que se añade a las de Raptor en 2021 y de Actito en 2022, va a reforzar la oferta de QNTM en el ámbito del MarTech El grupo QNTM (QNTM Group) ha anunciado hoy la adquisición de una parte mayoritaria de Qualifio SA (Qualifio), la ...

The MarketWatch News Department was not involved in the creation of this content. May 02, 2023 (The Expresswire) -- Pre and Post Covid Report Is Covered | Final Report Will Add the Analysis of the ...

Marketing Platforms Software Market 2023 Size, Shares, and Future Forecasts to 2031

New Jersey, United States - The Marketing Platforms SoftwareMarket is the title of another report delivered by IBI. The

Marketing Platforms Software Market Likely to Enjoy Remarkable Growth with HubSpot, Constant Contact, Mailchimp, SAP

Actito

actito

Disclaimer: This post includes affiliate links; I may receive compensation if you purchase the book from the different links provided in this post. This review is about DuckDB in Action by JoMark Needham, Michael Hunger, and Michael Simons from Manning. The book was sent to me by Michael Simons. He asked for my feedback: I changed my reading schedule, took a few months, and here it is. Facts 10 chapters
288 pages
$33.59 (eBook) Note that MotherDuck, the company behind DuckDB, offers a free PDF copy. Chapters An introduction to DuckDB
Getting started with DuckDB
Executing SQL queries
Advanced aggregation and analysis of data
Exploring data without persistence
Integrating with the Python ecosystem
DuckDB in the cloud with MotherDuck
Building data pipelines with DuckDB
Building and deploying data apps
Performance considerations for large datasets
Conclusion The book takes a step-by-step approach, starting from the basics of DuckDB and SQL. Pros and Cons After the mandatory section about introducing DuckDB and installing it, the book explains SQL. At first, I admit I thought that the book was for newbies, as it explained things as simple as JOIN. However, the chapter afterwards explained Common Table Expressions and built complex queries upon them. I like how the authors describe DuckDB in its "natural environment", i.e., how it integrates into different ecosystems, such as Python's Pandas and Apache Spark. In addition, a complete appendix section focuses on DuckDB in Java. Finally, the authors dedicate a section to MotherDuck, a DuckDB cloud provider. Conclusion My thoughts on the book are a bit divided. On one side, it tries to explain DuckDB itself and its integration in different environments. On the other hand, it teaches regular and advanced SQL, which users of an SQL database product should know IMHO. The book can't decide between a Learn SQL with DuckDB approach and a DuckDB in Action one. The role of a book editor is to help authors make hard decisions. It feels as if this one didn't want to stop the authors' enthusiasm and couldn't bring themselves to rein them in. Don't get me wrong: the book is great and can teach you a lot, but it could have been better with more focus. Originally published on A Java Geek on November 2nd, 2024 Disclaimer: This post includes affiliate links; I may receive compensation if you purchase the book from the different links provided in this post. This review is about DuckDB in Action by JoMark Needham, Michael Hunger, and Michael Simons from Manning. DuckDB in Action The book was sent to me by Michael Simons . He asked for my feedback: I changed my reading schedule, took a few months, and here it is. Michael Simons Facts 10 chapters 288 pages $33.59 (eBook) 10 chapters 288 pages $33.59 (eBook) Note that MotherDuck, the company behind DuckDB, offers a free PDF copy . free PDF copy Chapters An introduction to DuckDB Getting started with DuckDB Executing SQL queries Advanced aggregation and analysis of data Exploring data without persistence Integrating with the Python ecosystem DuckDB in the cloud with MotherDuck Building data pipelines with DuckDB Building and deploying data apps Performance considerations for large datasets Conclusion An introduction to DuckDB Getting started with DuckDB Executing SQL queries Advanced aggregation and analysis of data Exploring data without persistence Integrating with the Python ecosystem DuckDB in the cloud with MotherDuck Building data pipelines with DuckDB Building and deploying data apps Performance considerations for large datasets Conclusion The book takes a step-by-step approach, starting from the basics of DuckDB and SQL. and Pros and Cons After the mandatory section about introducing DuckDB and installing it, the book explains SQL. At first, I admit I thought that the book was for newbies, as it explained things as simple as JOIN . However, the chapter afterwards explained Common Table Expressions and built complex queries upon them. JOIN I like how the authors describe DuckDB in its "natural environment", i.e. , how it integrates into different ecosystems, such as Python's Pandas and Apache Spark. In addition, a complete appendix section focuses on DuckDB in Java. Finally, the authors dedicate a section to MotherDuck, a DuckDB cloud provider. i.e. Conclusion My thoughts on the book are a bit divided. On one side, it tries to explain DuckDB itself and its integration in different environments. On the other hand, it teaches regular and advanced SQL, which users of an SQL database product should know IMHO. The book can't decide between a Learn SQL with DuckDB approach and a DuckDB in Action one. The role of a book editor is to help authors make hard decisions. It feels as if this one didn't want to stop the authors' enthusiasm and couldn't bring themselves to rein them in. Don't get me wrong: the book is great and can teach you a lot, but it could have been better with more focus. Originally published on A Java Geek on November 2nd, 2024 Originally published on A Java Geek on November 2nd, 2024 A Java Geek

DuckDB in Action: A Review

Orchestrating Airflow DAGs with GitHub Actions - A Lightweight Approach to Data Curation Across Spa

 A Deep Dive Into GitHub Actions From Software Development to Data Engineering

Setting up GitHub Actions to automate the publishing of Python packages to the Python Package Index (PyPI) involves creating a workflow that runs when you push changes to your repository. Here’s a step-by-step guide to help you integrate GitHub Actions with PyPI for your Python projects. Step 1: Prepare Your Python Package Ensure your Python package is ready for distribution. You should have the following files in your project directory: setup.py: This file contains metadata about your package.
pyproject.toml: This file is often used for specifying build dependencies.
Your package source code in a directory (e.g., my_package/). Here's a simple example of what your setup.py might look like: from setuptools import setup, find_packages

setup(
    name='my_package',
    version='0.1.0',
    packages=find_packages(),
    install_requires=[
        # List your package dependencies here
    ],
) Step 2: Create a PyPI Account If you haven’t already, create an account on PyPI. Once registered, you can create an API token for authentication. Log in to your PyPI account.
Go to your account settings and create a new API token.
Copy the generated token, as you will need it later. Step 3: Store the PyPI Token in GitHub Secrets To securely use your PyPI token in GitHub Actions, add it to your repository secrets: Go to your GitHub repository.
Click on Settings > Secrets and variables > Actions > New repository secret.
Name the secret PYPI_TOKEN and paste your PyPI API token in the value field. Step 4: Create the GitHub Actions Workflow Create a workflow file in your repository to define the steps for publishing to PyPI. Create a directory .github/workflows/.
Inside that directory, create a file named publish.yml. Here’s a sample publish.yml file: name: Publish to PyPI

on:
  push:
    tags:
      - 'v*'  # Trigger on version tags like v1.0.0

jobs:
  publish:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v2

      - name: Set up Python
        uses: actions/setup-python@v2
        with:
          python-version: '3.8'  # Specify your Python version

      - name: Install dependencies
        run: |
          python -m pip install --upgrade pip
          pip install setuptools wheel twine

      - name: Build package
        run: |
          python setup.py sdist bdist_wheel

      - name: Publish to PyPI
        env:
          TWINE_USERNAME: __token__  # Use the token authentication
          TWINE_PASSWORD: ${{ secrets.PYPI_TOKEN }}
        run: |
          twine upload dist/* Step 5: Create a Tag for the Release To trigger the workflow, you need to create a Git tag that matches the pattern defined in your workflow file (e.g., v1.0.0). You can do this using the following Git commands: git tag v1.0.0
git push origin v1.0.0 Step 6: Check GitHub Actions After pushing the tag, go to your GitHub repository and check the Actions tab. You should see the workflow running. If everything is set up correctly, it will build your package and publish it to PyPI. Conclusion By following these steps, you can successfully set up GitHub Actions to automate the process of publishing your Python development projects to PyPI. This integration not only streamlines your deployment process but also ensures that your package is consistently updated with the latest changes. Setting up GitHub Actions to automate the publishing of Python packages to the Python Package Index (PyPI) involves creating a workflow that runs when you push changes to your repository. Here’s a step-by-step guide to help you integrate GitHub Actions with PyPI for your Python projects. Step 1: Prepare Your Python Package Ensure your Python package is ready for distribution. You should have the following files in your project directory: setup.py: This file contains metadata about your package. pyproject.toml: This file is often used for specifying build dependencies. Your package source code in a directory (e.g., my_package/). setup.py : This file contains metadata about your package. setup.py pyproject.toml : This file is often used for specifying build dependencies. pyproject.toml Your package source code in a directory (e.g., my_package/ ). my_package/ Here's a simple example of what your setup.py might look like: setup.py from setuptools import setup, find_packages

setup(
    name='my_package',
    version='0.1.0',
    packages=find_packages(),
    install_requires=[
        # List your package dependencies here
    ],
) from setuptools import setup, find_packages

setup(
    name='my_package',
    version='0.1.0',
    packages=find_packages(),
    install_requires=[
        # List your package dependencies here
    ],
) Step 2: Create a PyPI Account If you haven’t already, create an account on PyPI . Once registered, you can create an API token for authentication. PyPI Log in to your PyPI account. Go to your account settings and create a new API token. Copy the generated token, as you will need it later. Log in to your PyPI account. Go to your account settings and create a new API token. Copy the generated token, as you will need it later. Step 3: Store the PyPI Token in GitHub Secrets To securely use your PyPI token in GitHub Actions, add it to your repository secrets: Go to your GitHub repository. Click on Settings > Secrets and variables > Actions > New repository secret. Name the secret PYPI_TOKEN and paste your PyPI API token in the value field. Go to your GitHub repository. Click on Settings > Secrets and variables > Actions > New repository secret . Settings Secrets and variables Actions New repository secret Name the secret PYPI_TOKEN and paste your PyPI API token in the value field. PYPI_TOKEN Step 4: Create the GitHub Actions Workflow Create a workflow file in your repository to define the steps for publishing to PyPI. Create a directory .github/workflows/. Inside that directory, create a file named publish.yml. Create a directory .github/workflows/ . .github/workflows/ Inside that directory, create a file named publish.yml . publish.yml Here’s a sample publish.yml file: publish.yml name: Publish to PyPI

on:
  push:
    tags:
      - 'v*'  # Trigger on version tags like v1.0.0

jobs:
  publish:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v2

      - name: Set up Python
        uses: actions/setup-python@v2
        with:
          python-version: '3.8'  # Specify your Python version

      - name: Install dependencies
        run: |
          python -m pip install --upgrade pip
          pip install setuptools wheel twine

      - name: Build package
        run: |
          python setup.py sdist bdist_wheel

      - name: Publish to PyPI
        env:
          TWINE_USERNAME: __token__  # Use the token authentication
          TWINE_PASSWORD: ${{ secrets.PYPI_TOKEN }}
        run: |
          twine upload dist/* name: Publish to PyPI

on:
  push:
    tags:
      - 'v*'  # Trigger on version tags like v1.0.0

jobs:
  publish:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v2

      - name: Set up Python
        uses: actions/setup-python@v2
        with:
          python-version: '3.8'  # Specify your Python version

      - name: Install dependencies
        run: |
          python -m pip install --upgrade pip
          pip install setuptools wheel twine

      - name: Build package
        run: |
          python setup.py sdist bdist_wheel

      - name: Publish to PyPI
        env:
          TWINE_USERNAME: __token__  # Use the token authentication
          TWINE_PASSWORD: ${{ secrets.PYPI_TOKEN }}
        run: |
          twine upload dist/* Step 5: Create a Tag for the Release To trigger the workflow, you need to create a Git tag that matches the pattern defined in your workflow file (e.g., v1.0.0 ). You can do this using the following Git commands: v1.0.0 git tag v1.0.0
git push origin v1.0.0 git tag v1.0.0
git push origin v1.0.0 Step 6: Check GitHub Actions After pushing the tag, go to your GitHub repository and check the Actions tab. You should see the workflow running. If everything is set up correctly, it will build your package and publish it to PyPI. Actions Conclusion By following these steps, you can successfully set up GitHub Actions to automate the process of publishing your Python development projects to PyPI. This integration not only streamlines your deployment process but also ensures that your package is consistently updated with the latest changes. Python development

Automate Python Package Publishing with GitHub Actions

Authors:
(1) Martin Kleppmann, University of Cambridge, Cambridge, UK (martin.kleppmann@cst.cam.ac.uk);
(2) Paul Frazee, Bluesky Social PBC United States;
(3) Jake Gold, Bluesky Social PBC United States;
(4) Jay Graber, Bluesky Social PBC United States;
(5) Daniel Holmgren, Bluesky Social PBC United States;
(6) Devin Ivy, Bluesky Social PBC United States;
(7) Jeromy Johnson, Bluesky Social PBC United States;
(8) Bryan Newbold, Bluesky Social PBC United States;
(9) Jaz Volpert, Bluesky Social PBC United States. Table of Links Abstract and 1 Introduction 2 The Bluesky Social App 2.1 Moderation Features 2.2 User Handles 2.3 Custom Feeds and Algorithmic Choice 3 The at Protocol Architecture 3.1 User Data Repositories 3.2 Personal Data Servers (PDS) 3.3 Indexing Infrastructure 3.4 Labelers and Feed Generators 3.5 User Identity 4 Related Work 5 Conclusions, Acknowledgments, and References 3.1 User Data Repositories All data that a user wishes to publish is added to their repository, which stores a collection of records. Whenever a user performs some action – making a post, liking another user’s post, following another user, etc. – that action becomes a record in their repository. Records are encoded in DAG-CBOR [45], a restricted form of CBOR [17], a compact binary data format. The schema of records is defined by the lexicon, and a repository may contain a mixture of records from several different lexicons, representing user actions in different social modes. Media files (e.g. images) are stored outside of the user’s repository, but referenced by their CID [32] (essentially a cryptographic hash) from a record in the repository. Similarly, a reference to a record in another repository (e.g. identifying a post being liked) also includes its CID. Each user account has one repository, and it contains all of the actions they have ever performed, minus any records they have explicitly deleted. A Personal Data Server (PDS) hosts the user’s repository and makes it publicly available as a web service; we discuss PDSes in more detail in Section 3.2. A user only updates their own repository; for example, if user 𝐴 follows user 𝐵, this results only in a follow record in user 𝐴’s repository, and no change to 𝐵’s repository. To find all followers of user 𝐵 requires indexing the content of all repositories. This design decision is similar to the way hyperlinks work on the web: it is easy to find all the outbound links from a web page at a given URL, but to find all the inbound links to a page requires an index of the entire web, which is maintained by web search engines. The AT in atproto stands for Authenticated Transfer, which reflects the fact that repositories are cryptographically authenticated. The records in a repository are organized into a Merkle Search Tree (MST), a type of Merkle tree that remains balanced, even as records are inserted or deleted in arbitrary order [3]. After every change to a repository, the root hash of the MST is signed; the public verification key for this signature is part of the user identity described in Section 3.5. This enables an efficient cryptographic proof that a given record appears within a given user’s repository. Moreover, when a user updates or deletes a record, the MST enables a proof that the old record no longer appears in the repository. This paper is available on arxiv under CC BY 4.0 DEED license. Authors: (1) Martin Kleppmann, University of Cambridge, Cambridge, UK (martin.kleppmann@cst.cam.ac.uk); (2) Paul Frazee, Bluesky Social PBC United States; (3) Jake Gold, Bluesky Social PBC United States; (4) Jay Graber, Bluesky Social PBC United States; (5) Daniel Holmgren, Bluesky Social PBC United States; (6) Devin Ivy, Bluesky Social PBC United States; (7) Jeromy Johnson, Bluesky Social PBC United States; (8) Bryan Newbold, Bluesky Social PBC United States; (9) Jaz Volpert, Bluesky Social PBC United States. Authors: Authors: (1) Martin Kleppmann, University of Cambridge, Cambridge, UK (martin.kleppmann@cst.cam.ac.uk); (2) Paul Frazee, Bluesky Social PBC United States; (3) Jake Gold, Bluesky Social PBC United States; (4) Jay Graber, Bluesky Social PBC United States; (5) Daniel Holmgren, Bluesky Social PBC United States; (6) Devin Ivy, Bluesky Social PBC United States; (7) Jeromy Johnson, Bluesky Social PBC United States; (8) Bryan Newbold, Bluesky Social PBC United States; (9) Jaz Volpert, Bluesky Social PBC United States. Table of Links Abstract and 1 Introduction Abstract and 1 Introduction 2 The Bluesky Social App 2 The Bluesky Social App 2.1 Moderation Features 2.1 Moderation Features 2.2 User Handles 2.2 User Handles 2.3 Custom Feeds and Algorithmic Choice 2.3 Custom Feeds and Algorithmic Choice 3 The at Protocol Architecture 3 The at Protocol Architecture 3.1 User Data Repositories 3.1 User Data Repositories 3.2 Personal Data Servers (PDS) 3.2 Personal Data Servers (PDS) 3.3 Indexing Infrastructure 3.3 Indexing Infrastructure 3.4 Labelers and Feed Generators 3.4 Labelers and Feed Generators 3.5 User Identity 3.5 User Identity 4 Related Work 4 Related Work 5 Conclusions, Acknowledgments, and References 5 Conclusions, Acknowledgments, and References 3.1 User Data Repositories All data that a user wishes to publish is added to their repository, which stores a collection of records. Whenever a user performs some action – making a post, liking another user’s post, following another user, etc. – that action becomes a record in their repository. Records are encoded in DAG-CBOR [45], a restricted form of CBOR [17], a compact binary data format. The schema of records is defined by the lexicon, and a repository may contain a mixture of records from several different lexicons, representing user actions in different social modes. Media files (e.g. images) are stored outside of the user’s repository, but referenced by their CID [32] (essentially a cryptographic hash) from a record in the repository. Similarly, a reference to a record in another repository (e.g. identifying a post being liked) also includes its CID. Each user account has one repository, and it contains all of the actions they have ever performed, minus any records they have explicitly deleted. A Personal Data Server (PDS) hosts the user’s repository and makes it publicly available as a web service; we discuss PDSes in more detail in Section 3.2. A user only updates their own repository; for example, if user 𝐴 follows user 𝐵, this results only in a follow record in user 𝐴’s repository, and no change to 𝐵’s repository. To find all followers of user 𝐵 requires indexing the content of all repositories. This design decision is similar to the way hyperlinks work on the web: it is easy to find all the outbound links from a web page at a given URL, but to find all the inbound links to a page requires an index of the entire web, which is maintained by web search engines. The AT in atproto stands for Authenticated Transfer, which reflects the fact that repositories are cryptographically authenticated. The records in a repository are organized into a Merkle Search Tree (MST), a type of Merkle tree that remains balanced, even as records are inserted or deleted in arbitrary order [3]. After every change to a repository, the root hash of the MST is signed; the public verification key for this signature is part of the user identity described in Section 3.5. This enables an efficient cryptographic proof that a given record appears within a given user’s repository. Moreover, when a user updates or deletes a record, the MST enables a proof that the old record no longer appears in the repository. 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

How AT Protocol Repositories Secure and Store User Actions

Why actions speak louder than titles in leadership How many of you have felt the frustration of seeing people who have been assigned a title without any experience? How many of those people do their work diligently, leaving us questioning the validity of their titles? Have you ever seen people doing extraordinary work without any titles? These individuals inspire us, showing that their actions, not titles, truly define our impact. Society’s unsung heroes are natural leaders who lead by example. They are not the ones who are assigned titles; they do what needs to be done. Let’s recognize and appreciate these leaders, regardless of their titles. “Leadership is not about titles, positions or flowcharts. It is about one life influencing another.”― John Maxwell The disconnect between titles and actions Every organization has a hierarchy that defines the roles of people. This is done to maintain proper communication between all people. A group of people are assigned to one person, and the person is given a title so that he is different from others. But sometimes, it backfires unless precaution is taken. Titles are often bestowed upon individuals regardless of their capabilities or behaviour, leading to chaos. An inexperienced person is allowed to do a task he has never faced in his life. For example, a newly hired employee might be called a “team leader” without demonstrating leadership skills. People will lose trust in the organization when they see how people are given power. If an inexperienced person manages a team of experienced people, the trust between the team will not be built. The growth required in a team will not happen. When the sites don’t match the people's abilities, it creates havoc. Organizations must maintain a proper way to see to whom titles are given and whether their abilities match. The importance of attitude in leadership Effective leadership requires various things and an attitude that never lets people down. Here are some things a leader needs to do for his people. Create a safe space


Listen more than talk


Lead with vulnerability


Celebrate small wins


Encourage risk-taking


Provide growth opportunities


Put people first, always On the other hand, people who are given the title of leader need to integrate the above into their attitudes and lives. You cannot lead without these qualities. A person’s attitude defines how his team will perform or how he will lead. Hiring a person with a good rather than a bad attitude is always good. Attitude plays a crucial role. If a person’s attitude is not good, the team’s morale will be down. People’s productivity declines daily, and soon, it becomes so bad that you must fire someone. To become a better leader, you must follow the traits mentioned above. If you do that, there will be no need for any title whatsoever. You can also lead without it. A person’s attitude and behaviour are more indicative of their leadership qualities than any formal title. For example, an experienced team member who consistently supports and guides colleagues may be seen as a leader by their peers, even without an official leadership role. Characteristics of natural leaders Great leaders always work for others. Here are some traits you need to have to become a great leader. I read somewhere about these and included them here so all readers can benefit. Empowerment: Great leaders uplift their team, giving them the confidence and tools to succeed.


Vision: Leadership is about setting a clear direction and communicating clearly to ensure others see the bigger picture.


Service: At its core, leadership is about serving others and ensuring their growth and well-being come first.


Collaboration: It’s about working with your team, not above them. The best leaders value input and diverse perspectives.


Adaptability: Leadership is being open to change and guiding your team through uncertainty.


Trust-Building: True leaders develop an environment of trust, transparency, and mutual respect.


Inspiration: Leadership is about motivating others to be their best, not by words alone, but through example. Have you heard of the term ‘servant leadership’? It is called that for a reason. It’s a leadership style that emphasizes the leader’s role as a servant to their team, focusing on their growth and well-being. When you work for people, you will automatically be uplifted. Influential leaders often possess empathy, active listening, and the ability to provide guidance. For example, a coworker who trains new employees and addresses their concerns might naturally emerge as a respected figure in the workplace. The superficiality of titles When someone is assigned a title, some responsibility is attached to it. The bearer and other people have to respect that title. The pressure to decide to assign a title is more on the bearer. He has to prove to himself and others that giving him a title is the right decision. Some people misuse the title assigned, which creates a hostile environment. People do all kinds of things in the shadow of the powers delegated to them. In today’s age, titles are superficial. I have seen people with one year of experience have the title of CTO. I laugh sometimes when I see how titles are losing their value. Assigning someone a title does not make him that person. You cannot become a CEO just because you started your own company. You may not even know the roles of the CEO. Titles are labels that do not necessarily reflect a person’s abilities or impact. For example, a manager with an impressive title who fails to inspire or motivate their team may need help to gain respect despite their position. Earning recognition through actions When someone gains trust without any required title, he is doing something right. Helping others when in need, sharing ideas, and taking initiative will make you stand out. You have to lead by example if you want to earn that respect and recognition. Authentic leadership and respect are earned through consistent positive actions and behaviours rather than being automatically granted a title. For example, an entry-level employee who consistently goes above and beyond, proposing innovative solutions and helping colleagues, may gain more influence and respect than a higher-ranking but less engaged manager. Organizations must understand that recognizing such people will increase their trust among people, and they will come forward to do the same. Feedback should be introduced in the organization to learn about such people. The company should recognize such people monthly or quarterly through emails, awards and widespread appreciation. People love to come forward to become leaders and do their work more diligently. To conclude, any person can be given a title. It does not mean he will act like one. You can provide a fresher with the title of a leader. Does that matter? No, titles are just badges. A person’s attitude tells us about his personality. A person can also act as a leader without a title. For example, people love someone who empathizes with them, listens to them, and guides them. It does not matter if he has the title of leader. Titles are only name badges, nothing more than that. If you are doing things that people love, and that too without any title, you are real. Titles do not make any person better. Instead, we have to earn that title. Book a FREE one-on-one call with me My ebook on building authority through writing. Why actions speak louder than titles in leadership How many of you have felt the frustration of seeing people who have been assigned a title without any experience? How many of those people do their work diligently, leaving us questioning the validity of their titles? How many of you have felt the frustration of seeing people who have been assigned a title without any experience? How many of those people do their work diligently, leaving us questioning the validity of their titles? Have you ever seen people doing extraordinary work without any titles? These individuals inspire us, showing that their actions, not titles, truly define our impact. Have you ever seen people doing extraordinary work without any titles? Society’s unsung heroes are natural leaders who lead by example. They are not the ones who are assigned titles; they do what needs to be done. Let’s recognize and appreciate these leaders, regardless of their titles. “Leadership is not about titles, positions or flowcharts. It is about one life influencing another.”― John Maxwell “Leadership is not about titles, positions or flowcharts. It is about one life influencing another.”― John Maxwell John Maxwell The disconnect between titles and actions Every organization has a hierarchy that defines the roles of people. This is done to maintain proper communication between all people. A group of people are assigned to one person, and the person is given a title so that he is different from others. But sometimes, it backfires unless precaution is taken. Titles are often bestowed upon individuals regardless of their capabilities or behaviour, leading to chaos. An inexperienced person is allowed to do a task he has never faced in his life. For example, a newly hired employee might be called a “team leader” without demonstrating leadership skills. a newly hired employee might be called a “team leader” without demonstrating leadership skills. People will lose trust in the organization when they see how people are given power. If an inexperienced person manages a team of experienced people, the trust between the team will not be built. The growth required in a team will not happen. When the sites don’t match the people's abilities, it creates havoc. Organizations must maintain a proper way to see to whom titles are given and whether their abilities match. The importance of attitude in leadership Effective leadership requires various things and an attitude that never lets people down. Here are some things a leader needs to do for his people. Create a safe space Listen more than talk Lead with vulnerability Celebrate small wins Encourage risk-taking Provide growth opportunities Put people first, always Create a safe space Create a safe space Listen more than talk Listen more than talk Lead with vulnerability Lead with vulnerability Celebrate small wins Celebrate small wins Encourage risk-taking Encourage risk-taking Provide growth opportunities Provide growth opportunities Put people first, always Put people first, always On the other hand, people who are given the title of leader need to integrate the above into their attitudes and lives. You cannot lead without these qualities. A person’s attitude defines how his team will perform or how he will lead. Hiring a person with a good rather than a bad attitude is always good. Attitude plays a crucial role. If a person’s attitude is not good, the team’s morale will be down. People’s productivity declines daily, and soon, it becomes so bad that you must fire someone. To become a better leader, you must follow the traits mentioned above. If you do that, there will be no need for any title whatsoever. You can also lead without it. A person’s attitude and behaviour are more indicative of their leadership qualities than any formal title. For example, an experienced team member who consistently supports and guides colleagues may be seen as a leader by their peers, even without an official leadership role. an experienced team member who consistently supports and guides colleagues may be seen as a leader by their peers, even without an official leadership role. Characteristics of natural leaders Great leaders always work for others. Here are some traits you need to have to become a great leader. I read somewhere about these and included them here so all readers can benefit. Empowerment: Great leaders uplift their team, giving them the confidence and tools to succeed. Vision: Leadership is about setting a clear direction and communicating clearly to ensure others see the bigger picture. Service: At its core, leadership is about serving others and ensuring their growth and well-being come first. Collaboration: It’s about working with your team, not above them. The best leaders value input and diverse perspectives. Adaptability: Leadership is being open to change and guiding your team through uncertainty. Trust-Building: True leaders develop an environment of trust, transparency, and mutual respect. Inspiration: Leadership is about motivating others to be their best, not by words alone, but through example. Empowerment: Great leaders uplift their team, giving them the confidence and tools to succeed. Empowerment : Great leaders uplift their team, giving them the confidence and tools to succeed. Empowerment Vision: Leadership is about setting a clear direction and communicating clearly to ensure others see the bigger picture. Vision : Leadership is about setting a clear direction and communicating clearly to ensure others see the bigger picture. Vision Service: At its core, leadership is about serving others and ensuring their growth and well-being come first. Service : At its core, leadership is about serving others and ensuring their growth and well-being come first. Service Collaboration: It’s about working with your team, not above them. The best leaders value input and diverse perspectives. Collaboration : It’s about working with your team, not above them. The best leaders value input and diverse perspectives. Collaboration Adaptability: Leadership is being open to change and guiding your team through uncertainty. Adaptability : Leadership is being open to change and guiding your team through uncertainty. Adaptability Trust-Building: True leaders develop an environment of trust, transparency, and mutual respect. Trust-Building : True leaders develop an environment of trust, transparency, and mutual respect. Trust-Building Inspiration: Leadership is about motivating others to be their best, not by words alone, but through example. Inspiration : Leadership is about motivating others to be their best, not by words alone, but through example. Inspiration Have you heard of the term ‘servant leadership’? It is called that for a reason. It’s a leadership style that emphasizes the leader’s role as a servant to their team, focusing on their growth and well-being. When you work for people, you will automatically be uplifted. Have you heard of the term ‘ servant leadership ’? servant leadership Influential leaders often possess empathy, active listening, and the ability to provide guidance. For example, a coworker who trains new employees and addresses their concerns might naturally emerge as a respected figure in the workplace. a coworker who trains new employees and addresses their concerns might naturally emerge as a respected figure in the workplace. The superficiality of titles When someone is assigned a title, some responsibility is attached to it. The bearer and other people have to respect that title. The pressure to decide to assign a title is more on the bearer. He has to prove to himself and others that giving him a title is the right decision. Some people misuse the title assigned, which creates a hostile environment. People do all kinds of things in the shadow of the powers delegated to them. In today’s age, titles are superficial. I have seen people with one year of experience have the title of CTO. I laugh sometimes when I see how titles are losing their value. Assigning someone a title does not make him that person. You cannot become a CEO just because you started your own company. You may not even know the roles of the CEO. Titles are labels that do not necessarily reflect a person’s abilities or impact. For example, a manager with an impressive title who fails to inspire or motivate their team may need help to gain respect despite their position. a manager with an impressive title who fails to inspire or motivate their team may need help to gain respect despite their position. Earning recognition through actions When someone gains trust without any required title, he is doing something right. Helping others when in need, sharing ideas, and taking initiative will make you stand out. You have to lead by example if you want to earn that respect and recognition. Authentic leadership and respect are earned through consistent positive actions and behaviours rather than being automatically granted a title. For example, an entry-level employee who consistently goes above and beyond, proposing innovative solutions and helping colleagues, may gain more influence and respect than a higher-ranking but less engaged manager. an entry-level employee who consistently goes above and beyond, proposing innovative solutions and helping colleagues, may gain more influence and respect than a higher-ranking but less engaged manager. Organizations must understand that recognizing such people will increase their trust among people, and they will come forward to do the same. Feedback should be introduced in the organization to learn about such people. The company should recognize such people monthly or quarterly through emails, awards and widespread appreciation. People love to come forward to become leaders and do their work more diligently. To conclude, any person can be given a title. It does not mean he will act like one. You can provide a fresher with the title of a leader. Does that matter? No, titles are just badges. Does that matter? A person’s attitude tells us about his personality. A person can also act as a leader without a title. For example, people love someone who empathizes with them, listens to them, and guides them. It does not matter if he has the title of leader. Titles are only name badges, nothing more than that. If you are doing things that people love, and that too without any title, you are real. Titles do not make any person better. Instead, we have to earn that title. Book a FREE one-on-one call with me Book a FREE Book a FREE My ebook on building authority through writing. My ebook My ebook

The Rise of the Titleless Leader: How Everyday Actions Build Extraordinary Leaders

Have you ever wandered into the realm of GitHub API authentication? In case you did, you have arrived in the right spot, because I have an experience that I want to share with you. When trying to authenticate to the GitHub REST API you need to use either a personal access token , the workflow GITHUB_TOKEN variable or a GitHub installation access token. The first option is not really an option for automation purpose, because a personal access token as the name suggests it is usually attributed to an user and expires after a given time frame. The GITHUB_TOKEN variable can be an interesting option for a stand-alone repo, but it is scoped to the respective repository. Hence the correct option from a GitHub organization perspective is the use of GitHub installation access token. The process of generating an installation access token requires several inputs that we obtain when we register a new GitHub application in an organization: Enter name, description, provide an URL (we’ll only use the app for authentication purposes, so you can use a dummy one) and uncheck the “Active” tick for the webhook. The other optional fields are to be left blank.
While on the same page you need to configure the permissions required by the app.
Once the registration is done, you will receive additional information on the next screen, such as app id.
While on the same screen, press “Generate a new client secret” button.
Import the App's private key in your AWS Account KMS service, under customer-managed keys of type asymmetric, sign-verify, RSA 2048, following steps 1 to 4 from the link. The private key is the client secret from previous step. The previous step follows the security best practices of storing the app private key. Storing the private key in a GitHub secret is not as secure, because if an attacker gains access to the GitHub runner environment, the attacker will consequently have access to the GitHub secret. The solution proposed is similar to Azure Key Vault, but uses AWS KMS instead. Once imported in KMS, the private key can no longer be retrieved. The authorized users can ask the AWS KMS API to sign/verify messages on their behalf, but will not perform such actions directly on the messages using the key. This way, sign/verify actions, key storage as well as user authentication and authorization are delegated to AWS. Please, make sure your AWS account access is properly secured! As you might have realized already, AWS authentication becomes the weakest link in the chain in this scenario. While AWS takes care of the security of the cloud, you are responsible for the security in the cloud. This is a broader topic which is outside the scope of this article, but as a guideline, It is highly advised to use temporary AWS credentials scoped to the least privilege when accessing AWS API in order to sign the JWT token. More on how to set up a GitHub as an OIDC provider for AWS here. Using AWS KMS will generate additional charges in your AWS bill. In the following steps, we’ll prepare the repository to be able to get the GitHub app installation access token: Store the App's ID generated previously in your repository environment variable or secret (example: APP_ID).
Store the previously generated KMS Key ID as a repository secret (example KMS_KEY_ID).
Store the AWS role to be assumed by the action as a repository secret (example ROLE_TO_ASSUME). The setup assumes you are assuming an AWS role, hence using temporary AWS credentials.
Store the AWS session name as an environment variable (example ROLE_SESSION_NAME). This is needed in case you are assuming and AWS role using OIDC.
Store the AWS region name as an environment variable (example AWS_REGION). Once you’re set up with all the above, you have all the prerequisite necessary in order to use this GitHub action for generating the GitHub installation access token for your GitHub app. The action which I have developed unlike the vanilla one uses AWS KMS in order to sign/verify the JWT token required for generating the GitHub installation access token. Terraform - A Case Study Recently I have started to investigate ways to authenticate terraform provider to the GitHub API in order to be able to use it in deploying GitHub Infrastructure (create repos, etc) inside a GitHub organization. The terraform documentation gives 2 options,  GitHub app and OAuth/personal access token. I have taken the inputs required by the GitHub app authentication (i.e. app id and app private key) and developed a GitHub action capable of using AWS KMS for storing the private key and generating the installation access token. Once the token is generated, you can override the GITHUB_TOKEN workflow environment variable with the token produced by the action. Here is a terraform example on how to use the action as well as the respective workflow file. Enjoy! Have you ever wandered into the realm of GitHub API authentication? In case you did, you have arrived in the right spot, because I have an experience that I want to share with you. When trying to authenticate to the GitHub REST API you need to use either a personal access token , the workflow GITHUB_TOKEN variable or a GitHub installation access token. The first option is not really an option for automation purpose, because a personal access token as the name suggests it is usually attributed to an user and expires after a given time frame. The GITHUB_TOKEN variable can be an interesting option for a stand-alone repo, but it is scoped to the respective repository. Hence the correct option from a GitHub organization perspective is the use of GitHub installation access token . authenticate to the GitHub REST API GITHUB_TOKEN GitHub installation access token The process of generating an installation access token requires several inputs that we obtain when we register a new GitHub application in an organization: generating an installation access token new GitHub application Enter name, description, provide an URL (we’ll only use the app for authentication purposes, so you can use a dummy one) and uncheck the “Active” tick for the webhook. The other optional fields are to be left blank. While on the same page you need to configure the permissions required by the app. Once the registration is done, you will receive additional information on the next screen, such as app id. While on the same screen, press “Generate a new client secret” button. Import the App's private key in your AWS Account KMS service, under customer-managed keys of type asymmetric, sign-verify, RSA 2048, following steps 1 to 4 from the link. The private key is the client secret from previous step. Enter name, description, provide an URL (we’ll only use the app for authentication purposes, so you can use a dummy one) and uncheck the “Active” tick for the webhook. The other optional fields are to be left blank. While on the same page you need to configure the permissions required by the app. Once the registration is done, you will receive additional information on the next screen, such as app id. While on the same screen, press “Generate a new client secret” button. Import the App's private key in your AWS Account KMS service, under customer-managed keys of type asymmetric, sign-verify, RSA 2048 , following steps 1 to 4 from the link. The private key is the client secret from previous step. Import the App's private key in your AWS Account KMS service, under customer-managed keys of type asymmetric, sign-verify, RSA 2048 Import the App's private key in your AWS Account KMS service, under customer-managed keys of type asymmetric, sign-verify, RSA 2048 The previous step follows the security best practices of storing the app private key. Storing the private key in a GitHub secret is not as secure, because if an attacker gains access to the GitHub runner environment, the attacker will consequently have access to the GitHub secret. The solution proposed is similar to Azure Key Vault, but uses AWS KMS instead. Once imported in KMS, the private key can no longer be retrieved. The authorized users can ask the AWS KMS API to sign/verify messages on their behalf, but will not perform such actions directly on the messages using the key. This way, sign/verify actions, key storage as well as user authentication and authorization are delegated to AWS. the security best practices Please, make sure your AWS account access is properly secured! Please, make sure your AWS account access is properly secured! As you might have realized already, AWS authentication becomes the weakest link in the chain in this scenario. While AWS takes care of the security of the cloud, you are responsible for the security in the cloud . This is a broader topic which is outside the scope of this article, but as a guideline, It is highly advised to use temporary AWS credentials scoped to the least privilege when accessing AWS API in order to sign the JWT token. More on how to set up a GitHub as an OIDC provider for AWS here . While AWS takes care of the security of the cloud, you are responsible for the security in the cloud here Using AWS KMS will generate additional charges in your AWS bill. Using AWS KMS will generate additional charges in your AWS bill. In the following steps, we’ll prepare the repository to be able to get the GitHub app installation access token: Store the App's ID generated previously in your repository environment variable or secret (example: APP_ID). Store the previously generated KMS Key ID as a repository secret (example KMS_KEY_ID). Store the AWS role to be assumed by the action as a repository secret (example ROLE_TO_ASSUME). The setup assumes you are assuming an AWS role, hence using temporary AWS credentials. Store the AWS session name as an environment variable (example ROLE_SESSION_NAME). This is needed in case you are assuming and AWS role using OIDC. Store the AWS region name as an environment variable (example AWS_REGION). Store the App's ID generated previously in your repository environment variable or secret (example: APP_ID ). Store the App's ID generated previously in your repository environment variable Store the App's ID generated previously in your repository environment variable secret secret APP_ID Store the previously generated KMS Key ID as a repository secret (example KMS_KEY_ID ). Store the previously generated KMS Key ID as a repository secret Store the previously generated KMS Key ID as a repository secret KMS_KEY_ID Store the AWS role to be assumed by the action as a repository secret (example ROLE_TO_ASSUME ). The setup assumes you are assuming an AWS role, hence using temporary AWS credentials . Store the AWS role to be assumed by the action as a repository secret Store the AWS role to be assumed by the action as a repository secret ROLE_TO_ASSUME temporary AWS credentials Store the AWS session name as an environment variable (example ROLE_SESSION_NAME ). This is needed in case you are assuming and AWS role using OIDC. Store the AWS session name as an environment variable Store the AWS session name as an environment variable ROLE_SESSION_NAME Store the AWS region name as an environment variable (example AWS_REGION ). Store the AWS region name as an environment variable Store the AWS region name as an environment variable AWS_REGION Once you’re set up with all the above, you have all the prerequisite necessary in order to use this GitHub action for generating the GitHub installation access token for your GitHub app. The action which I have developed unlike the vanilla one uses AWS KMS in order to sign/verify the JWT token required for generating the GitHub installation access token. this Terraform - A Case Study Recently I have started to investigate ways to authenticate terraform provider to the GitHub API in order to be able to use it in deploying GitHub Infrastructure (create repos, etc) inside a GitHub organization. The terraform documentation gives 2 options,  GitHub app and OAuth/personal access token. authenticate terraform provider I have taken the inputs required by the GitHub app authentication (i.e. app id and app private key) and developed a GitHub action capable of using AWS KMS for storing the private key and generating the installation access token. GitHub action Once the token is generated, you can override the GITHUB_TOKEN workflow environment variable with the token produced by the action. Here is a terraform example on how to use the action as well as the respective workflow file . Here workflow file Enjoy!

Stories, News & Mentions about ACTITO

Actito’s Stories on HackerNoon

Actito's News & Mentions