SiddharthShyniben

import socket
import threading
import argparse

HOST = "0.0.0.0"   # Server binds here (0.0.0.0 = all interfaces)
PORT = 5000        # Default port


def handle_client(conn, addr, clients):
    """Handle incoming messages from a single client and broadcast to others."""

SiddharthShyniben

# lab_blackjack.py
# Multiplayer "no-dealer" Blackjack over a shared E: drive.
# Everyone runs the same script; state is coordinated via E:\<session_id>.json
# [Tech: shared-file state machine, cooperative polling, Windows file lock, Fisher–Yates shuffle,
#  blackjack evaluator (soft/hard aces), turn arbitration]

import json, os, sys, time, random, tempfile, getpass
from datetime import datetime
from typing import List, Dict, Any

SiddharthShyniben

As in sysexits.h, but in a (sometimes) more accessible place. Formatted painlessly in Vim

---

According to style(9), it is not a good practice to call exit(3) with arbitrary values to indicate a failure condition when ending a program. Instead, the pre-defined exit codes from sysexits should be used, so the caller of the process can get a rough estimation about the failure class without looking up the source code.

The successful exit is always indicated by a status of 0, or EX_OK. Error numbers begin at EX__BASE to reduce the possibility of clashing with other exit statuses that random programs may already return. The meaning of the codes is approximately as follows:

Exit Code	Description

SiddharthShyniben

A router in 108 89 83 bytes

(a,b,c=_=>(a.find(p=>b=p.path.exec(location.hash))?.render(b),c))=>onhashchange=c()

Shortened with inspiration from @Posandu

const route = (a,b,c=_=>(a.find(p=>b=p.path.exec(location.hash))?.render(b),c))=>onhashchange=c();

SiddharthShyniben

// add or remove classes. classify(element, '+class-to-add -class-to-remove other-class-to-add')
(a,b)=>b.split` `.map(c=>c[0]=='-'?['remove',c.slice(1)]:['add',c[0]=='+'?c.slice(1):c]).map(([d,e])=>a[d](e))

SiddharthShyniben

Unix wars

If you know who originally wrote this, please tell me so that I can credit them. I found this in an old hard disk.

---

A long time ago, at an installation far, far away...

It is a time of intra-system war, as forces of the User Alliance struggle to break the iron grip of the evil Admin Empire. Now, striking from a

SiddharthShyniben

class Backtracking {
  constructor(height, width) {
    if (width % 2 === 0) {
      width += 1;
    }
    if (height % 2 === 0) {
      height += 1;
    }

    this.width = width;

SiddharthShyniben

Ninja code

Learning without thought is labor lost; thought without learning is perilous.

— Confucius

Programmer ninjas of the past used these tricks to sharpen the mind of code maintainers.
Code review gurus look for them in test tasks.
Novice developers sometimes use them even better than programmer ninjas.
Read them carefully and find out who you are – a ninja, a novice, or maybe a code reviewer?

SiddharthShyniben

‎‎‎‎‎‎‎‎‎‎‎‎‎‎‎‎‎‎ 

SiddharthShyniben

<div class="drop">
	<div id="drag" draggable="true" ondragstart="event.dataTransfer.setData('text/plain', null)">
		Drag me!
	</div>
</div>
<div class="drop"></div>
<div class="drop"></div>
<div class="drop"></div>