My thoughts as an enterprise Java developer.

Friday, February 13, 2015

Literary Hex

? = 2B || !2B

Thursday, February 20, 2014


CodeCombat: "Learn to Code JavaScript by Playing a Game"

Tuesday, January 14, 2014

Preferences/Settings should be minimized

Allowing a user to change how an application works by only going into preferences/settings should be avoided.

  • Most users won't even look there so features will be underused which is a waste of development resources.
  • Try to prompt the user to change their preference when they do a related action. i.e. if there is a preference for the number of items to show on a page and the user changes the dropdown to show a different number of items on the page then ask the user if they would like to update the preference to the new value.
  • When prompting the user, avoid making the user click an extra time. Instead of doing a popup, just add text that prompts the user.

Tuesday, December 10, 2013

More interesting wait screen

I have seen many wait screens that do the job but are boring. I think it might work a lot better to make a wait screen that displays something interesting. Maybe draw a fractal or present a simple game. If there is something interesting, the user shouldn't mind the wait as much.

Friday, December 06, 2013

U.S. Supreme Court to decide whether software can be patented | Reuters

U.S. Supreme Court to decide whether software can be patented | Reuters: "The U.S. Supreme Court on Friday agreed to decide on a key software industry issue of which kinds of computer-related software are eligible for patent protection."

Thursday, October 17, 2013

The type of work that I like to do

I like working on detailed, complex, and/or interesting problems on a product that I know well, has a large codebase, and has to support high load. I call those “guru-level” problems.

Tuesday, October 15, 2013

Change comments to logs?

It seems that almost all of the time, comments in a method work better as logging statements.

  • The log statements still give clues to the developer about what is happening
  • The log statements also give that information to someone looking at the logs
  • Since log statements will be seen more, they are more likely to to kept current