| Some fragmented programming-related notes, not meant as introduction or tutorial
Data: Numbers in computers ·· Computer dates and times ·· Data structures
Wider abstractions: Programming language typology and glossary · Generics and templating ·· Some abstractions around programming · · Computational complexity theory notes · Synchronous, asynchronous · First-class citizen
Syntaxy abstractions: Constness · Memory aliasing · Binding, assignment, and such · Hoisting · Closures · Context manager · Garbage collection
Language specific: Python notes ·· C and C++ notes · Compiling and linking ·· Lua notes
Algorithms: Dynamic programming · Sorting · String search · Sequence alignment and diffs
Sharing stuff: Communicated state and calls · Locking, data versioning, concurrency, and larger-scale computing notes ·· Dependency hell
Design concepts: Entanglement, Decoupling; Information Hiding, Inversion · Design patterns
Teams and products: Programming in teams, working on larger systems, keeping code healthy · Benchmarking, performance testing, load testing, stress testing, etc. · Maintainability
More applied notes: Optimized number crunching · OS-level notes · File polling, event notification · Webdev · GUI toolkit notes · StringBuilder
Mechanics of duct taping software together: Automation, remote management, configuration management · Build tool notes · Packaging · Installers
|
What people usually mean with syntax-fu is clever expressions.
...often too clever, overly compact things you will not be able to remember the details of or reasoning for later.
In the name of maintainability, such compactness is generally discouraged, in favour of a more verbose-but-more-readable style,
especially if that is no less efficient yo execute.
Unless everyone knows the trick, of course.