Prolog Cookbook
Documenting, testing, and moduling
Game Trees
Tictactoe
Graph Traversal
Depth First
Breadth First
Transitive Closures
Route Finding
Cycles With Tabling Iterative Deepening
Puzzle Solving
Wolf Goat Cabbage Buttons and Lights
Classical Logic
Truth
Conjunction
And Intersection Inner Join Product Series
Negation
Not Difference Fill Values De Morgan's Law
Disjunction
Or Union Outer Join Sum Parallel
Implication
Proofs
Equivalence
Postgresql
Commands
Delete
Update
Insert
Select
Filter
Aggregate Functions
Configuration
Other Commands
Set Explain SHOW
Concurrency
Read Write Conflicts
Graphs
Types
Jsonb
PL/pgSQL
Inter Process Communication
Pipes
Data
Visualisation
Metadata
Microdata schema.org
Action
Achieveaction
Creativework
Game
Local Business
Organization
Place
Event
JSON-LD
Html5
Dublin Core
Systemd
Unit Service Sockets
Go
Packages
Server
Pgx
Error Handling
Types
Pointers
Concurrency Oriented Programming
Input Output
Javascript
Jsdoc
Jasmine
Node
Browser
Html Tools
CSS
Color Style Guides Layout
Functions
Landmarks
Lighthouse
Hugo
Assets
Modules
Menus Branch
Leaf
Bash
Shellspec
Shebang Builtins
Mapfile Readarray
Echo
Read
Logic
Pattern Matching
Indexed Arrays Associative Arrays
Appending Deletion Iteration
Core Utilities
grep sed awk
Date
External Utilties
jq
nc
hq
Git
Tree
Parameter Expansion
Defaults Slicing Transforming Trimming
Linux Utilities
Concurrency
Concurrency Control
Understanding locks
7 tips for dealing with locks
Something I learnt the hard way by getting the computer to play games over-and-over and then update the average scores each time was it crashed my Postgresql functions with
ERROR: relation "_states" does not exist LINE 1: SELECT id FROM _states WHERE state = NULL The problem was garbage values were getting returned from queries if their table was being updated, and the solution was: