TECHNICAL REF

The third one among "the coder tricks" (see first and second one)

They say I am a master to document myself. Do not be afraid of me, nothing about hypnosis, copycats or teleporting. Mastering technical reference today means simply to be able to solve problems by following principles and suggestions documented by others. In few words mastering how to document yourself is the ability to not reinvent the wheel every day... Reuse past documentation is undoubtly a good quality to own and nevertheless a good RAD practice!

Here, in this website, I offer some references you can browse and reuse like I continue doing (Please be aware that the list doesn't want to be complete and the display of one and the other material it doesn't have secondary meanings or purposes):

CLASSIC ASP

ASP 2.0 Unleashed

PHP

PHP for the Web, Larry Ullman
PHP Advanced and Object-Oriented Programming, Larry Ullman
Modern PHP, Josh Lockhart
PHP, the website https://php.net
PHP Tips https://phptips.net

Tcl/tk

Tcl/tk doc https://www.tcl.tk/doc/
Tcler's Wiki https://wiki.tcl-lang.org

Unix

OpenBSD FAQ https://openbsd.org/faq/
Mastering FreeBSD & OpenBSD Security

Security

The art of deception, Kevin Mitnick

Open Source

Open Sources, DiBona Ockman and Stone

Software Engineering

Code Complete 2nd Ed., Steve McConnell
Software Engineering Modern Approaches, Braude
Software Engineering Principles and Practice, Vliet
Multiparadigm Programming, IEEE
Software Engineering Code and Professional Practice, IEEE

Project Management

UML Notation Guide
Scrum Master in Under 10 min, Youtube
[A first reference to write IT contracts]
[A second reference to write IT contracts]

And the fun

Designing interactions, Bill Moggridge
Media Semiotics: an introduction, Bignell
The medium is the massage, M. McLuhan
A theory of computer semiotics, Andersen
Bill Gates, Heller Robert