hh-lohmann

Understanding Command-Line Arguments: Flags, Options, and Beyond

Disclaimer: ChatGPT generated document.

When working with command-line programs, one of the first concepts you encounter is the idea of passing inputs directly to a program at launch. These inputs control behavior, configure execution, or provide data. While many developers casually refer to all such inputs as “flags,” the reality is more nuanced.

This article provides a clear, structured understanding of what these inputs are actually called, how they are categorized, and why the distinctions matter—especially for developers building robust CLI tools.

hh-lohmann

The 23 Gang of Four Design Patterns (Cheat Sheet)

• The 23 Gang of Four Design Patterns (Cheat Sheet)
  • Abstract Factory
  • Adapter
  • Bridge
  • Builder
  • Chain of Responsibility
• Command

hh-lohmann

{
  "title": "Takeout API",
  "discoveryVersion": "v1",
  "ownerName": "Google",
  "version_module": true,
  "resources": {
    "exports": {
      "methods": {
        "get": {
          "flatPath": "v2/{service}/exports/{exportId}",

hh-lohmann

<?php
function randomPassword( $len = 8, $ucfirst = false, $spchar = false ){
	/* Programmed by Christian Haensel
	 * christian@chftp.com
	 * http://www.chftp.com
	 *
	 * Exclusively published on weberdev.com.
	 * If you like my scripts, please let me know or link to me.
	 * You may copy, redistribute, change and alter my scripts as
	 * long as this information remains intact.

hh-lohmann

#!/usr/bin/env bash

# https://gist.github.com/BobbyRyterski/7a511b96ece47655b17d
# based on http://stackoverflow.com/q/14471692

readonly BASE62=($(echo {0..9} {a..z} {A..Z}))

base62_encode() {
  local out=
  for i in $(bc <<< "obase=62; $1"); do