Category: Technobabble

By Posted on Posted in Calculators, Free, Open Source, PDRater, Technobabble, Website Updates No Comments Tagged with , , , , , , , , , , , , , ,

In my never ending quest to build the world’s best workers’ compensation website, I’ve made a few upgrades:

  • Upgraded from WordPress 2.6 to WordPress 2.6.1
  • Infinitesimal changes to the theme
  • Adapted a new plugin for WordPress that redirects you directly to the calculator page as soon as you log in

Why keep upgrading WordPress?

Using open source software can be a two-edged sword. On the down side, anyone with the ability to read the source code can figure out the security vulnerabilities. The plus side is that people are constantly working to improve and eliminate those very same security vulnerabilities.

Since people are working on WordPress all the time, it will need to be upgraded all the time. Doing so allows me to take advantage of the latest features and security updates. So far I’ve used WordPress 2.3.2, 2.5, 2.5.1, 2.6, and now 2.6.1.

Why change the theme?

The theme (the “look” of this website) is completely user configurable. Since this website’s launch I’ve been constantly tweaking the look. Minor changes to the color scheme, menu at the top of the website, and how many posts are shown on the blog page.

I work on the theme in order to (hopefully) make the website more aesthetically pleasing and easier to use.

Why the new plugin?

I’d like to make the free registration process as quick and as painless as possible. I’ve had the opportunity to watch a few people go through the free registration process for this website. What I saw was that people were logging in for the first time and were sent to their user page – which looks totally different from the rest of the website. Unfortunately, this caused no end of confusion.

I modified an existing plugin to override website’s default settings to send users directly to the calculator page as soon as they log in.

By Posted on Posted in Articles, Author, Downloads, EAMS, Free, PDRater, Technobabble, Workers Compensation Resources No Comments Tagged with , , , , , , , , , , , , , , , ,

I received a few handouts regarding the new EAMS system while at the San Francisco WCAB yesterday. The WCAB SFO only had a limited number of these documents, so I’ve scanned my copy for everyone else’s benefit.

I also learned some interesting things about EAMS:

  1. Everyone knows that EAMS and the WCAB will reject your filings if you’re not registered with EAMS. Did you know that the Judges aren’t sure if EAMS will reject your filings if the employer is not registered?
  2. If a party brings physical paper exhibits, Judges will only be accepting the most important documents for filing (since the WCAB will be doing the scanning)
    • The parties will be expected to bring any possibly relevant exhibits. Any documents not accepted will be returned to the parties or shredded.
    • Judges will mainly be accepting just permanent and stationary reports.
  3. A party bringing a CD burned with scanned exhibits, will need to submit all medical files and documents which are typically required to be filed with the WCAB.
    • They will will not have the option of only submitting the most relevant exhibits.
  4. For the time being, normal walk through procedures are gone. Any new case activation would not be assigned a Board number until approximately 3 am after the day of submission. Be ready to drop off your walk throughs the day before you want to obtain approval.
  5. The EAMS forms haven’t been approved by the Office of Administrative Law and won’t be mandatory until approved.
  6. For the time being, every Board will have a telephone conference each morning starting at 8 am with their “command center.”
  7. The decision to go ahead with EAMS starting August 25, 2008 was only made on August 22, 2008!

By Posted on Posted in AJAX, Free, Javascript, MySQL, Open Source, PDRater, PHP, Subscription Features, Technobabble No Comments Tagged with , , , , , , , , , , , , , ,

I recently gave a brief overview of my permanent disability and workers’ compensation benefit calculators. In that post I wrote a little bit about how my online benefits calculators work. Since then I’ve posted about my use of javascript, PHP, and AJAX in creating these permanent disability and permanent impairment calculators.

As I mentioned in the prior post in this series, my first few versions of this website and its workers’ compensation calculators did not use MySQL.  The initial versions of this site only saved information – which meant I only had to use PHP to open a file on the server, add an extra line of information, and then close the file.  This had several problems:

  1. Once my website became more popular, it was not uncommon to have more than one user online.  That meant the server tried to open the file – but couldn’t since it was already open.  This caused the program to freak out.
  2. In order to view just a little bit of information, I had to download the entire file.  This got crazy pretty quickly.
  3. Each time the file got larger, it would take slightly longer to open, append with more information, and close.

MySQL is an incredible tool for storing, organizing, and retrieving a large amount of data.   Like PHP, it is also open-source.  This means it is:

  • Well supported.  There are lots of online resources and books to help you learn.
  • Secure.  Lots of people spend a lot of time thinking of ways to prevent security vulnerabilities.
  • Customizable.  You can configure or even rewrite it, if you wish.
  • Interoperability.  You can save it to just about any format – including MS Excel spreadsheets.
  • Free.  Unlike Oracle or any of the MS alternatives, it is totally free.

So, why did I avoid MySQL?  I didn’t want to have to learn a whole new programming language.  I had to learn how to set up a database, tables within the database, how to search for information in a table, how to put information into a table, and how to change information which was already in a table.  There was a lot of trial and error.  I ended up doing some pretty cool things in the process of learning this language.  Some examples:

  • Teaching others some of the basics of MySQL
  • Writing a program for cataloging books
  • Writing several programs which performed various calculations to track invoices, billings, etc
  • Setting up several blogs/websites

The end result of learning this language is a more interactive website.  One of the last incarnations of this site was a version that would show different color schemes, advertisers, and messages depending upon the user.  All of this was made possible by large amounts of data stored in MySQL.

Thus ends my technical overview of my workers’ compensation permanent disability calculators!  If you have any questions, please feel free to email me or leave a comment below!

By Posted on Posted in Javascript, Not Workers Compensation, PDRater, Technobabble No Comments Tagged with , , , , , , , , , , , , , , , , , , , ,
Howie Mandell trying to look hard.
Howie Mandell trying to look hard.

Javascript appears all over the internet. You can be pretty sure that your favorite websites use a LOT of javascript. You see it every time a website creates a pop-up advertisement, sends you an alert, lets you bookmark their page, or interacts with you in some way.

I’ve written some pretty cool (in my nerdy opinion) things in javascript:

  • A blackjack strategy simulator. You tell the program how many decks, when you want to hit, stand, double down depending on the deck count, and it will run through a given number of hands – telling you how much your strategy has won/lost overall.
  • A “Deal or No Deal” odds simulator. The program calculated the average of the remaining unopened suitcases – to compare against the Banker’s offer. It made rudimentary guesses about how much the Banker would offer. There has been some incredible and complex analysis of how these offers are created.
  • A billing program. It had separate timers for different tasks, tallied time, expenses, ability to save reports, and create invoices for different clients.
  • A simple program for tallying points for gin rummy.
  • Several small programs for solving various internet website puzzles.
  • Several small tools which allow me to write other programs or web pages more efficiently.

I’ve written innumerable other mini-programs which either had a very limited or one-time use or which I never developed into an actual program. One example was a program that would help me quickly search muliple ebay auctions and compare the various prices. Another was a Sudoku puzzle solver which I never completed.