Me: *opens a terminal in front of parents and starts a build script from command line. Logs start rapidly flooding the screen*

Mom: *whispers to dad proudly* “look at how much she has worked. Look how fast the lines are running on the screen!!

I didn’t wanna burst their bubble by explain them that their child is NOT doing any rocket science, and is something even they can do(maybe better).
So I responded back with a fake serious tone
“Yeah it’s all code.”
If only they knew what I was actually doing...

>Be client
>Have an issue with incredibly slow webpage load time
>Blame memcache issues

So... I look into the problem. Yes, the page either loads up fast, or times out. So, into the logs I go. Webserver is fine (except the timeout), PHP though... Error log is fine (just notices), but slow log shows the issue is the database (of course... its always the database... ugh)

So, checking the database, there is one ugly query that seems to be an issue. 5 joins and a huge where condition.

So I run EXPLAIN on the query and... Proceed to bang my head against the wall.

OF COURSE ITS SLOW YOU FU******, NONE OF YOUR TABLES HAVE ANY INDEXES.

What do they expect when the database has to always go down the whole table and do everything in memory, until it runs out and has to dump it all on disk and work with it there.

Ugh... Some clients...

So there's that project with my coworker. We splitt up the classes, 10 to be implemented by him, 10 by me.

Fast Forward to 4 weeks before deploy.
Coworker: Your stuff logs a lot of stuff. It's not very clear and a liiittle to verbouse. 5 entries per second? Too much!
Me: Okay, you're right. Let me fix that.

2 Days later I look at his logs at runtime. He logs EVRY SQL statement and their results! In a batch that processes a 10'000 of customers!
He points out: That's useful stuff and it's not that much. It's needed for debuging.

My face: 😦

If I add a log statement on every small thing it makes it look like my application is running REALLY fast