Skip to main content

Job Hunting Tips for New Developers Out of University

Open Source projects on your resume are more important than your co-op or education. I've seen brilliant developers that shatter walls of constraints by being strictly committed to the vision of the project. If there was ever an issue that constrained the team's ability to move forward, there was always that developer hero that would step up to the plate and do what he could to resolve the issue. These types of developers don't play by the rules of the game. They change the game.

Software development companies don't want drones. Drones are people who have jumped through the hoops, ran the courses, and are ready to get paid. Drones aren't creative, confident, or committed. Once a company starts to accumulate too many drone programmers, your company starts to grow "corporate arthritis". Corporate arthritis paralyzes your company's ability to deliver your products efficiently with a degree of quality and reduces your company's ability to keep your customers happy.

The first thing a technical hiring manager will do is Google your name. Then, he or she will try to figure out what your Github is. By looking at how many pull requests / tests / gists / repositories you have, we're able to discern the following characteristics:

- How you write your code
- How you inspire your teammates through your ideas and participation
- Why you make certain technical decisions in your projects
- Why specific decisions need commitment from your teammates. Are you able to get commitment out of your teammates on volunteer software development?
- Can you really convince your teammates that your technical decisions steers the team in the direction that best suits the teams' needs?
- How committed and passionate you are about your discipline
- Do you act as a mentor to your teammates?

Since open source software development is solely based on building a shared vision and aligning everyone's personal masteries (design, development, quality assurance, technical writing), you're essentially putting yourself as a developer on the map for smart companies to hire you. There's nothing more important to a company than hiring heroes that really understand the meaning of shared vision, commitment, dedication, hard work, creativity, inspiration, and mentorship.

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, 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…