Subj : Re: Old computer
To   : TALIADON
From : boraxman
Date : Mon Jul 04 2022 22:52:08

 TA>  bo> Standards go beyond those ratified by documents, such as ISO standard
 TA>  bo> RFC, but also incorporate social expectations and practices.
 TA> 
 TA> Unfortunately, this simply isn't the case in the 21st century. Standards
 TA> and "accepted/subjective practices" are diametrically opposed in almost
 TA> every way imaginable; the days of corporate developers picking their
 TA> preferred tools and "doing it their way" are long gone. This is
 TA> precisely the way it was back in my day - engineers often made
 TA> themselves "indispensable" by using techniques/methods that only they
 TA> were familiar with - and corporations are unlikely to make the same
 TA> mistake again. From a corporate perspective, employees are no different
 TA> from any other kind of asset, and thus should be transparently
 TA> replaceable once they become a liability. Of course, rather than playing
 TA> the "irresistible force" to their "immovable object", creating your own
 TA> business/product is a sure way of avoiding this scenario altogether.
 TA> 

An engineer doing things "his own way" is not equivalent to a company or an industry having its own methodology or techniques.  But this is a little beside the point that I was trying to make.  What we sometimes get is code written in a way that only the developer can understand.  What I was trying to allude to was techniques or practices which are widely know, and can be adopted and adapted to solve particular problems.  For example, a way of using existing tools to create a private internet-accessible file system, or a way of creating and accessing, modifying and appending to registers as an alternative to using Excel.  In short, a kind of "did you know you can build this with tools you've got in your backyard" way of thinking.

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
 * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

.