1. Not everything can be declarative. Navigating tree models (file systems, DOM, decentralize relationships) is an inherently imperative task. This doesn't sto

1. Not everything can be declarative. Navigating tree models (file systems, DOM, decentralize relationships) is an inherently imperative task. This doesn't stop developers from forcing declarative abstractions over imperative concerns. It just means a foot gun at maintenance time or passing the buck to somebody else. 2. Legacy paradigms will continue to live, no matter how obsolete or harmful, so long as developers reliant upon those paradigms continue to find employment. Such developers will continue to find employment so long as such paradigms remain in formal education criteria. 3. Software hiring is extremely biased. Such bias will continue until software is perceived as generally harmful by people outside of software hiring. Until such time any attempts to limit bias will be met with maximum hostility, as such only benefits experienced and generally confident incumbents. 4. It is common in software to hate on credentials of any kind except a computer science bachelor's degree, which then becomes a credential. This line of thinking is prolific and extreme enough to view credentials as a form of incompetence regardless of what such credentials are or what they mean, thereby increasing bias. 5. Software will continue to swell and slow so long as the goals of the developers are out of alignment with the end product. Claiming product first goals by developers is not a solution if not reflected by the tool chain and processes. 6. The older the web gets the more costly it becomes to add text content to a commercial webpage.