Profile_bird

Hey there! ConverterX is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What are you doing? Join today to start receiving ConverterX's tweets.

Already using Twitter
from your phone? Click here.

ConverterX

  1. Vacation over, still out. Sorry.9:53 PM Oct 2nd from web
  2. Apologies to the people sending feedback I fail responding to: I'm on vacation, preparing for vacation, and office firefighting in between.5:09 PM Aug 5th from web
  3. I need to address the entire "bad DOM" use case I tried to throw out the window a few days ago -- but I'm closing shop for the day.5:33 PM May 9th from web
  4. Fixed that one, only to find a new problem in one of the earlier test cases. I'm starting to doubt this will ever end.5:25 PM May 9th from web
  5. The hypothetical scenario has materialized all right -- looking for a fix.4:00 PM May 9th from web
  6. Yay, the code now works well with my test case -- but I need to test for another, currently hypothetical, scenario before I cross that out.3:34 PM May 9th from web
  7. Ok, fixed a couple more bugs with hierarchical processing, but still have one to go before I finish the current queue.2:46 PM May 9th from web
  8. ...and then I proceeded to delete it. Excellent efficiency.1:00 PM May 9th from web
  9. Although I did take the time to identify the DOM issue today, I thought it was more fun to publish an "Odds and Sods" page than fix that.5:31 PM May 8th from web
  10. This is taking way longer than anticipated, I decided to release minor version 0.8.6 ahead of time in order to fix a nasty bug.12:38 PM May 7th from web
  11. Remember the single point of failure I was talking about? It produced false positives. I'm back to handling stuff I thought fixed days ago.3:56 PM May 6th from web
  12. Three hours of implementing logic related to preferences, saving preferences, loading preferences, preference icons and whatnot preferences.3:35 PM May 6th from web
  13. Ended up implementing a fallback mechanism for bad DOM. A preference for forcing legacy conversions is now the next logical step.5:49 PM May 5th from web
  14. Managed to narrow down the DOM issues to a single point of failure; everything else now triggers an exception.3:44 PM May 5th from web
  15. While investigating this I found some DOM issues which can potentially create problems, so I'm thinking about creating a call home feature.2:52 PM May 5th from web
  16. Good thing I didn't rush to release, I found a couple of more bugs. One down, the other will need to wait.11:17 AM May 3rd from web
  17. One last hiccup later, it finally seems I'm actually done with it! Not releasing today though, I really need to test this through.5:00 PM May 2nd from web
  18. Almost done, I only need to trim a bit of unexpected fat which seems to appear out of nowhere...2:53 PM May 2nd from web
  19. I'm finally on the right track with the usability thing, this is seriously annoying.1:24 PM May 2nd from web
  20. I was unable to make it on Tuesday. I'm seriously contemplating releasing as-is tonight.1:44 PM May 1st from web