November 2011
7 posts
Tip of the day #2
Don’t have any coding errors in your advertising materials (such as a missing semicolon in any php snippets), as it will distract all the programmers who read your sign, and they will be thinking about that coding error while they’re talking to you.
Tip of the day
If your company is participating in a job fair, and you’re the one manning the table, don’t be wearing the t-shirt of some random other company, as that will confuse the heck out of people who are wondering what company you represent.
Coke computer vs. Pepsi computer
There’s a good deal of talk about the “death of the spec” these past few days. The truth is, the only people that care about specs are those who need to. Almost every techie out there has had a conversation similar to the following:
Non-techie:So, I want to buy a computer, and I saw a <some computer brand> with <some random number> <some random spec…...
Learn Git progressively - Day 3
You’re reading Part Three of the “Learn Git progressively” four-part tutorial.
Basics - Setup, init, add, and commit
Daily usage - status, diff & difftool, and log
Branching & Merging - branch, checkout, and merge
Collaborative coding - remote and Github.com
This is a follow-up to my previous post, Learn Git progressively - Day 2. I suggest reading that post before...
Learn Git progressively - Day 2
You’re reading Part Two of the “Learn Git progressively” four-part tutorial.
Basics - Setup, init, add, and commit
Daily usage - status, diff & difftool, and log
Branching & Merging - branch, checkout, and merge
Collaborative coding - remote and Github.com
This is a follow-up to my previous post, Learn Git progressively - Day 1. I suggest reading that post before...
Learn Git progressively - Day 1
You’re reading Part One of the “Learn Git progressively” four-part tutorial.
Basics - Setup, init, add, and commit
Daily usage - status, diff & difftool, and log
Branching & Merging - branch, checkout, and merge
Collaborative coding - remote and Github.com
I recently came across a question on Stackoverflow asking about version control systems, and one of the answers...
Interviewing is all about failing gracefully
I’ve recently gone through a lot of interviews for a very wide range of positions, and I’ve come to realize that good interviewers are looking for two things:
How much you know
How gracefully you fail
Virtually all interviewees — no matter where they’re interviewing, no matter what the subject material — will not know the complete answer to all interview...
