When it comes to software development, sometimes the program is too complex. Developers may think of 100 different user scenarios, but they know there are still 100 scenarios that they did not anticipate. One amazing thing about Windows is that when the program cannot run, it will prompt you with the lowest level error message, although Windows doesn’t know why (because there are 10 million developers).
But developers themselves know what aspect of what they are developing, and based on this error message, they can gain great insights (for 99.999 users, this error message is worthless, but important to developers), so developers link your computer to their push server and send themselves an email with this error message.
But if the developer’s program has 100 types of logic, such as logic 30, logic 80, logic 90, logic 65, etc., all using exactly the same steps, it is possible that exactly the same errors will occur. Therefore, the developer requires you to write the process, commands, and scenarios you use as clearly as possible, so that the developer can quickly identify the problem and find it out during the next upgrade.
How do you write clearly and where do you write it? How is it transmitted to the developer? It is sent to the developer through the form shown in the picture and the push server. All users who use this form use the push server prepared by the developer for you. A needs to use this server to send emails, and B also uses this server to send emails. The developer does not know who gave it, and only when you leave your email address can the developer reply to you.
If we see a prompt that clearly tells you where the problem lies, then this prompt is something that developers have long considered (scenario prediction). Follow the prompt and it will definitely be correct.
But because the developer’s thinking is not rigorous (or he has never seen such an operation before), the prompt given makes the user completely unsure of how to handle it. This prompt is given to you by Windows, and you can’t ask anyone on Earth except the developer. Even if you ask the developer, they must provide a clear usage environment and operation process.
The code is a repeated call relationship. Our SWTDO has 30000 to 40000 lines of code, but only 10m, while Dassault’s software has 15GB. It is impossible to flip through millions of lines of code from scratch with just a prompt given by Windhos. You must know where the prompt popped up in order to refine the problem.
We use macro programs, where did all the 91 errors come from? Because the person who edits macros spends most of their energy on coding rather than operating SW, they never expected you to do this, so the prompts you encounter are given to you by Windows, not by developers
Pay attention to distinguishing between prompts, whether they are human prompts or Windows prompts. (Let’s say, even if there are some prompts that are artificial, you still feel like they are not human language. The reason is not because the software author, but because those A translators don’t understand.). Please note that TDO is a domestically produced original, we are not a copied software, not a D-version software. We have written it in Chinese, and you have a high probability of understanding it.
There are also some users who never look at the prompts. This kind of clumsy and clumsy person is only suitable for doing manual labor and mechanical design. It’s too difficult to do, so quickly switch careers. Unless you know how to ride a horse, working for thirty years is just running errands. Even if you climb up, you will inevitably be poked in the spine by someone
Professional knowledge is by no means the strongest weapon in the mechanical industry, meticulous! Extremely meticulous, I guarantee you will surpass all your peers
For programmers, many people think that implementing functionality is difficult, but this is only one aspect. On the other hand, developers need to anticipate any malicious actions from all users, which is the biggest workload.
The simple operation result you see is that developers may need to write 10 times or 20 times different code to deal with multiple scenarios.
What does it mean that Tesla’s autonomous driving has 400 million codes? Scene prediction.
If autonomous driving is tested on Chang’an Avenue, it is definitely the unmanned vehicle with the highest accident rate. In an environment where everyone follows the rules, algorithms do not have the ability to learn.
I have never seen the crazy lane grabbing of a long x taxi, nor have I seen a Changying tricycle driving in reverse. The software doesn’t know whether the person coming ahead is a living creature or just a shadow.
The computer thought, “Huh? There are cars that drive upside down?” It must have crashed into something