snapvolumes

Unfortunately using pry-nav with pry has some limitations that ruby-debug doesn't: 1. It doesn't seem to work in some cases (like putting binding.pry in a Proc.new { ... } 2. On Windows, binding.pry works when directly embedded in a ruby script, but when put into code such as a Rails controller or model then several things don't work properly ('whereami' will show it doesn't have context.. though this works fine on Linux)

For these reasons, I still find ruby-debug better for actual debugging (when step/next are necessary) and pry better for inspecting state at a particular moment in time (but I can just call pry from the ruby-debug in that case)

SnapVolumes is hiring two Windows kernel developers. We are located in downtown Los Altos, CA (close to VMware headquarters and Palo Alto).

We are a funded early-stage startup (< 5 engineers) with unique technology, solving lots of interesting and challenging problems in virtualization space, with lots of room for career growth and plenty of financial upside.

We are happy to talk with anyone with Windows kernel experience (ideally experience writing mini-filter drivers but it isn't required). We are willing to hire H1Bs or remote developers, but we'd prefer people to relocate to the San Francisco Bay Area (we can cover relocation expenses).

Email: jobs@snapvolumes.com