Never gonna happen:

* Port our API to graphql. Or even make it just vaguely rest-compliant. Or even just vaguely consistent.
* Migrate from mysql to postgres. Or any sane database.
* Switch codebase from PHP to... well, anything else.
* Teach coworkers to not commit passwords, API keys, etc.
* Teach coworkers to write serious commit messages instead of emoji spam
* Get a silent work environment.
* Get my office to serve better snacks than fermented quinoa spinach bars and raw goat milk kale smoothies
* Find an open source IDE with good framework magic support. Jetbrains, I'll give you my left testicle if you join the light side of the force.
* Buy 2x3 equally sized displays. I'm using 6, but they're various sizes/resolutions.
* Master Rust.
* Finish building my house. I completely replaced the roof, but still have to dig out a cellar (to hide my dead coworkers).
* Repair/replace the foundation of my house (I think Rust is easier)
* Get slim and muscular.

Realistically:

* Get a comfortable salary increase, focus more on platform infrastructure, data design, coaching
* Get fat(ter). Eating, sitting, gaming, coding and sleeping are my hobbies after all.
* Save up for the inevitable mental breakdown-induced retirement.

Currently working on the privacy site CMS REST API.

For the curious ones, building a custom thingy on top of the Slim framework.

As for the ones wondering about security, I'm thinking out a content filtering (as in, security/database compatibility) right now.

Once data enters the API, it will first go through the filtering system which will check filter based on data type, string length and so on and so on.

If that all checks out, it will be send into the data handling library which basically performs all database interactions.

If everything goes like I want it to go (very highly unlikely), I'll have some of the api actions done by tonight.

But I've got the whole weekend reserved for the privacy site!

Absolutely loving the Slim 3 PHP framework. It's extremely simple, fast, and easily extensible. And nice use of dependency container.

A Website where the user alterts us about a defect on his printer.
There are predefined categories (things like error messages in the printer display, issues with the prints, issues with paper jams, issues with noise and so on) maybe around 10 to 20 categories.
They decide which fields are shown when the user selects it.

Should I do a Dropdown? List field? Radio buttons?

Tech: PHP, Slim Framework, fontsawesome, resulting in a mail sent to our ticket system to pre-fill form items to avoid 1st level support...

So a few months ago I decided to use Slim Framework for the smaller projects. I chose it mainly because of the number of the recommendations here when I asked for help. The other reason is the PHP version of our server (which we can't change unfortunately). Everything about Slim is pretty awesome. It's easy to use and stuff - but without virtual hosts, I can't run multiple sites written with it on our server. The last uploaded one always wins in selecting vendor and config paths, and so the older ones want to use those new paths, too. This generates a lot of errors in the log and of course, we can't load completely any sites but the last uploaded one. We've tried everything until now, so guess we need a workaround.

I just found out that PHP Slim framework is same as Node.js Express!
Am I right?