diff --git a/doc/httpmock_tutorial.adoc b/doc/httpmock_tutorial.adoc index a24aab3..a2ea467 100644 --- a/doc/httpmock_tutorial.adoc +++ b/doc/httpmock_tutorial.adoc @@ -1,10 +1,6 @@ -= Unit Test Outbound HTTP Requests in Golang += Unit Test Outbound HTTP Requests in Go Erik Winter 2020-07-04 -:kind: tutorial -:public: yes -:language: en -:tags: golang, tdd, http, rest, go-kit In general, when one wants to test the interaction of multiple services and systems, one tries to set up an integration test. This often involves spinning up some Docker containers and a docker-compose file that orchestrates the dependencies between them and starts the integration test suite. In other words, this can be a lot of work. diff --git a/doc/logging-in-golang.adoc b/doc/logging-in-golang.adoc index 7016aff..c9f6cdc 100644 --- a/doc/logging-in-golang.adoc +++ b/doc/logging-in-golang.adoc @@ -1,10 +1,6 @@ -= My Take on Logging in Golang += My Take on logging in go Erik Winter 2021-04-08 -:kind: tutorial -:public: yes -:language: en -:tags: golang, go-kit The subject of logging comes up every now and then, in every group of developers. Apparently it is something to be opinionated about, like code formatting. Or to something complain about, like leaving off the cap of the toothpaste. If only there was a `go fmt` for logging. Or toothpaste.