Home Notes Other

Seen on Stack Overflow E-mail
Saturday, 14 May 2011 14:44

The question was removed so I couldn't get the entire text, but I was able to capture the gist of it.


On professionalism E-mail
Saturday, 26 February 2011 12:08

Recently, for work on a client's site, I had to contact a representative at a company whose service I had to integrate into the client's site.  Here's my e-mail to the representative:

Hi Mr. P-,
My name is Pranshu Arya, I am developing a website for a group of --- who have subscribed to your --- services.  I was wondering if you would be able to answer a few technical questions for me about the service you provide.

In his infinite wisdom this douchebag decided to forward me the message from his technical person, including what he wrote to that person.  The response I received from this person was (interesting part in bold):

Hey Pranshu…
Here are your answers: Please see below.
On Thu, Feb 3, 2011 at 1:40 PM, C  P wrote:
Hey… do you mind answering these quickly for me to talk to this guy later?
It is not worth wasting time on a call with him just yet but I want him to be able to see that it is an easy back end solution so he gives the thumbs up to the money guy…

That was the first e-mail.  After that I had to send a second, asking technical questions, and the response came:

On Wed, Feb 9, 2011 at 6:53 PM, C P wrote:
We got a signed contract back today from these guys so I guess they are worth the time

Is it just me or is this extremely unprofessional behavior from someone who considers themselves a "professional" and represents the public face of a company?

Skeleton project outline E-mail
Sunday, 21 November 2010 14:25

As a project manager, and especially as a freelancer, you have to organize projects into smaller, more manageable subprojects, so that when you bill your clients you can provide sufficient level of detail about how much time was spent on what task.  At the same time, you don't want to go overboard with the specificity (i.e., "changing header background color from #fff to #fafafa", or "Updating footer text from xyz to abc").  Indeed, many small tasks will require less time to perform than to keep track of if you insist on being overly meticulous, which not only costs your clients extra money but also results in more headache for you in switching back and forth between tracking tasks and actually performing them.


The taxonomy I have arrived at that works for me, I believe, achieves a good balance between the two - specificity and ease of use.  I like to structure my projects so:


Project name

  • Research and setup
  • Work performed
  • Testing
  • Revisions
  • Meetings

Within each of these categories you can define as many (or as few) subcategories that you feel is appropriate for the scale of your project.  For a small catalog-type site, for example, I would stick with just these five categories, whereas for a larger-scale project I could expand it to something like:


Project name

  • Research and setup
    • Asset collection - quality and completeness check
    • Database design and setup
    • Reviewing project requirements
    • Development, test environment, and version control setup
    • Other research


  • Work performed
    • HTML/CSS programming
    • Client-side programming (JavaScript, jQuery, AJAX)
    • Server-side programming (PHP, Ruby on Rails, MySQL)


  • Testing (and deployment)
    • Cross-browser testing
    • Unit, functional, and other business logic testing
    • Production environment testing
    • Deploying to demo or production environment


  • Revisions (and troubleshooting)
    • Styling revisions
    • Functionality revisions
    • Other revisions
    • Fixing others' mistakes
    • Fixing discrepancies between local and remote environments


  • Meetings
Designers vs. developers - pretty funny E-mail
Friday, 12 November 2010 00:06

Infographic of web designers vs. web developers


Page 3 of 14