Tech Notes From The Trenches

“It’s just a web page. ”

“It’s just a text box.”

“It’s just an email notification.”

I have heard and read so many of these. “It’s just a… ” you name it!

This usually comes from someone who wants you to be 10 times more optimistic about the task at hand than you would be. Programmers are inherently optimistic. So there is no need for more optimism.

We, as software engineers, need to explain to clients why it’s not “just a web page” or “a text box” or an “email notification.” For example, web pages need to be cross-browser compatible (ie. Firefox, Internet Explorer, Safari and now.. Chrome on both Mac and Windows)

There are a lot of aspects that we consider and clients don’t. That’s why they pay us to do it. It’s always positive to explain these aspects when presenting an estimate.

Always be realistic about your estimate. Don’t let the “It’s just a…” influence your estimate. Follow a process. Separate the task in sub-tasks. Estimate effort for each sub-task. Add up your estimate.

And most importantly, support your estimate with your expertise. You will always get the “12 hours?!? I thought it would take 2 hours.” from a client or boss. Stand behind your estimate and defend it with facts and your expertise.

I work on a Mac with Aptana. Sometimes Aptana crashes and then, after restarting it, it shows this error when I try to access my application:

Errno::EPIPE in Site#home

Showing layouts/_banner_headers.html.erb where line #11 raised:

Broken pipe

The line doesn’t matter. The problem is that Webrick continues to run even after restarting Aptana. So, when you go to http://localhost:3038/ it is actually accessing a ‘zombie‘ Webrick. Not the one you last launched.

Here is the solution:

1. Fire up a Terminal

2. [etagwerker@gesell trunk]$ ps aux | grep ruby

etagwerker 22930   0.2  2.0   165156  84312   ??  S     2:53PM   0:48.88 /usr/local/bin/ruby -e p(Process.pid.to_s) -e load(ARGV.shift) -I … etc…

The first number is the PID

3. Kill the zombie process

[etagwerker@gesell trunk]$ kill -9 22930

4. Restart your Aptana.

Assuming you already have a tumblr account, like http://ellens.tumblr.com/

1. Go to your DNS manager (eg. http://GoDaddy.com)

2. Login and go to the DNS total control panel

3. Add an ‘A’ record that points your subdomain

(eg. ‘your-cool-subdomain-name’ or ‘tumblr’) to 72.32.231.8 – if you want to have your-cool-subdomain-name.ellens.com or tumblr.ellens.com

4. Save that configuration

5. Go to your tumblr page (eg. http://ellens.tumblr.com/)

6. Click on ‘Customize’

7. Check ‘User a custom domain’

8. Add your custom subdomain (eg. http://tumblr.ellens.com/)

9. Click ‘Save’

This is pretty simple.

Very important note: Please give it time, 1 to 24 hours. I forgot about this and I freaked out because I was getting the “We couldn’t find the page you were looking for.” error message. I gave it 15 minutes and then it started working.

Also, keep in mind that http://etagwerker.tumblr.com will redirect to http://tumblr.etagwerker.com after you do this. You can change it back at any time.