I’m excited to share the journey of a project that I hope will revolutionize how developers approach and execute code reviews. Still in its early stages, DevSitter is already stirring up excitement in the programming community. The name ‘DevSitter’ is a playful nod to ‘Babysitter’, reflecting its role in assisting developers 😃.
The Genesis of the Idea
It all began with a trend I noticed in various programming groups and communities, including my own. Novice developers often share their repositories, seeking feedback. Such reviews can be time-consuming, with project authors waiting and asking for help that sometimes takes days to arrive, if at all 🙃. This led me to seek ways to streamline the process, giving birth to the idea of DevSitter.
What is DevSitter?
DevSitter aims to be every programmer’s best friend. My goal is to create a tool that provides automatic, instant feedback for submitted projects, accessible to developers at all skill levels. After all, even seasoned programmers need feedback on their projects and insights on what could be improved!
Journey to the Prototype
Creating the first working prototype of DevSitter was a journey with several twists, which I’ve detailed in a video on my YouTube channel. Initially, I considered using tools like ChatGPT for a simple MVP. However, the high cost of scanning projects, limitations due to the size of the source code (especially with classes having thousands of lines), and the inability to analyze connections led me to static code analysis tools.
How Does DevSitter Differ from Other Static Code Analysis Tools?
DevSitter utilizes various tools, scanning and aggregating responses to be simple, clear, and intuitive for the programmer. Its biggest advantage is the lack of any configuration requirement. In the web application, you just submit a repository link and receive feedback! This is beneficial not only for beginners unfamiliar with these tools but also for experienced developers who prefer to save time on configuration and focus on other tasks.
Beta and Feedback
Launching the beta version was a significant milestone. The initial impressions from a closed group of users were very positive, prompting me to initiate a public beta for my Kickstarter backers.
Kickstarter — A New Chapter
I chose Kickstarter to take DevSitter to the next level. Moving from beta to a stable version requires significant work and infrastructure funding. To avoid creating an app that ultimately lacks interest, I launched a Kickstarter campaign as a sort of preorder and concept validation. Check out the campaign here ➡️ DevSitter.app
What Does the Future Hold?
Looking ahead, I see DevSitter not just as a code review tool but as a platform that supports learning and collaboration within the developer community. Beyond traditional code reviews, we aim to provide tips and suggestions on best practices. You can read more about the planned features in my Kickstarter campaign.
In Conclusion
Working on a personal solution always brings many positive experiences. As a former startup owner, I know that sometimes, in the wave of enthusiasm, we can create fantastic tools that ultimately no one uses. Therefore, the community validation that has begun on Kickstarter will decide whether DevSitter enters the market. I’ll be reporting all progress, and I’m eager to hear your thoughts. What do you think about DevSitter? Does it address a real need in the code review and feedback process? I’m looking forward to your insights and suggestions. Let’s connect and shape the future of code review together! See you in the code! 😃
Top comments (0)