Skip to main content

Unionization for Developers and Designers

There was a time in the past where I actually thought developers and designers would benefit from unionization. I realize now that it would shape a devastating reality to the overall advances of technology and design. Unionization would paralyze our ability to innovate because the level of protectionism inherent in unions encourages laziness.

By looking at different disciplines, such as, carpentry and construction, we can observe that there hasn't been any real innovation in toolsets. Carpenters still do not have any robust tools that'll make their jobs 100x more convenient. I compare that manual labour to a programmer writing in binary just to build an eCommerce site. It is puzzling how other technology sectors have little to no progression. Another example is economic airline technology--20 years ago we had super sonic jets and now we're stuck with slower airplanes. How do they fix this problem? They improve the fuel efficiency in the engines. Aircraft technology needs another Howard Hughes--someone who can really push the industry in the right direction and really make lives better. Without Howard Hughes' achievements, we would never have had commercial flight.

In software, there are many heroes that have Howard Hughes' determination to prevail: Steve Jobs, Mark Zuckerberg, and Bill Gates. While Steve Jobs has been leading the efforts in consumer software and hardware (computing and mobile), Mark Zuckerberg has been leading the efforts in social networking. Facebook has revolutionized the way humans interact with each other by allowing people to build new relationships, rekindle old relationships, and share life's timeless memories through videos, photos, and status updates.

One of the primary reasons I design and develop software is because the environment changes constantly. It's an evolving ecosystem to be in. Problems are surfaced and solutions are executed against those problems at different angles. It's fast-paced.

Imagine a world where developers could work 8 hour days and be confident about his unfinished/untested work. What about his teammates? Don't they depend on his code being feature complete? Nothing would ever get done because of the level of protection unions provide people -- It's a shield for the lazy.

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…