antipasta
Re:How to write a bug report that actually gets resolved – and why eve...
on Thursday October 20, 2016 @10:31AM (#12752519)
Just dawned on me that a demo might be better than just linking to the marketing site :)
Here is a BugReplay recording demonstrating an ebay security vulnerability that we recorded awhile back:
https://app.bugreplay.com/shared/report/3efa632d-5b51-45f1-a...
Re:How to write a bug report that actually gets resolved – and why eve...
on Wednesday October 19, 2016 @03:10PM (#12746761)
After years of vague bug reports at various places we've worked, my 2 cofounders and I built a tool that records video of a bug, alongside network traffic and JavaScript logs.
That way even with a vague description, and no steps to reproduce, we can get a much better idea of what a customer is trying to report to us.
Would love for anyone interested to check it out: https://www.bugreplay.com
Re:Vim for Humans
on Monday October 17, 2016 @02:33PM (#12727838)
I started out trying to go plugin free since I wanted to avoid bloat, but eventually gave in once I found plugins that eased bottlenecks in my workflow with a barebones vim.
Though I love the plugins I use now, I do agree that it makes sense to be fairly comfortable in a plugin-free vim before installing a ton of them.
I wrote a blog about this topic a month or so back:
http://blog.bugreplay.com/post/149712686514/how-i-learned-to...