MuhammadSulaiman001

Change Log

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog and this project adheres to Semantic Versioning.

[Unreleased] - yyyy-mm-dd

Here we write upgrading notes for brands. It's a team effort to make them as

MuhammadSulaiman001

Git Branching Strategy

Quick Legend

Branch	Name	Notes
Stable	master	Accepts merges from Release and Hotfix branches only.
Development	develop	Accepts merges from Feature/Bugfix, Release and Hotfix
Features/Bugfix	feat-* / bug-*	Always branch off HEAD of develop
Hotfix	hotfix-*	Always branch off master. Merges back into master and develop.

MuhammadSulaiman001

using System;
using System.Collections.Generic;
using TwinCAT.Ads;
using TwinCAT.Ads.Reactive;

namespace Project.CncModule.Utils;

public static class AdsExtensions
{
    private static readonly HashSet<IDisposable> AdsDisposables = new();

MuhammadSulaiman001

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules

MuhammadSulaiman001

# The following command works for downloading when using Git for Windows:
# curl -LOf http://gist.githubusercontent.com/kmorcinek/2710267/raw/.gitignore
#
# Download this file using PowerShell v3 under Windows with the following comand:
# Invoke-WebRequest https://gist.githubusercontent.com/kmorcinek/2710267/raw/ -OutFile .gitignore
#
# or wget:
# wget --no-check-certificate http://gist.githubusercontent.com/kmorcinek/2710267/raw/.gitignore

# User-specific files

MuhammadSulaiman001

So this is a guide for how to use XAMPP to test any PHP website on your own computer. Well, actually, it's more a guide of guides than an actual guide. I personally didn't find the process to be bad, but it also wasn't straightforward, and it involved a lot of googling separate problems. There was no One Guide for the Entire Process, but a bunch of separate things.

So I decided to put everything together. Here are the steps:

Step 1: Install XAMPP. Download from here.

Step 2: Set up XAMPP. Follow instructions here.

Step 3: Go to PhpMyAdmin and create any relevant MySQL tables, if any.

MuhammadSulaiman001

using System;
using System.Speech.Recognition;

namespace ConsoleApp
{
    internal static class Program
    {
        private static void Main(string[] args)
        {
            // Create an in-process speech recognizer for the en-US locale.  

MuhammadSulaiman001

Good projects on "Speeck Emotion Recognition"

• https://github.com/MiteshPuthran/Speech-Emotion-Analyzer (1.1k stars)
• https://github.com/x4nth055/emotion-recognition-using-speech (408 stars)
• https://github.com/SuyashMore/MevonAI-Speech-Emotion-Recognition (134)
• https://github.com/shaharpit809/Audio-Sentiment-Analysis (53 stars)
• https://github.com/Jason-Oleana/speech-emotion-classification (13)
• https://github.com/LetianLee/Speech-Emotion-Recognition (12)

Note: RAVDESS Dataset = 7,356 files (total size: 24.8 GB)

MuhammadSulaiman001

Definition (Code Smells) Code smells are common code anti-patterns which could and should be refactored.

This doc is summarized from Martin Flower's book Refactoring (the 2nd Edition).

Refactoring is all about Change

• You may inverse previous refactorings as software grows
• You may change names of a function/parameter/varible/... as you learn

How to use this doc

Go to a section of code smell, and the refactoring techniques to that smell are written in Pascal Case under the Solution section. Refer to the book's catalog to get detailed examples and explainations for each refactoring technique.

Table of Code Smells

MuhammadSulaiman001

Git submodule workflow example..

Monday 10:00 AM. (adding the submodule to the base repo)

• You have a project (exisiting repo), you want to add/host another repo inside your project..

  • This project might be yours, ex. you have a library and many projects that you want to use the library inside them, so you want to keep just one-updated copy of the library..
  • Or, You've forked a repo, You want to do frequent/many changes to the code and you want to keep up to date with the owners edits and bug fixes..

• In your project (that will host the submodules):