Phew... okay, I think it's time for me to go to bed. I just coded two webpages in HTML/CSS/JavaScript/PHP, everything works great and I also added some smooth animations when you hover over parts of the page :D

Basically... this last part (a.k.a. "smooth animations") was useless to this exercise, but... y'know... i was interested in experimenting it.

The more I code, the more I think I should be a design guy, lol.

Anyways... jeez, I really should go... it's 2:50 AM right now @.@

Goodnight y'all... 💙
( ¯﹃ ¯๑) zzZ...

Overengineering. Finding the right point between overdesign and no design at all. That's where fancy languages and unusual patterns being hit by real world problems, and you need to deal with all that utter mess you created being architecture astronaut. Isn't that funny how you realize that another fancy tool is fundamentally incompatible with the task you need to solve, and you realize it after a month of writing workarounds and hacks.

But on the other hand, duct tape slacking becomes a mess even quicker.

Not being able to promote projects. You may code the shit out of side project and still get zero response, absolutely no impact. That's why your side projects often becomes abandoned.

Oversleeping. You thought tomorrow was productive day, but you wake up oversleeped, your head aches, your mind is not clear and you be like "fuck that, I'm staying in bed watching memes all day". But there's job that has to be done, and that bothers you.

Writing tests. Oh, words can't describe how much I hate writing tests, any kind of. I tried testing so many times in high school, at university, even at production, but it seems like my mind is just doesn't accept it. I know that testing is fundamentally important, but my mind collapses every time I try to write a single fucking test, resulting in terrible headache. I don't know why it's like that, but it is, and I better repl the shit out of pure function than write fucking tests.