Have you ever felt that your day was completely packed from morning to night. Waking up at six, going to campus, doing group assignments, attending student council meetings, then continuing coding for a side project until three in the morning. That day you felt like the most productive person in the world.

But the next day, you wake up late with a heavy head, a weak body, and your motivation suddenly disappearing without a trace. You feel empty. So empty that even replying to someone's chat feels like too much effort.

In the world of cloud computing, this is called your system experiencing unscheduled downtime aka dying suddenly because your server overheated.

Many people are very proud of hustle culture. They think humans are machines that can run 24/7 without stopping. But even servers like AWS or Google Cloud have what is called an SLA (Service Level Agreement). They promise an uptime of 99.9 percent. Why not 100 percent? Because engineers are fully aware that no system in this universe can stay on continuously without maintenance. It definitely needs time to restart, clean up junk logs, or update software.

If sophisticated multi-billion dollar servers need time to breathe, why do you force your brain to work relentlessly without mercy?

A personal SLA is extremely crucial. You must set boundaries on when you can be accessed by work or other people, and when you must be completely offline.

If you never set up scheduled maintenance for yourself (for example getting enough sleep, playing games all day, or just lying down while thinking about how absurd this life is), your body will forcefully take that downtime. And trust me, forced downtime has a much worse effect than scheduled downtime.

When you force yourself to work even though your energy indicator is already red, you will be prone to creating bugs. Ranging from bugs in your code that cause your program to crash during a demo in front of your lecturer, to bugs in the way you communicate that make you easily angered and fight with your partner just over picking a place to eat. All of this roots from one thing: your mental server is overloaded with requests.

So how do you determine an SLA for yourself?

First, learn to say no. This is like a rate limiting feature in an API. If your friend requests help doing their assignment even though you yourself are currently stressed, just immediately give a 429 Too Many Requests response. No need to feel bad. If you do their assignment, your own server will break, and they will not want to take responsibility to pay for your mental recovery costs.

Second, prepare a staging environment for your emotions. Do not immediately deploy your anger or sadness feelings to production (other people). If you are annoyed, write it in your phone notes, play a fighting game, or vent to a wall. Let your system process those error logs in the background until you are completely calm, only then do you talk to the person.

Third, acknowledge that lying around is part of the optimization process, not laziness. When you are just quiet doing nothing, your brain is actually running garbage collection. Cleaning up junk thoughts and organizing your memories more neatly so tomorrow you can think more clearly.

From now on, if someone asks why you did not reply to their chat or did not join the hangout on the weekend, just say you are under server maintenance.

Khay