Here's a tip to caffeinated-beverages lovers.

People often make this mistake with coffee.. They take a cup of coffee after lunch and expect it will make them productive and concentrated immediately. That's BS. Wait for the pee.

Digestion takes ~27% of your body energy molecules [ATP], so you will anyway be sleepy.

When you ingest a cup of coffee you ingest a warm beverage. The warmth will most likely make you sleepy and the sleepiness might last 5 to 15 minutes.

Caffeine in the coffee acts as diuretic - it makes your kidney filter blood more aggresively. As a result 20-40minutes after ingestion you will want to pee.

When you want to pee it's an obvious sign the caffeine is working. Now you should be productive.

Brain [cerebrum] uses glucose molecules for energy rather than ATP, like the rest of the body does. So for the best effect:
- have lunch
- have coffee with sugar during or right after the lunch [do not drink coffee if your stomach is empty!! Ulcers, gastritis, refluxes - that's your future if you do]
- wait ~30 minutes or until you pee
- go to do your work.

This way you will not be working sleepy and your brain will have enough pure glucose to operate on [sugar is just 2x glucose molecules bound together]

I just realised that I've been experiencing a lot of stress and frustration over the last couple of months. I also realised that these feelings of dread and existential anxiety stem from my heavy use of Ubuntu. So I ended another agonizing 3 hours of trying-to-get-internet-access-again-so-I-can-get-some-fucking-work-done and managed to blow off some steam without causing too much property damage. Then I sat down and thought about it. And you know what? I hate Ubuntu.

With Window$ I can at least get some work done without having to write my own network drivers because the current ones do not function when the day of month is a prime number or some shit.

Passed my fucking Type Theory exam!
This course gave me stomach ulcers during the semester but I am done with it finally...
I just wanted to share with someone. :)

Sometimes my hatred for code is so.. overwhelming that I think I need a sabbatical or should even stop altogether.

Let's face it. All code sucks. Just on different levels.
Want to go all bare metal? Love low level bit fiddling. Well, have fun searching for concurrency, memory corruption bugs. Still feel confident? Get ulcers from large C/C++ code base already in production, where something in the shared memory, function pointer magic is not totally right?
So you strive for more clean abstractions, fancy the high level stuff? Well, can you make sense of gcc's template error messages, are you ready for the monad, leaving behind the mundane everyday programmers, who still wonders about the scope of x and xs?

Wherever you go. Isn't it a stinking shit pile of entropy, arbitrary human made conventions? You're just getting more familiar with them, so you don't question them, they become your second skin, you become proficient - congrats you're a member of the 1337.