Skip to main content

Building teams based on passion

After being in a meeting on how to increase team effectiveness and increase the quality of the products we're trying to build, I thought of the process of building teams based on a common passion.

Diving deeper, have you ever met a creative person that loved designing social networks? What about a designer that loved creating interfaces on Mobile platforms? Have you ever met a developer that loved building software that connects people? Why is it that teams in the agency realm with multiple disciplines can't grab a group of people who have a common passion. This is totally different from basing it on "skill set". It's about what they love to build. For example, my skill set ranges from backend (multiple databases, multiple integration languages, localization) to frontend (html, css, js) on different platforms like web and mobile; however, I love building social networks on mobile platforms and how you can integrate with different 3rd party services like Flickr, Facebook, Google, and Foursquare. I strongly believe that the world is moving towards Mobile and some form of secure way of sharing data between different services.

In our current ways of doing things, employees (designer/developer/project manager/quality assurance) are just "resources"--they're thrown around on to different projects with barely any context. Context switching is so expensive--ramp up time, meetings, discovery, and rebuilding a shared vision.

If the overall goal is to secure projects so we can gain revenue (what comes in is what comes out) without knowing exactly what we're trying to build then the designers and developers should have full rights to opt-out of the project. As in, they shouldn't have to build something they're not passionate about. What does the company need to do then? Hire contractors. I'm lucky to have landed a few projects that I've been quite passionate about but I've also had to deliver projects which I totally wished I wasn't associated with. The quality is quite obvious.

My only suggestion to companies that are paralyzed in this state is to try and interview your designers and developers. Figure out what they really love making. Ultimately, humans intrinsically love to build things on their own--why not leverage this aspect of human behaviour to build better software?

Good luck and have fun,
Jaime Bueza

Jaime Bueza is a software developer in Vancouver, British Columbia, Canada. He has developed web applications for Nintendo, Starbucks, Electronic Arts, Ritchie Brothers, Kiwi Collections, Cox Communications and Microsoft. When he's not developing useful software that constantly evolves with business requirements, he's creating tutorial videos for aspiring front-end developers.
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…