Skip to main content

Significance of working in the same proximinity

Best Buy and Yahoo have started their own initiative to remove the ability to work from home. Incidentally, for the past few years, I've been a big advocate for autonomous, remote working in teams. Great examples of amazing work cultures including Github and 37signals (Basecamp). In the best conditions possible, we should all be able to trust each other to pull their weight; however, it has become a huge dampener for Yahoo as the culture has become stagnant. It is the gradual deceleration over a number of months that kills the company's ability to innovate and ship great products.

For me, I prefer to work in an office with my teammates, perhaps, this is because in my past experience, I was part of teams shipping software on fast deadlines (3-week projects including design, development, testing, and user acceptance) -- you need that face-to-face interaction to show a number of things
  • confidence in your teammates
  • optimism on hitting targets
  • validity on progression 

If I saw a teammate working late to finish something, I would get back in there, redistribute the workload, and help out. Truthfully, I am not saying I'm an expert in death marches, but I've been in a few to know that instinctive feeling of "do or die"; where you're in the trenches with other teammates, sleep deprived, and clients keep changing requirements. Welcome to the world of software -- this is how it is. There are certainly other ways of shipping fantastic products without much hardwork (or at least it seems that way on the outside) but I truly believe that in order to exceed the expectations of your customers, you need to put in an order of magnitude of effort upfront.  

Bob Fitch is the hero who saved Blizzard Entertainment from uncertainty -- when their customers called Starcraft "Orcs in Space" -- he invested countless hours to rewrite Starcraft so it would go beyond the expectations of its users. Starcraft went on to have a massive legacy -- people in Korea are still playing the game even after a decade.

We can try to sugar coat things as much as possible on tight deadlines but at the end of the day -- we're all here to do the best we can. Sometimes your "best" isn't good enough, which is why it is important to take the necessary steps to set yourselves up for success (even if it means less work freedoms like remote working). This is why I side with Marissa Mayer's decision to all workers to a Yahoo office to get shit done. When Yahoo! emerges as a successful internet technology company as it once was, I'm sure they will give back remote working to specific employees who have proven themselves. For Yahoo!, in an optimistic and determined tone, it's time to go to war.

Post a Comment

Popular posts from this blog

TextMate Tutorial: How to add a Strikethrough keybind to your Markdown bundle

Markdown is awesome for quickly generating Readme's on Github. After looking at other projects using the strike tag, I've decided to create a custom keybind for it in my TextMate Markdown bundle. Here's how:

1) Click the + sign on the bottom left and click New Command.
2) Paste this into the editbox and make sure you name your command "Strikethrough".

For the input field, select WORD in the drop down.
For the output field, select "insert as snippet".
As for the keybind, you can totally map it to whatever you're comfortable with but I chose Command-D as it is the same thing in Microsoft Word.

Cheers,
Jaime

Using Git Hooks: Prepare Commit Message to automatically prepend branch names on commit messages

When you're practicing branch by feature with distributed version control, typically you'll get assigned a ticket or issue and that ends up being your feature branch. Instead of always typing in the branch name in every commit, you can edit your Git hooks (specifically prepare-commit-msg).

Assuming that this is a brand new git repository:

mv .git/hooks/prepare-commit-msg.sample .git/hooks/prepare-commit-msg
vi .git/hooks/prepare-commit-msg

Edit the file by commenting out what was originally in the file and then add this:



Now, whenever you make a commit, it should show up like this in the log:



Since GitHub and Bitbucket both support Emojis inside commit messages, you can do something cute like this



Want more emojis? check out the Emoji Mardown Cheatsheet!

NodeJS Hack Session: MMO Pokemon with NodeJS/WebSockets

The primary focus of this proof of concept is to determine how easy it is to build real-time web applications for all iPad, iPhone, droids, Safari, Chrome users on top of NodeJS (non-blocking event driven server side Javascript platform). The proof of concept was built within 6-8 hours including the following:

Uses Express framework for server side Javascript development (inspired by Rails / Sinatra / Django)Uses EJS for templating language (much like Django templates and symfony) -- allows partials and passing parameters into partials like symfony PHPReal-time chat using WebSocketsArena Queueing System for real-time competitive matchplay using WebSocketsHTML5 AudioCSS3 transitions for all hand cards, tappable cards, transparent panels, rounded corners, drop shadowsFallbacks for Firefox, IEFirefox/IE will fall back to Flash socketIE will fall back to XHR long poll if the user doesn't have Flash installedNoSQL CouchDB for fetching users and soon cards, achievements, friend associat…