"By the Time"

What do you think about the future? Will my future life be better, worse, will it be the same now? Is this hot, flat and crowded world becoming "the position only in space"? People are hoping that many of our current problems will be solved by 2100.

Clean water is one of the most precious resources. Demand for water will be ten times. Actually, there may be a serious shortage. Is water worth more than oil? Can you find a way to protect our most precious resources by 2100?

Energy comes from a variety of energy sources, such as wind, air, sun, hydrogen fuel, nuclear fusion. Cars stop using gasoline and use more efficient detours. Public transport is expected to play a greater role in our daily life

The boundary between entertainment and education disappears. "Education and pleasure" is the preferred learning system. The story of parents who have a backpack with a 60 pound book will be a source of entertainment for children. Learning is done "on demand" and focuses on the specific needs of the global employment market.

Air travel is safer and faster. The computer uses a sensor to operate the aircraft. This prevents the sensor from colliding with other aircraft and natural phenomena. The problem of the convoy (SST) ground is solved by the engineer and the passenger aircraft moves at Mach 0.1

Robots will replace people in the manufacturing industry; however, the demand for personal services is high. But by 2100, the company replaced the phone tree with a manual operator. Local products such as foodstuffs, clothing items, furniture that feel "handmade" will again outperform the better, cheaper products produced by robots.

What experts can not predict is whether we will be a more kind and considerate person. Do we understand that violence and war can only lead to pain and despair? Can we share Earth resources? Would you stop looking at the differences and start seeing common goals?

Sensor (N) - Sends a signal to a measuring or control device with light, temperature, radiation level, or a movement sensitive mechanical device.

I waste time on public transportation, waiting for the meeting time, waiting for my coffee time and have no meaningful time to see it (you know this). The time of the "emergency" response of a person, the talk time remains silent or muted, and time selects the task with the highest priority and many other tasks. I know that I need to change the schedule. I know what I can do more at no additional cost. I opened my eyes. My monthly performance evaluation and code quality evaluation are extremely rare, and there are about three pull requests a day. I do not believe in the plan that "everything will be true without you." For that reason, we recommend that you carefully consider the code rather than scrolling down. There are examples that failed due to PR scrolling, but it sounds like another big article

For businessmen, writing unit tests means more code and more writing time. More code and more time means more cost. And for inefficient businessmen. Remember, the company's mission is to reduce IT costs rather than increasing costs. By writing test tools to increase the value of software, IT is considered a cost center, not a profit center. Please let the software developer write twice the code with the same number of functions in each iteration. This is meaningless from a business point of view.

Software is never perfect. Those who can understand the problem in a timely manner and deal with it when a problem occurs are those who write software. However, the developer's time is precious. They should not be asked to take care of their work. It will take a considerable amount of time to refine the software, fix errors found, add new features, and solve performance problems. Therefore, from an engineering, human or economic point of view, there are some supplementary software that can grasp the state of business-critical software in case of problems. When combined with an appropriate and meaningful error message, this capture state can provide a failed context. It is much easier to analyze the root cause when retrieving a snapshot from a failure.