Hi All, this is Shardul here - I am the co-founder of Videobug.<p>https://bug.video<p>We are super excited to share Videobug with you. Videobug records run time code execution so that developers can watch it line by line as frequently as they want, right in their IDE. It takes away the pain of recreating exact conditions that led to a bug and saves developer time in every bug squash.<p>Parth (my co-founder) and I have worked on multiple production grade applications in startups and enterprises.<p>We used Logrocket, Sentry, and Datadog for logging and found ourselves adding more logs after a bug is found.<p>Adding accurate logs required disciplined engineering and collaboration across teams. Time to connect these logs to what’s wrong in the code, took quite sometime.<p>Videobug logs everything automatically. We are super psyched to launch our offline version. We plan to launch a fully self hosted version in 4 weeks from now, which will allow you to record and replay code executions in your staging and production environments.<p>We are looking for product feedback.<p>Here is a 2 min demo explaining how to use Videobug.<p>https://www.youtube.com/watch?v=U53IQifMt54<p>Join our discord channel to share your feedback or in case you need support.<p>https://discord.gg/Hhwvay8uTa<p>P.S. Please note that we collect the following analytics data from your IDE: Your computer hostname, debugging events such as “started debugger”, “fetched exceptions” and “searched for code execution”.
Hi, I am Parth, the other cofounder.<p>Debugging and catching bugs has always been a fun game for me, but as the team size grows it becomes very tidious<p>1. Run into too many “works-on-my-machine-but-not-in-production” cases.<p>2. Logical errors were hard to catch with logging tools. We often added more logs to trace back where the issue was. This involved several production deployments.<p>3. Race conditions were rare and hard to recreate, and remained unresolved for days. Combing through logs for days was frustrating.<p>4. Logging tools offered stacktrace for crashes - we needed to figure what data led to these crashes. This was time-consuming.<p>Adding the links here again to make them clickable for mobile users<p><a href="https://bug.video" rel="nofollow">https://bug.video</a><p>2 min demo explaining how to use Videobug.<p><a href="https://www.youtube.com/watch?v=U53IQifMt54" rel="nofollow">https://www.youtube.com/watch?v=U53IQifMt54</a><p>discord channel<p><a href="https://discord.gg/Hhwvay8uTa" rel="nofollow">https://discord.gg/Hhwvay8uTa</a>
This looks neat! I just watched Alan Kay's recent talk at GOTO Conference "Is Software Engineering Still an Oxymoron" and this tool reminds me a bit of the CAD -> SIM -> FAB part of his talk:<p><a href="https://youtu.be/D43PlUr1x_E?t=2034" rel="nofollow">https://youtu.be/D43PlUr1x_E?t=2034</a>
I think this is a very interesting concept. Will definitely shorten the REPL cycle from reporting a bug to recreating it in the code. I can see this being useful in QA and staging environments. Looking forward to the self hosted version for security reasons.