comment_out

Came across this, it just slammed two words together

instrument/adjective in·stru·men·t/ad·jec·tive

    an instrument related to a keyboard in that it is played rather than written
    "an instrument/adjective keyboard"

My work mainly involves setting up internal enterprise applications.

- The standard testing package

- Manually setup dependency injection. Generally a flow like config=>databases=>models=>routes=>server.

- https://github.com/gorilla/mux for routing and https://github.com/swaggo/swag for documentation

- As for HTTP frameworks I just use the standard package and I really enjoy https://github.com/sirupsen/logrus for logging

We use IIS. I really wanted to use go so, I found a way to run go applications on top of it. That was not fun to figure out, but I can make use of the windows authentication underneath IIS. Required a custom module that forwards some headers to my go applications. Also the version of IIS we use doesn't even support http2 which sucks.

I've been using kitty running through WSL/VcXsrv. Which has been an overall better experience than any native windows terminal I've used. Had to setup a few scripts to get everything working 'quake' style, but it works.