Technical Support
The following page contains support guidelines for my paid subscribers.
Communication Channels
If your question/comment is related to one of my articles, then please comment on the article.
If your question/comment is not related to some specific article, you can comment on chat.
If you are an Engineering Leader wanting your team(s) to practice TDD and you’re considering a group subscription for your team(s), then book a free call with me.
Response Times
Generally, I respond to questions within 1 working day.
When I’m out of the office, you’ll still receive my articles (they are scheduled in advance) with an Out-of-office notice, in which case I generally respond when I return back to work.
Note: If it happens that more than 5 days passed and I still didn’t answer your comment, please send me a message with a link to the comment:
Support for Sandbox Project
Answers to questions you have about my articles
Review and feedback for your GitHub Sandbox Projects
Support for Real Life Project
I cannot access your Real Life Project, please don’t include any details about your Real Life Project in any communication (not allowed due to NDA reasons)
So if you do want me to support you with a challenge on your Real Life Project, then replicate that problem within the Sandbox Project, and then ask me
What support is NOT included?
Tech Stack / Debugging / Troubleshooting is not included. It’s your responsibility to ensure that your system compiles, that it runs, that tests pass, etc.
I assume you have programming experience in your Tech Stack. You may need to learn (via tutorials) the basics of Docker, Pipelines, WireMock, Testcontainers, and Pact. I won’t be able to help you get something working on your GitHub Sandbox Project; instead, I expect that you’ll get it in a working state, and my role will be to review it and provide guidance if you can do it better.
Questions?
If you have any questions about the above, you can send a message: