Culture
The Software Engineering Job Ladder 11 minutes read.
An incredible resource by Chuck Groom to help you define the Career Ladder in your company for Software Engineers. This one is critical when you have that ladder in place: "Promote people who are already functioning at the next level. If a level-2 engineer wants a promotion, they should demonstrate they are doing level-3 work. It’s your job as a manager to give them projects where they can cut their teeth (and land gracefully if they’re not quite ready)."
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
Why I Quit Google to Work for Myself 10 minutes read.
Every performance evaluation system converges to a game, no matter the intentions when it started: "I drastically reduced the time developers spent repairing those failures, but there were no metrics that tracked developer time... Now that I understood how the process worked, I could keep doing the same good work, just with better record-keeping... Well, Google kept telling me that it couldn’t judge my work until it saw me complete a project. Meanwhile, I couldn’t complete any projects because Google kept interrupting them midway through and assigning me new ones."
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
Plan a Better Meeting With Design Thinking 4 minutes read.
"We recommend that you ask yourself: If this meeting is wildly successful, what will people feel, know, and do as a result? Include these desired outcomes in your agenda, so that participants know why they’re attending and can gauge with you whether or not the time has been productive." -- This post should be shared with everyone in your company. Meetings cost a lot of money, optimize each and every one of them.
Read it later via
Instapaper.
Share
it via
Twitter
or
email.