Break's over

I finally took some vacation, which explains why I haven’t updated the blog recently.

I looked at this blog in a new light upon my return. My tone was getting negative. It’s time to fix that. Apparently, I was more tired than I realized.

Let’s look at an example of good packaging:

The image shows the back of a teabag with text “LIFT HERE” and a graphic showing the teabag in a cup with a numeral 1 and another graphic with the text “3-5 MIN.”

[Read More]

Hiring process gaffe

I once submitted an application to a firm that specializes in computer security, and was granted a screening teleconference with a technical recruiter. I was told to expect an e-mail about progress of my consideration for the position on the following Tuesday, which e-mail never arrived. I sent the technical recruiter an e-mail to ask about progress, and got an excuse. Five days later, I got an e-mail from the recruiter which stated that the firm had “decided to move forward with other candidates at this time.”

[Read More]

Naming for the future

How we ended up here: There is never enough time.

Software evolves over time. Example: When writing the software, a developer creates a simple object and calls it Provider. Later, there’s a need for another object quite similar to Provider, so the harried developer takes most (but not all) of the attributes of the object Provider and creates a class (which contains the original object). Which class the developer also calls Provider. There’s no time to think of another name, and even if there were all the time in the world, the developer might not see a need to apply a better name.

[Read More]