Running Puppy
This puppy has nothing to do with this post whatsoever.

Last Friday I announced some “website tweaks.”  Since then a paid subscriber ((As opposed to a free subscriber)) reiterated a feature request. ((Thanks Marc!)) As a paid subscriber, he is able to calculate an unlimited number of ratings so that they all show up on a single page.  Basically, he wanted to be able to see the dollar value for a particular permanent partial disability percentage at the same time as a rating.

This isn’t the first time I’ve wrestled with the problems in creating such a feature.  There are several problems with incorporating this feature into the calculator’s page.

  1. The rating calculator and the dollar value of permanent disability calculators cannot be open at the same time.
  2. The rating calculator does not require the date of injury, just the age of the injured worker.  Without the date of injury, the website cannot properly display the dollar value of a permanent partial disability percentage.
  3. When a paid subscriber has performed more than one rating calculation on a page, the website cannot decide which rating string to convert into the equivalent number of dollars.

This exact feature had been suggested by other users in the past. ((And even some competitors!!!))  My original thinking was that trying to accommodate this feature request would involve too many unknown variables.  After giving the matter some more thought, here’s what I’ve come up with:

  • Paid subscribers benefit from improved print formatting. Basically, I’ve created a special file that changes the way the calculator page looks when a paid subscriber is printing.  ((The special file is actually just some CSS to optimize page for printing.))  Paid subscribers benefit from having the calculator page streamlined specifically for printing.
  • Paid subscribers can have more than one calculator open at a time. This one feature probably addresses 90% of this user’s concerns.  If you’re able to keep both calculators open at the same time, it should be easy to perform a rating and then turn the percentage into a dollar value.
  • Paid subscribers receive automatic calculations of dollar value of ratings. When a paid subscriber performs a rating calculation, the “Dollar Value of Permanent Disability” calculator automatically opens and the dollar value of the rating is automatically calculated.  The user will still have to adjust calculation to account for the year of the injury.  However, this is probably the most elegant solution to this issue.

Mr. Road Warrior, Esq.
Road Warrior, Esq.

Appearances, whether for a hearing or deposition, require additional equipment, preparation, and forethought.  Here’s what I carry with me when I’m scheduled to appear.

  • Cell phone
    • Phone numbers for the office, destination, and client programmed in the day before.
    • Photocopier code programmed into the phone.
    • Includes calculator. ((Since workers’ compensation is really just math.))
    • Alarm.  When parking at a meter, set the phone’s alarm for 5 minutes before time expires.
  • GPS
    • Address and phone number of destination programmed in the day before.
  • Money
    • $5 is the bare minimum, in case I need to be across a bridge on short notice.
    • Quarters for parking.
    • Bills for photocopies.
    • Copy cards.
      • Every time I use a copy card, I write the date and amount remaining on it in permanent ink.
  • BART tickets
    • I consider $5 a minimum, in case I need to be in S.F. on short notice.
  • Dictaphone
    • Extra batteries.
  • Leather bound folder
    • Legal pad
    • PD chart
    • Mini-rating manual for 1997 and 2005 ((I’ve created my own “mini-rating” manual.  Its basically comprised of excerpts from the 1997 and 2005 manuals.  Carrying this obviates the need for the 100+ page manuals.))
  • Settlement documents.
    • You never know when a case might unexpectedly settle.
  • Record release forms.
    • You never know when a settlement might fall through.
  • Backpack

Previous “Road Warrior Checklists”:

For some reason MS Remote Desktop refuses to work intermittently.  Every 90 days, to be precise.  Like clockwork. ((Photo courtesy of Laffy4k))

Among the myriad of incompatibilities between Microsoft’s various products and operating systems is the mind bending error thrown by Remote Desktop.  Remote Desktop should work between any version of Windows starting with XP.  Even when using full versions of MS operating systems, you will likely still get this error:

The remote computer disconnected the session because of an error in licensing protocol.

89 days and counting...
89 days and counting...

There are two reasonable ways around this.

  • First, if you’re not an advanced Windows user, you should really try TightVNC.  Its small, free, open source, uses very little bandwidth, and is easy to install and use.  It will do probably 90% of everything Remote Desktop will do.  As a bonus, you won’t have to monkey with it every 90 days.
  • Second, if you are an advanced Windows user and are comfortable using Regedit, there is another option.  If you’ve never heard of Regedit, you really really should not use this option.  If your Windows registry settings get fouled up, and it is incredibly easy to do, you can kiss your Windows install goodbye.  In any case, the solution is to go to, “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing” and delete everything under that heading.  The only downside is that this must be performed every 90 days.

FYI, this second ridiculous work around is from the official MicroSoft website!  You’d think that if your product stopped working every 90 days you’d, you know, try to fix it.  Instead their game plan is to actually suggest users delete vital parts of the operating system.

For what its worth, I use a combination of the two solutions.  I fire up Regedit every 90 days so I can use Remote Desktop and I use TightVNC when I can.

It was not very long ago I announced 100 registered users for this site.  Today there are more than 200 registered users of this website. ((Photo courtesy of Mark Strozier.))  Since that time:

Pass Go, Collect 200
Pass Go, Collect 200

Wikipedia has this to say about the number 200:

  • 200 MeV is the temperature of quark-gluon plasma phase transition.  ((Of course it is…))
  • An HTTP status code indicating a successful connection.
  • The sum of dollars given in the classical Monopoly game to a player passing Go.

Changing themes for a WordPress website is incredibly easy.  However, sometimes there can be slight problems in the transition.  I had heavily edited and customized the prior theme’s code so that it would be better suited to this website. ((Click this link see what the prior theme looked like.))

Fixing things
Fixing things

Changing the website’s theme has involved a few small tweaks ((Photo courtesy of CharlesThompson)) :

  • For about four days the Articles section was merged with the Blog section.  This has been fixed.
  • I’ve found a really great plugin that allows me to insert footnotes into blog posts. ((Cool, no?))  My previous attempts at inserting footnotes manually were either time consuming or incredibly clumsy.  ((A special thanks to Mr. Simon Elvery for writing this great footnote plugin.))
  • I’ve made minor alterations to the current theme – background colors, menu ordering, etc.
  • Some people were separating their WCAB “legacy” number to ADJ number searches by semi-colons, rather than commas.  I believe there’s really no sense in fighting users.  ((Unlike a certain “web-based” electronic adjudication management system…))  If a slightly different method makes sense to users, go with it.  I’ve adjusted the WCAB “legacy” number to ADJ number search function so that you can separate by semi-colons or commas. ((Or both!))
  • In printing out some Average Weekly Wage calculations, I discovered to my dismay that this website looked terrible when you tried to print it out.  Worse yet, the website header, sidebar, and other navigation information took up nearly a page.  This meant that a printout of a calculation might span two or more pages.  I’ve since fixed this using some particularly cool CSS. ((Well, my definition of cool, anyhow.))