DEV Community: Learn dev tools

Best Linux Developer Tools for a Lean and Productive Setup

Learn dev tools — Mon, 29 Dec 2025 17:02:44 +0000

When I started cleaning up my Linux workflow, I realized something obvious that I had ignored for years. Productivity didn’t come from installing more tools. It came from choosing a small set that worked together without friction. Before diving into the details, here is the toolkit that shaped my daily development routine and actually stayed installed on my machine.

1. Code editors / IDEs

VS Code / VSCodium
JetBrains IDEs (IntelliJ, PyCharm, WebStorm)
Neovim

2. Version control & repositories

Git (CLI first)
GitHub / GitLab (for collaboration)

3. Shell, terminal, productivity

Fish or Zsh
Kitty, Tilix, or Terminator
tmux (session management and panes)

4. Automated testing & CI

pytest, Jest, PHPUnit (depending on language)
GitHub Actions or GitLab CI (basic pipelines)

5. Containers & environments

Docker or Podman
docker-compose for multi-service setups

6. Debugging, profiling, databases

gdb / lldb
Valgrind
DBeaver or DataGrip

7. Design and architecture thinking

Excalidraw
PlantUML
draw.io

8. AI helpers (used carefully)

GitHub Copilot
Codeium
Cursor or similar AI coding assistants

9. Two practical stacks

Free stack: VS Code or Neovim, Git, tmux, Docker, CI, DBeaver, Excalidraw
Paid-plus stack: JetBrains IDEs, Copilot, DataGrip, managed CI minutes

If any of these tools catch your attention, I break them down in more detail in the full guide, with examples of how they fit into real projects.

Best Production Management Software for Small Manufacturers in 20256

Learn dev tools — Wed, 26 Nov 2025 20:50:06 +0000

Small manufacturers often rely on spreadsheets or disconnected tools, which leads to delays, stock errors, and low visibility. The original article explains why modern production-management software helps reduce mistakes, sync inventory, and provide real-time visibility on the shop floor.

Why Production Software Matters

Real-time production tracking
Automatic inventory and warehouse syncing
BOM (Bill of Materials) management with version control
Easier planning and fewer human errors
Integrations with ecommerce, accounting, and shipping
Simple onboarding for small teams
Scalable without needing a full ERP

What to Look For in a Good Tool

Real-time dashboards
Inventory automation
BOM versioning
Easy training
Strong integrations (Shopify, QuickBooks, scanners, etc.)

Top Recommended Tools (2025)

Software	Best For
Katana	Ecommerce-driven and DTC manufacturers
MRPeasy	Small workshops replacing spreadsheets
Odoo	Growing teams that need modular ERP flexibility
Fishbowl Manufacturing	Inventory-heavy and regulated products
Prodsmart	Real-time shop-floor digitization
JobBOSS²	Custom make-to-order job shops
ERPNext	Open-source ERP built for scalability

Which Tool Should You Choose?

For ecommerce-first workflows → Katana, MRPeasy
For scalable ERP features → Odoo, ERPNext
For strong warehouse controls → Fishbowl
For digitizing paper processes → Prodsmart
For custom one-off production → JobBOSS²

Final Note

The right tool depends on your workflow. Start by identifying your pain points (inventory errors, scheduling, visibility), then test the tools that match your needs.

👉 Read the full article here: https://www.learn-dev-tools.blog/best-production-management-software-for-small-manufacturers/

Top LLMOps Tools to Manage Your AI Stack in 2025

Learn dev tools — Mon, 21 Apr 2025 22:00:04 +0000

🚀 LLMOps is no longer a luxury — it's the backbone of modern AI workflows.

If you're building anything with GPT, Claude, or LLaMA in 2025, you need tooling that scales. From prompt orchestration to observability and deployment, this space is growing fast — and messy.

In this post, you'll get a curated shortlist of the top LLMOps platforms, based on real-world use cases and practical criteria.

✅ What to Look for in an LLMOps Platform

Prompt versioning and testing support
Observability (latency, drift, hallucinations, cost tracking)
Seamless deployment workflows (GPU support, serverless, containerization)
Integration with OpenAI, Hugging Face, Anthropic
Enterprise readiness (compliance, auditing, scalability)

🧰 Top LLMOps Tools (Shortlist)

LangChain — Best for chaining workflows and agent logic

W&B — Best for experiment tracking and observability

LlamaIndex — Ideal for RAG and external data integration

Arize AI — LLM observability with hallucination detection

Fiddler AI — Focused on fairness, bias, and explainability

PromptLayer — GitHub-style versioning and A/B testing for prompts

BentoML — Production-ready model deployment (GPU + API support)

📊 Bonus: Download the LLMOps Toolkit (PDF)

🧠 Final Thoughts

The best LLMs still need great infrastructure. Whether you’re documenting internal copilots or launching a production-grade chatbot, the tools you use will make or break scalability and performance.

Need help documenting or selecting your stack?

👉 Let’s work together

Originally published on learn-dev-tools.blog

How to Add a File Service Plugin to Your Medusa Store?

Learn dev tools — Wed, 26 Apr 2023 21:31:00 +0000

Headless commerce has been out there for a long while with Medusa being one of the best alternatives to Shopify. Medusa’s composable architecture allows you to build a store with any framework or language of your choice hence providing a full customization ability. Medusa equally allows you to build a unique ecommerce experience by providing a set of tools and essential building blocks developers can add up to create a powerful ecommerce website. It offers out-of-the-box features like customer, product, shipping, tax and region management, and RMA Flow. In today’s tutorial, you will learn how to add a file service plugin in order to be able to add products to your Medusa store via the admin dashboard

What is Medusa

Medusa is an open-source set of tools that allow you to build amazing and reliable ecommerce websites. With more than 17.8k stars and 1.3k forks on GitHub, this headless commerce solution comes with a handful of commerce modules from basic to advanced and is freely available. Its well-written documentation also contributes to its success as there are step-by-step guidelines on how to add a module or plugins. Some popular plugins among others are payments, notifications, search and file service plugins.

What is a File Service Plugin

A file service plugin allows you to host files like images used in Medusa. You may face issues if you don’t use or set up a file service for your Medusa store properly. Medusa offers three different ways to manage file storage; S3, MinIo and Spaces. This tutorial solely focuses on S3 file storage to store images and files uploaded in Medusa.

S3 or Simple Storage Service is an object storage used to store and retrieve any amount of data from anyway and at any time. We will use Amazon S3 for this demonstration.

How to upload files into your Medusa store

Amazon keeps data as objects within a bucket. An object consists of a file and optional data that describes it. To store a file, you need to upload it in a bucket(Buckets are the containers for objects), once uploaded, you can set permissions on the object.

Now let’s get you to upload files in your Medusa projects quickly.

Prerequisites

A Medusa store. A Medusa project is basically divided into three components; a storefront, an admin dashboard and a Medusa Backend
An AWS account

If you have everything set up then follow the steps below to add a File Service Plugin to Your Medusa Store.

Step 1: Create an S3 Bucket

In the next page, Click on Create bucket

In the window that opens, provide the information necessary to create your bucket.

General Configuration

Provide a name to your bucket and leave the default region or choose another one per your requirements.

Object Ownership

For ownership, allow objects in the bucket to be owned by your account.

In the Block Public Access settings, uncheck Block all public Access. Doing this will show a warning message check the box in the message as in the image.

As for the Bucket versioning, tags, default encryption and advanced settings, leave the default settings or change them per your project requirements and click on Create bucket.

Step 2: Manage Policies

The next step consists of managing your created bucket policies. Head to the page of your bucket and open the permission tab. Then scroll down to the bucket policy section, click on edit, add the code below and Save.

{
 "Version": "2012-10-17",
 "Id": "Policy1397632521960",
 "Statement": [
   {
     "Sid": "Stmt1397633323327",
     "Effect": "Allow",
     "Principal": {
       "AWS": "*"
     },
     "Action": "s3:GetObject",
     "Resource": "arn:aws:s3:::<YOUR_BUCKET_NAME>/*"
   }
 ]
}

Replace <YOUR_BUCKET_NAME> with the name of your bucket. Here it is medusastorebucket

Step 3: Attach a Policy

In your account navigate to IAM and select Access Management->Policies in the left menu.

If this is your first time choosing a policy, then you will see a Welcome to Manage Policies Page and select get started else choose Create policy.

Then select the JSON tab and add the following code:

{
  "Version": "2012-10-17",
  "Statement" : [
    {
      "Effect" : "Allow",
      "Action" : [
        "action-statement"
      ],
      "Resource" : [
        "resource-statement"
      ]
    },
    {
      "Effect" : "Allow",
      "Action" : [
        "action-statement"
      ],
      "Resource" : [
        "resource-statement"
      ]
    }
  ]
}

Substitute the action-statement and resource-statement per your requirement and click on Next:tag

Learn more about Policies and permissions

Tags are optional so you can skip this step and click on the review button to review your policy.

Next, provide a name and description for your policy then click on Create policy

Now that you have created your policy, you need to attach it to a user group, navigate to Amazon console and choose User Groups. Select the name of the group then open the Permission tab

Choose Add permission and then attach policies

In the window that opens, select the policy you want to attach and click on add permission at the bottom of the page.

Step 4: Get Your Access Key

You need to obtain your access key in order to integrate the S3 Plugin into your project. You will need two elements; Access Key ID and Secret Access Key.

To get your AWS Access Key ID and Secret Access Key, head to your Amazon console on the left navigation, and choose Users.

Choose your IAM user name and open the Security credentials tab

Scroll down to Access Keys and click on Create Access Key

In the next window, you will be asked to choose where you want to use the access key. Check Local code if you are working in a local dev environment.

By choosing local a warning message will appear asking you if you understand the recommendation. Check the box and click on the next button.

Finally, add a tag description if you like to add one and click on Create access key

In the next window, you will see your Access and Secret Access key. Kindly copy and paste it somewhere on your PC since you will use it in the next step or download the CSV file.

Step 5: Install the S3 Plugin

Now that you have set up your bucket and created your access keys, it’s time to install the S3 plugin. To do so head to your Medusa backend folder and install it with the following command:

yarn add medusa-file-s3

npm install medusa-file-s3

Then open your .env file and add the following

S3_URL=<YOUR_BUCKET_URL>
S3_BUCKET=<YOUR_BUCKET_NAME>
S3_REGION=<YOUR_BUCKET_REGION>
S3_ACCESS_KEY_ID=<YOUR_ACCESS_KEY_ID>
S3_SECRET_ACCESS_KEY=<YOUR_SECRET_ACCESS_KEY>

Where

<YOUR_BUCKET_URL> is the URL of your bucket. It is in the form https://<BUCKET_NAME>.s3.<REGION>.amazonaws.com. Where <BUCKET_NAME> is the name of your bucket, <REGION> the region.
<YOUR_BUCKET_NAME> is the name of the bucket created
<YOUR_BUCKET_REGION> the region of your bucket
<YOUR_ACCESS_KEY_ID> is your Access Key
<YOUR_SECRET_ACCESS_KEY> is your Secret Key

Finally in your medusa-config.js add the following code:

const plugins = [
  // ...
  {
    resolve: `medusa-file-s3`,
    options: {
        s3_url: process.env.S3_URL,
        bucket: process.env.S3_BUCKET,
        region: process.env.S3_REGION,
        access_key_id: process.env.S3_ACCESS_KEY_ID,
        secret_access_key: process.env.S3_SECRET_ACCESS_KEY,
    },
  },
]

Note that if you have many storage plugins configured, then the last plugin declared will be used. So if you want S3 to be used make sure it's the last storage plugin added.

Step 6: Testing the Plugin

Now that you have successfully added your plugin. It's time to test to make sure that everything is in the right place. You can use REST APIs or the Medusa Admin to test.

Navigate to your admin and backend folders respectively and run the following command:

// admin 
yarn run start

// backend
yarn run start

The default admin email and password are admin@medusa-test.com and supersecret respectively. Open your admin panel with http://localhost:7000/

In the menu click on Products then Add Product. Provide details for your product and publish it.

Lastly, you need to add a configuration in your storefront that adds the S3 bucket domain name into the configured images’ domain names if you are using NextJS storefront. If you don't do it you will receive the following error next/image Un-configured Host.

So in your next.config.js add the following:

const { withStoreConfig } = require("./store-config")

// ...

module.exports = withStoreConfig({
  // ...
  images: {
    domains: [
      // ...
      "<BUCKET_NAME>.s3.amazonaws.com",
    ],
  },
})

<BUCKET_NAME> represents the name of your bucket.

Run your storefront with yarn run dev to check if the new products you added are there and proceed to the next phase of your project.

Conclusion

This marks the end of this tutorial, hopefully, you were able to add a file service plugin to your Medusa store. To get the best of Medusa, consider adding payment services, search and notifications services.

How to build a Medusa Webshop with one command?

Learn dev tools — Tue, 18 Apr 2023 21:29:01 +0000

Introduction

With the growth of the internet and the evolution of technologies, there is a need for businesses dealing in the ecommerce sector to remain competitive by keeping up with the latest trends in the area. Medusa is a popular open source headless ecommerce solution developed recently, scalable, and flexible making it one of the best choices for building an ecommerce website. It comes with two storefronts NextJs and Gatsby from which you can choose one or use a different stack for your storefront since Medusa has a composable architecture allowing you to use different technologies for your front and backend hence giving the possibility to fully customize your store and creating a store that will fit your needs.

In this article, you will get started with Medusa by building your first headless store with a single command.

Why Medusa?

Medusa is an open source user and developer-friendly platform for building incredible webshops. With over 17.8k stars on GitHub, its architecture allows you to build your online commerce shop with any framework of your choice that is developers have full control over their tech stack and the logic behind the commerce features. Besides that, it offers multi-regional support, advanced features for promotion and RMA flows, a user-friendly admin interface, and a community to support users.

How to Build a Medusa Webshop?

You will learn how to build your first webshop with just a single Medusa command. However make sure you have the following elements installed and working properly:

Node.js version 16 or latest. To check your Node.js version open your terminal or command line and run node -v. If you don’t have Node installed, then head to the official website, and follow the instructions to get it running on your OS
Git
A package Manager(Yarn or Npm)
Medusa CLI

Now let’s get started. The first step will be to install the Medusa CLI. You can’t use Medusa without installing its command line. Run the following command to get it set up:

yarn global add @medusajs/medusa-cli

npm install @medusajs/medusa-cli -g

Upon installing the CLI, check the version by running the following command in your terminal

medusa -v

If you ever encounter errors installing the CLI then visit this Medusa troubleshooting guide to get everything up.

Creating your Webshop with create-medusa-app

Medusa is divided into three main parts:

Backend - It’s the commerce engine
Storefront - The actual webshop
Admin Dashboard - An application to manage your store(add/remove products, collections, payment methods, manage customers…)

Step 1: Install your Webshop with create-medusa-app

Open a terminal in your desired directory and run the following command:

npx create-medusa-app

NB: When you install your project with this command, it comes with Tailwind CSS

Step 2: Specify the project name

You need to specify the name of your webshop or leave the default value my-medusa-store. Here we will name the store my-headless-store.

? Where should you project be installed? . my-headless-store

Step 3: Choose a Backend starter

Once you have named your store, the next step is to choose a Medusa starter. Here we will be using medusa-starter-default

? Which Medusa starter would you like to install? …
❯ medusa-starter-default

This Medusa starter contains admin plugins, which will allow you to later access the admin dashboard. All the resources for the backend will be installed in the backend directory

Step 4: Choose a Storefront starter

The next consists of choosing the Medusa starter for your storefront. Here we will be using the NextJS starter

? Which storefront starter would you like to install?
❯ Next.js Starter

Your storefront will be installed in the storefront directory.

Now you need to wait until your project sets up completely before testing your store.

Step 5: Test your store

Upon installing all components of your project, you will see find three folders in your project directory.

Admin
Backend
Storefront

To start each component of your project navigate to each component root and run the commands as follows:

Your project is ready. The available commands are:

// Medusa API
cd my-headless-store/backend
yarn start

// Medusa Admin
cd my-headless-store/admin
yarn start

// Storefront
cd my-headless/storefront
yarn dev

To view your store and admin dashboard, open your favourite browser and type localhost:7000 and localhoat:8000 in the address bar respectively

Your store should look like the image below:

And your dashboard:

To access the dashboard, use

admin@medusa-test.com as email
supersecret as password

Well, if you have reached this stage that means you have successfully set up a basic webshop with Medusa however if you run into any trouble reach out on this website or reach out to the Medusa Discord channel for further assistance.

Conclusion

Hopefully, you have learnt how to build a basic store with Medusa, now you need to customize your store and add plugins and services like:

Payment methods with Klarna, Paypal, or Stripe
Notification services with SendGrid, Mailchimp or Twilio SMS
Search functionality with Algolia or MeiliSearch
File upload Services with S3, Space or MinIO
Shipping method.
Gift cards

Just head to the full Medusa Documentation to get the necessaire instructions to fulfil each task. Equally, feel free to sign up for our newsletter in order to get the latest ecommerce related content.

What is Open Source Software? A Beginner's Guide

Learn dev tools — Tue, 18 Apr 2023 21:25:42 +0000

Introduction

If you have been in the tech industry for a while you may have heard about open source or open source software. When we talk about open source, you should think of open collaboration, open exchange, participation transparency and community-oriented development.

In this article, you will learn more about open source software including the difference between open source and other forms of software, key features of OSS, pros and cons of open source, how to start contributing to open source and some examples of OSS.

What is Open Source?

Open source designed any program whose source code can be modified and shared by anyone because it’s openly accessible.

What is Source Code?

A source code is a set of instructions written in the form of functions, descriptions, methods, calls or any other operational statement by a programmer using a computer programming language. A source code can be open that is available to anyone to edit and redistribute or closed. Source code is the part that most software or computer users cannot see.

Example of a Source code taken from Medusa's GitHub Repository

What Does Open Source Software(OSS) Mean?

The term Open source software is a non-proprietary software in which code is publicly available to anyone to inspect, comment on, modify, improve and redistribute it. Open source software is created and maintained by a group of developers so if you are new to computer programming, you can begin your journey as an open source contributor.

I have known open source since 2017 and started with my first contribution in 2020. I made my first contributions to the Apache Software Foundation Gihhub and Mozilla mobile Github.

What is the Difference between Open source Software and other Types of Software?

Do not get confused with open source, free, closed software and freeware. This section highlights the differences between these types of Software.

Open Source vs Free Software

Open source software is software available for anyone to edit, improve and redistribute. The source code is accessible to anyone. Open source promotes collaboration and sharing of source code. It’s an effective way for organizations, developers and individuals to collaborate. Freedom to use the software is not absolute or imposed but it’s allowed. Every open source software is not free. However, some open source licenses are restrictive. WordPress is an example of open source software

Free Software describes software in which source code is free to use, edit and redistribute without any restrictions. With free software, Freedom is a value that is more important than any other thing. All free software is open source software. Ares is an example

Open source and free software have distinguished features. Some open source software is restrictive and all free software are open source software but not all open source software is free software.

Open Source Software vs Freeware

Freeware is any software that is free to use and available to the general public. If you are a, it can be frustrating to use freeware because its source code is not open or rather, it’s closed so you can edit the software to fit your needs. You can only use the features it offers even if it it is limited. Google Chrome is an example of freeware

While with open source software, you have the possibility to edit, improve, and add different features to fit your needs. An example is Chromium.

Freeware source code is closed, only the developer or organization who created the software can view its source code while open source one can edit and redistribute. Freeware is copyrighted while Open source is not.

Open Source vs Proprietary Software

You do not need an authenticated license to use open source software. They function with GNU Public License. They can be installed freely on any computer system. Open source software is developed and maintained through open collaboration.

Proprietary Software is software with protected source code(closed). They cannot be installed on a computer without a valid license. So users need a valid and authenticated license to use it. They are also copyrighted like freeware but the difference is that you do not need to pay to use freeware. An example is Windows

Key features of Open Source Software

In this section, I will elaborate on the various key features and values that cover Open source Software.

Transparency: Open source allows you to track and understand any changes made to software without relying on the software manufacturer.
Collaboration: The main goal of the open source initiative is to allow anyone to freely participate and improve the software. By working together, we can easily identify and solve problems
Meritocracy: Including diverse perspectives from different brains can help identify the best ideas by decision-makers and could equally determine the success of a project.
Community: When many people gather to help and share ideas, it creates a community where each other can get support.
Review: Since source code is freely available to the public, different experimented community members can check, propose ideas and improve the software.
Reliability: Many collaborators can update and test the code to check if there is any bug and fix it. Open sources do not depend on one, two or three people to maintain but rather have a large community that supports them.
Flexibility: Flexibility refers to the fact that you can use open source code to address problems that are unique to your business. Plus you can rely on community help to improve an existing solution or implement a new one.
Lower cost: Most of the time, open source is free to use and download. Sometimes you may need to pay for only reinforcing security and interoperability.

What are the Benefits of Open Source?

Choosing to use or contribute to open source software offers many benefits. Some of them include:

Open source is free
You have more control over the software. Compare to Closed software you can edit open source software to fit your needs.
It's good for anyone beginning computer programming. As a beginner, you can become a better programmer by sharing your work and contributing to other works
Open source is good because it can help to enhance software security as anyone can spot and fix a security issue quickly that the original programmer may have missed
Open source projects tend to be more stable than other types of software since there is a great community behind ready-to-deploy means to improve it.
It promotes collaboration through the creation of communities.
Open source is flexible
They have Good Documentation

What are the Disadvantages of Open Source Software?

Not everyone embraces the open source philosophy. Some organizations still debate the fact that open source software is more vulnerable since their source code is open to anyone.

I have been in the software community for 3 to 4 years now and I have noticed that they tend to be more secure since issues linked to security or not can easily be identified and fixed by community members. However, I equally notice some drawbacks of open source.

Open source software can be difficult to set up, especially for beginners. Some of them may lack user-friendly interfaces imposing you to use a Terminal
Liability problems. Open source rarely contains warrant or liability protections
Compatibility issues.
Initially, there is no cost but it can be costly in the long term especially if you need immediate support. There is also training cost in case you incorporate the software into your team.
Not all open source possesses a user manual although you can seek help from the community it won't always be available immediately like commercial software where support is available 24h/7

How can you Start Contributing to Open Source?

It’s quite simple to contribute to open source software. You could do that by identifying and fixing bugs, adding features, improving documentation and writing content in the form of blog posts, technical tutorials or creating Videos. You also create your own open source project to promote open source.

To contribute to existing open source software, you should head to GitHub:

Find a project and Fork
Clone the Project to your Local machine
Create a new branch
Make changes
Commit your changes
Push your changes to your remote repository
Finally, Create a pull request

If you don’t have any project ideas, then open source projects to contribute to include

Open Source License

An Open source License governs how other individuals besides the initial developer can use, modify and redistribute the software. It allows the software to be transparent and changed by members of a community or third party. According to the Open Source Initiative include

Example of Open Source Software

You might have used an open source software without realising. There are many of them out there. Some popular and most-used open source software is

WordPress, an open source CMS for Content Management
Flutter for web, desktop and mobile development
CSS Frameworks Like Bootstrap for website layout
VLC Media Player for video and sound player
Libre Office for word processing
Open source Linux Operating System
Python is open source too.
Open source reporting tools include Metabase, BIRT
Open source PDF viewer include Qoppa PDF Studio, pdfFiller, and Soda PDF
Some Java open source projects are Arduino, Mindustry, and Signal Android
We equally have open source development tools like Eclipse IDE, and Apache Cordova

FAQ

Is Open Source Software Free?

Most open source software is free but there are some exceptions. Some open source licenses are restrictive and do not allow the creation of a modified version. An example is Open Source Watcom

Where can I find OSS?

You can find and download open source projects on SourceForge, OSDN, FossHub, GitHub, and F-Droid

Why Should you Contribute to OSS?

The most important advantage of contributing to open source is that you can find and collaborate with other developers hence improving your developer network.

Why is Open Source Important?

Open source improves innovations through collaboration with other organizations and developer

What are Some Open Source Competitions?

Open Source Competitions are contests where you can learn to participate in open source projects, demonstrate your coding skills, and get feedback. Examples of Open source competitions include Open Source Contest, Google Summer of Code (GSoC), Outreachy, Open Summer of Code, Free Software Foundation (FSF) Internship Program, GirlScript Summer of Code (GSSoC)

What is Closed Source Software?

Closed Software is software whose source code is only available to the author. So only the author can modify and copy it.

What is the Open Source Initiative?

The Open Source Initiative is a non-profit organisation with the main aim to educate about, form, and inform the benefit of open source

Conclusion

Open source is available for anyone to edit, use and redistribute. Some key features of open source include transparency, reliability, available community and flexibility. However, OSS can be costly in a long run. So if you are planning to incorporate OSS into your business you need to include additional or urgent costs in your project plan including the cost of training staff members to use the software. Some popular Open source projects include Apache, WordPress, and Mozilla Firefox.

If you like this kind of content, feel free to share or subscribe to our newsletter below to get fresh content like this periodically. But if you have any questions, you can reach me via my Twitter account. I will be glad to hear from you.