Skip to main content

How to push forward as a large software development corporation

The Art of War has taught us that when a skilled general decides on a strategy to execute on, they either move quickly, or stay in a position that yields a tactical advantage over his/her enemy. Incidentally, we can apply the same concept in corporate culture. If you take a second to disconnect yourself from your environment, zoom out to a birds eye view, you'll realize how really slow your team is progressing in comparison to the rest of the world.

Naturally, human beings can only see what is in front of them and they need to be constantly reminded of where they are and how they're progressing within their environment. That said, dispelling the blindness of corporate software development is like fighting against an enemy on his own turf and consistently having a positional disadvantage.

The question we keep trying to explore is: what can we use as leverage against such a tough and determined enemy? This is a vicious opponent that not only flattens the spirits of your teammates but paralyzes your abilities to think quickly, act quickly, and move quickly.

If your corporate culture finds itself in quicksand, take a moment to really assess the situation: as time goes by, you're sinking to your inevitable death. In order to really get around your slow and painful demise, you need to use leverage. The answer I believe is in the tools. Tools provide leverage. Much like a lever, you're able to use a minimal amount of effort but exert an incredible amount of force. As a software developer, my job is to write programs that are supposed to be useful. I've decided to generalize the role of a software developer because we are essentially builders, designers, crafters, wizards of the arcane, and automaters.

Examples of leverage are

- a tool that provides an intuitive user interface that all masteries (project management, engineers, and designers) of your team can use for software defects. (bug tracker)
- a tool that provides easier visualization of software requirements (diagramming software)
- a tool that provides sanity and health checks on your software (automation testing)
- a tool that provides a hub for knowledge sharing (wiki)

Since these examples are just tools, we must also understand that there is no such thing as a silver bullet. In some corporations, these tools may be used incorrectly, which wouldn't benefit the company at all; however, if you're able to maximize the potential of these tools and build a shared vision with your teammates, you'll find your company slowly dispelling its entanglements and pushing forward.

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.


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…