Feb 09

Quickfix Model of Develoment

I love new programming toys and this week is a good one for those. Ever since I laid the foundations for Dehydra I’ve been dreaming of a world where I can quickly lookup a piece of code(say something that someone complains about on IRC), fix it, get it reviewed and pushed in the most efficient manner possible. Seems that the pieces are finally falling into place.

  1. I want quick semantically aware code lookup via DXR. And guess what, there is progress in that direction.
  2. I want to DXR to provide a link to edit the code. Bespin looks like the most promising candidate for editing.
    As an aside, using canvas to do text editing is badass. I salute devs who are crazy enough to prove their point by reimplementing something (hopefully better) from scratch using an approach that hasn’t been tried before.
  3. I want my changes to be saved as a diff into bugzilla. I want that to be two way so I can edit existing patches and save them as new bugzilla attachments.
  4. From there I’d like a commit feature in bugzilla so the patch would go through try-then-push cycle that Jesse described.
  5. Having all this inplace would make it trivial to integrate random features such as crash stack trace navigation or Pork automagic refactoring.

Now I’m sure that most of us would still run Emacs and other desktop editors for longer development tasks. But just imagine being bored with a computer at a webcafe, boring friend, etc and having the ability to quickly jump into in the development process as easily as logging into webmail.

Feb 09

Security with Dehydra

When I wrote the initial prototype of Dehydra I pondered how long it would take before it’s adopted by security guys. Unfortunately, until now take-up has been non-existent. Grep and Perl still seem to rule in that community even though the plain text approach restricts the range of possible security scans.

Normally I would be tempted to rant on how grep is convenient yet limiting. However Ben Kurtz discovered Dehydra for security scans and did a great job explaining the issues involved. Thanks to Georgi for linking me to Ben’s post.