[EndedSojourn76]

Technical books 1.) Have the LOWEST resale value out of any another other published material. Versions of new software outpace the updates and changes and thusly are placed on sale and bargain bins.

Even authors complain about changes and versions in the foreword.

2.) Reinventing the wheel is common practice. If one is unable to see the same replicated patterns in technological adoption on only look at ideological standards of industrialzation. From Mainframe and Dumb Terminals.. to Cloud computing and updated hardware.

3.) Keep a set of decent cookbook style recipes and in the meantime go help a Rosetta Stone project website rebuild/remake a algorithm or pattern in the "new" format.

4.) Trends are meaninless and create new complications later down the road. More so with relying on libraries that were rewritten from the ground up to "just work". Time to rewrite your ASM to C to Perl to C+ to Java to C++ to Python to .Net to Euler to Go to Rust.

5.) Stay off the hampster wheel of training if you haven't been replaced by an offsite worker it just means the automation system isn't ready yet.

Find out why LISP is was always going to be a ultra expensive waste of time. Find out why Plan 9 was never made sane. Stay away fron the insanity of being controlled by market forces.