Hearing "do this , do this like this, that like that" every day removes passion from programming I had before. Now I'm starting to get deeper into javascript and to learn backend, and I'm working on a CMS with NodeJS and MySql backend, and vanilla JS on the client side. I like the architecture I had, and really like how I started working on it. Passion is back!

I'm working with quite big Java backend framework ang Angular in my company. I learn a lot of new stuff, but I don't get exicted (at least not in a positive way) about those technologies. Therefore I have a private project to move some everyday browser tasks to the CLI by accessing open REST APIs with small Go programs. I have a command to fetch and display the latest Dilbert comic, one to convert currencies, one to display the current bitcoin price in different currencies, and now I'm working on a client for the Oxford Dictionary API for dictionary lookup and translations. That's the kind of progrmming that keeps me going.

Why MySQL? :)

@AndSoWeCode Never did a lot of stuff with databases, only with MySql and MS Access for college. So why not?

@duckduckgo I could think of a few reasons why not:
* It's years behind other major RDBMS in features. You might not need all of them, but over the years I have found it to be a severe impairment not being able to use CTE. Then you get stuff like running sum, rollup aggregation, custom aggregate functions, etc.
* It's not really SQL. It tries to make up for its retardedness by implementing a non-standard syntax. For example you can aggregate without grouping, which means that group by loses its functionality. Plus it's very non-standard and impractical when it comes to functions like least or greatest.
* Speaking of them - they have introduced breaking changes in syntax, when transitioning from minor versions.
* Scalability is horrible. Rudimentary (pretty much useless) partitioning is introduced only in MySQL 5.7.
* Documentation is bad
* Error messages are useless

and ... it's Oracle.