The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
(Long story, barely related because I've managed to link computer manufacturing with a "script"):
At my first job straight after college, I wrote a utility that gathered hardware/software information, and could output it to a database, and/or leave behind that information in a file for future tech support reps to use.
We licensed that software to a large(ish) US company that built computers for Fortune 500 companies - it became part of their "build script" - essentially a checklist of items that had to be done before a computer could be sent to a customer. Whenever a computer was brought back with a problem, the file my utility wrote is one of the first things some other software looked for to present to the person running some diagnostics.
I was once brought in to visit what is essentially the manufacturing floor - I don't know how many tens of thousands of square feet it was, but that was pretty impressive for the 20-something year old I was back then. Larger than your average Costco store.
The most surreal thing however is when I was introduced to some people as the guy who wrote the utility everyone on the floor was using and familiar with. I swear some of these guys came up to me to shake my hand like I was some sort of rock star. Apparently it saved them a tremendous amount of time - not hard work, but incredibly tedious and repetitive, so they were very happy to see that part of their job being automated.
Just some coming trends I've been getting hints of that some of you may not have become aware of.
1. NoOps. Let's face it, Agile is OK, Lean is a little better, but ultimate having absolutely zero 'friction' between the developer and the customer is where we need to get. NoOps addresses this issue by ultimately pushing the development process to the customer, who knows his requirements better than anyone. You take requirements from the customer, complicate them significantly using core NoOps processes, and send them back to the customer to implement.
2. C++ 21 is going to introduce the most powerful language feature yet:
A 400GB template library of every possible program implementation will be part of the new standard template libraries. This is somewhat offset by the minimum 16 hour build time and minimum 20GB program size.
3. C# Darkode. Your company's code is the family jewels and if you lose control of that to hackers or competitor's espionage all of your work and investment will be for naught. The next version of C# will make your code immune to such problems by introducing so many syntactical options that no one can understand your code even if they have access to it. With a mazimum of 2.85% of your code being actually related to the problem solution, finding the important lines of code will be essentially computationally infeasible in medium to larger code bases.
4. Containertainers. Managing all of your containers and their options is now becoming a serious challenge to many companies. Containertainers are containers for your containers and their configuration operations, simplifying your container deployment and management process. Work is already under way on Containertainertainer technology, in anticipation of projected containertainer deployment growth.
5. PlausDen. In order to avoid potential legal and financial blow-back from software bugs, your company needs to develop solid plausible deniability strategies. The upcoming AllPacks package manager is a key aspect of PlausDen planning, insuring that you never actually understand more than 1% of the code that you deploy, and hence insuring that no damages can ever be legally proven to be due to failure on your part. The AllPacks manager system is based their patented EDND (enormously deeply nested dependencies) technology.
6. The UE is considering legislation making it illegal for software companies to require developers to understand the tools and languages they are using, calling it 'part of a discriminatory and elitist past.'