The-Running-Dev

If you already know some coding and are tired of the DSA/Leetcode treadmill, the next logical step is to shift from solving puzzles to building systems. That means learning design patterns, SOLID principles, and architectural thinking — the things that actually show up in production code.

Here’s a practical roadmap, not theory:

1. Core Design Patterns (the real backbone of OOP)
Focus on why they exist, not just how they work.

• Creational: Singleton, Factory Method, Builder, Prototype → manage object creation (e.g. config loaders, factories for services).
• Structural: Adapter, Facade, Decorator, Composite → wrap APIs, extend behavior, simplify interfaces.
• Behavioral: Strategy, Observer, Command, Chain of Responsibility, State → modular logic, event systems, UI flows.

The-Running-Dev

Assuming:

VPN interface: nordlynx
Local interface: enp2s0
Local LAN subnet: 192.168.1.0/24
Host IP: 192.168.1.2
DNS server IP: 192.168.1.2:53

🔁 1. Enable IP Forwarding
```bash

The-Running-Dev

something:
    container_name: something
    image: lscr.io/linuxserver/prowlarr:latest
    ....
    healthcheck:
      test: curl -sf http://localhost || exit 1
      interval: 60s
      timeout: 30s
      retries: 5
      start_period: 30s

The-Running-Dev

#!/bin/bash

set -e

echo "Updating system..."
sudo apt update
sudo apt upgrade -y

echo "Installing prerequisite packages..."
sudo apt install -y \

The-Running-Dev

# Exampe .env file for the Doplarr docker-compose.yml

BotToken=INSERT_YOUR_KEY_HERE
ConfigRootPath=/path/to/your/discord-bot/data
RequestsAPIKey=INSERT_YOUR_KEY_HERE
RequestsDefaultID=1
RequestsHost=requests

The-Running-Dev

param (
    [switch] $verbose
)

# Function to log messages
function Log-Message {
    param (
        [string] $message,
        [string] $type = 'INFO'
    )

The-Running-Dev

# Resources
# Sample package: https://www.myqnap.org/product/radarr-qbase24/
# Create a simple package: https://cheng-yuan-hong.gitbook.io/qdk-qpkg-development-kit/creating-a-qpkg-package-using-qdk/creating-a-simple-qpkg-package
# QNAP SDK docs: https://edhongcy.gitbooks.io/qdk-qpkg-development-kit/content/

# You will need the QNAP SDK, https://github.com/qnap-dev/QDK
# Download the package and put it on your NAS
# SSH into the nas and go to the directory where the package is located

# Create the QNAP build evnironment

The-Running-Dev

using System;
using System.Runtime.InteropServices;

public class FxHook:IDisposable {

	const int nBytes = 5;

	IntPtr addr;
	Protection old;
	byte[] src = new byte[5];

The-Running-Dev

if ($env:TEAMCITY_VERSION) {
	# When PowerShell is started through TeamCity's Command Runner, the standard
	# output will be wrapped at column 80 (a default). This has a negative impact
	# on service messages, as TeamCity quite naturally fails parsing a wrapped
	# message. The solution is to set a new, much wider output width. It will
	# only be set if TEAMCITY_VERSION exists, i.e., if started by TeamCity.
	$host.UI.RawUI.BufferSize = New-Object System.Management.Automation.Host.Size(8192,50)
}

function TeamCity-Message([string]$text, [string]$status = 'NORMAL', [string]$errorDetails) {

The-Running-Dev

<#
Save to:  Create-Kavita-Structure.ps1
and run it with: .\Create-Kavita-Structure.ps1 -sourceDir 'DriveLetter:\PathToBooks' -kavitaDir 'DriveLetter:\PathToKavitaWatchedDir"
If sourceDir is not specified, assumes current directory (.)
If kavitaDir is not specified, assumes @Kavita under the current directory (.\@Kavita)

To test this without making any changes: Create-Kavita-Structure.ps1 -whatIf
#>
[CmdletBinding(SupportsShouldProcess = $true)]
Param(