Every statement printing debug messages should ideally be a test case in your unit tests. However, let’s be honest — when no one is watching, we all do quick and dirty tricks to validate or debug our code. But is there a better way than cluttering your codebase with log statements? Spoiler alert: Yes, there is! Embrace logpoints in Visual Studio Code.
After getting our feet wet with a simple AI Assistant in the previous post, let's Continue (pun intended) with a more sophisticated solution: set up VS Code with the Continue extension. We will explore the main features through very simple examples, and I hope you will have a sense of how these tools can enhance your developer workflow.
If AI assistants are still new to you, you might be living under a rock. Chances are, you already have a subscription to Github Copilot or something similar. But why bother setting up your own local AI assistant? Can it really compete with a commercial product such as GitHub Copilot?
