s/Weather/Whether/ I think this post highlights something important - programming and automation have a very broad applicability, and it doesn't matter what in

s/Weather/Whether/ I think this post highlights something important - programming and automation have a very broad applicability, and it doesn't matter what industry you work in, there's likely some aspect of it that would benefit from some understanding of what computers do well and being able to take advantage of that. Generalised, industry agnostic versions of examples from the article. * Applets that integrate with your tool of choice. Practically native to the world of Finance, showcased here with modelling and animation tools, but the principle could be applied to any industry tool with an API. Video editing, CAD, Word Processing - every industry has their boilerplate or composable tasks which could have some assistance from scripts and extensions that fit your use case outside of what the programme would natively support. * Workflow automation We see here the 'pipeline' of storyboards becoming assets, becoming scenes, becoming films - however every job has processes, documents to review, authorisations and oversight that needs to occur. A friend of mine once said 'Just use JIRA'. It doesn't matter what it is, track with JIRA. In contrast. a colleague of mine once opined: "having a system that passes documents around is the easy part. Having a system that allows all the right people the right access at the right times, enforces all the restrictions you need it to and asserts that all requirements are met and tests are passed is hard. And I believe him. He's currently the architect on a £20m project that is essentially just a workflow/pipeline system. * Tiny one-off tasks One of the key parts of why I recommend 'Automate the Boring Stuff with Python' [0] to beginners is the books central thesis: anyone can program, anyone can benefit from programming. It shows how creating small, throwaway scripts can greatly reduce some manual tasks. I think the world would be a less stressful, more efficient place if more people knew about shell commands, regular expressions etc. I've seen people spend hours, even days painstakingly doing tasks that could have been done in seconds by a well placed `sed` or a short perl script. To that end: * Applying programming concepts to everyday life. Notably here we have dependency trees shown in the form of the workflow tools, but 'compilation time' checks could be useful in so many industries that currently don't use a lot of technology. Change a part of a document that is depended on by other documents/sections? Flag that the downstreams need review. In short, this article gives a good answer and some excellent examples to the question 'why should I learn to program' or, even, 'why should everyone learn to program? why should we teach coding in schools?'. [0] - https://automatetheboringstuff.com https://automatetheboringstuff.com