I get through tough devDays like this:

1. Brew coffee more black than a serial killer's soul in the midst of the Gotthard Base Tunnel without electricity in the midnight during a solar eclipse.

2. Flush the blackness down the throat.

3. Load the Playlist: Mostly Death/Doom Metal

4. Put on over-ear headphones (the ones your coworkers can see from a distance telling them to fuck of with their questions).

5. Code through without pauses (except for releasing piss)

6. If you're paid by the hour: $$$profit$$$

I fucking hate december. It's as dark outside as in a hobo's ass standing in a tunnel during a solar eclipse and there is "love" and "friends" everywhere.
Time for some nordic doom metal.

was pretty excited to see the annular solar eclipse, pretty cloudy today, wish I could adjust the sun's z-index 😐

Everyone argues about the perfect date, so I searched and found it using complex machine learning, a lot of trial and error, and too much alcohol:

'#76ab%Y%Y@98:%M%D%h@()%m&%m%Y%D%Y€¥$¢%M%h+%s-%s%%'

Where:
- %Y stands for one number of the last year
- %M stands for one number of the following month
- %D stands for one number (09 are two numbers for example) of SQRT((CURRENT_DAY^7)/3)
- %h stands for one number of the hour next evening(12h system)
- %% stands for either 7 or 3, 7 means that the hour(%h) is a.m., 3 means that the hour is p.m.
- %m stands for the minute the next solar eclipse will happen
- %s stands for one number of the second you will hate yourself to have this system implemented.

How to use it im 3 simple steps:

1. Implement it using ???
2. ?????
3. Profit?

For weeks the excitement had been going about the Eclipse, I guess because they don't know what it is like... I had the luck for one project, I don't think I want to see it again... 😧🙃😏