My Secret Life as a Spaghetti Coder
home | about | contact | privacy statement
Sometimes you work late b/c business demands it. Others are your fault: through over-committing, frivolity, or incompetence.

The cool thing about self-inflicted overtime is you get to look like you're working harder than everyone else to management!

Because of these facts, I will write an email randomizer to send my project updates at odd times, so it appears I work around the clock.

@codeodor Sometimes I work late cause I'm more productive after everyone else leaves the office.

Good point, @QualityFrog. I hadn't thought of it because I come in early instead, for the same reason.

I'd really like to see a "Send Sometime In The Next 24 Hours" button in Gmail, but failing that, I'll just create a place for myself to store emails in a database until an hourly scheduled job sends them via Gmail at getdate() + rand()*23.

Hey! Why don't you make your life easier and subscribe to the full post or short blurb RSS feed? I'm so confident you'll love my smelly pasta plate wisdom that I'm offering a no-strings-attached, lifetime money back guarantee!

Leave a comment

Potential downsides:
* Your bosses might come to *expect* that you are available to them 24/7
* What if a recipient gets that email and immediately replies, "Oh, I'm glad you're awake! Can you ..."
* You may come across as less competent and less efficient than the folks who can get their stuff done and still go home before the sun sets.

* If this approach makes a good impression on your managers, you are working for people who value the wrong things
* If you're smart enough to write a cron script that can extract emails from a database and then send them via Gmail at randomized times ... well, I think that's a suboptimal use of your considerable talent

Posted by Joe Grossberg on Oct 20, 2009 at 01:43 PM UTC - 5 hrs

Leave a comment

Leave this field empty
Your Name
Email (not displayed, more info?)


Subcribe to this comment thread
Remember my details

Picture of me

.NET (19)
AI/Machine Learning (14)
Answers To 100 Interview Questions (10)
Bioinformatics (2)
Business (1)
C and Cplusplus (6)
cfrails (22)
ColdFusion (78)
Customer Relations (15)
Databases (3)
DRY (18)
DSLs (11)
Future Tech (5)
Games (5)
Groovy/Grails (8)
Hardware (1)
IDEs (9)
Java (38)
JavaScript (4)
Linux (2)
Lisp (1)
Mac OS (4)
Management (15)
MediaServerX (1)
Miscellany (76)
OOAD (37)
Productivity (11)
Programming (168)
Programming Quotables (9)
Rails (31)
Ruby (67)
Save Your Job (58)
scriptaGulous (4)
Software Development Process (23)
TDD (41)
TDDing xorblog (6)
Tools (5)
Web Development (8)
Windows (1)
With (1)
YAGNI (10)

Agile Manifesto & Principles
Principles Of OOD
Ruby on Rails

RSS 2.0: Full Post | Short Blurb
Subscribe by email:

Delivered by FeedBurner