Fake Compiling - Free Online | LittlePrank

After opening it, the terminal begins to output the compilation log line by line: compiling the source code of each module, linking dynamic libraries, generating executable files, occasionally inserting yellow warnings or red errors, and the rhythm is almost the same as the real construction process. The log content, compilation "project name" and speed can all be customized, and they can even pretend to be the construction site of a well-known open source project, so that people who know the industry will feel that "this project is not small" at a glance.

Logging is a false output from front-end rendering that does not actually compile or run any code, and does not consume CPU; you exit when you close the page. If you want to act naturally, you can open it while your colleagues are halfway through building and pretend to be "Why did I take so long to write this project?" or open it on the conference room projector to create a busy atmosphere of "development is advancing."

It is suitable for performing a busy scene in front of programmers that "another big project is compiling". It is also often used as a warm-up picture for technology sharing or a prop to demonstrate the construction process in developer videos; for people who "fish", a never-ending compilation interface is the most confident shield.

Small reminder: Fake compilation can scare people for a while, but don't use it repeatedly to avoid real work delivery; it's okay to have fun occasionally. Using it as a shield for "I'm busy" for a long time will easily backfire. Sooner or later, colleagues will discover "Why do you compile it for so long?" No output."

Fake compilation tools allow the terminal to scroll through the logs of module compilation and link library, occasionally popping up a few warnings to create a busy feeling of "compiling large projects", and programmers believe it.