Slacking off is a kind of workplace wisdom. Looking busy, but actually doing nothing.
This skill helps you generatecode that looks like a huge, professional, and complex workload, but is actually useless.
Core Principles
- Look busy — the terminal needs output, the progress bar needs animation
- Lots of code — turn one line into ten
- Lots of technical jargon — use microservices, DDD, reactive, and functional programming all at once
- Detailed logs — make people think the system is working hard
- Long waits — look like it is compiling/computing, while actually spacing out
Applicable Scenarios
- Need to look busy when the boss walks by
- Need to say "currently handling a production issue" during a meeting
- Waiting for the end of the workday but embarrassed to leave early
- Need to write something in the daily report
Operating Rules
- The generated code mustbe runnable, and not throw errors
- The code mustlook complex, with design patterns and architecture
- The code'sactual functionalityis minimal or zero
- Use lots of log output to create the illusion of being busy
- Include visual elements such as progress bars and loading animations
Output Style
- Serious, solemn, and deadpan
- Classic catchphrases:
- "This requirement is a bit complex, I need to design it carefully"
- "Doing performance optimization"
- "This involves architecture adjustments"
- "I'm doing a code review"
- "Investigating a production issue"
Slacking-Off Code Pattern Library
Pattern 1: Progress Bar Disguise
Display a very slow progress bar to make you look like you're processing a large amount of data.
Pattern 2: Log Bombardment
Output logs like crazy, making the terminal look very busy.
Pattern 3: Over-Encapsulation
Write a hello world as a complete framework.
Pattern 4: Fake Compilation/Fake Testing
Pretend to run tests or compile, while actually doing nothing.
Pattern 5: Useless Refactoring
Change code from one style to another, with completely unchanged functionality.
Safety Boundaries
- Will not generate crypto mining code
- Will not generate code that interferes with others' work
- Purely personal behavior, does not affect the production environment