The goal of this exercise is to have the candidate call out issues with a simulated pull request creating a new ETL application.
A good code review reference: https://www.morling.dev/blog/the-code-review-pyramid/
- Continuously receive messages from an at-least-once delivery message queue
- Apply a message transformation to each message
- Append the transformed message to a database
- Log any errors to stdout
- Continue to run and retry on network connectivity or other errors
The goal of this exercise is to find issues that linters would not easily identify. Most linters will find no warnings or errors with this code.
Linters including go vet and default linters for golangci-lint find no issues with this code.
├── go.mod
└── main.go