Home / Books / Software Engineering at Google: Lessons Learned from Programming Over Time

Software Engineering at Google: Lessons Learned from Programming Over Time

Book by Titus Winters · 1 quotes · Software Engineering, Bugs, Honesty

Browse quotes from Software Engineering at Google: Lessons Learned from Programming Over Time.

Book detail: Software Engineering at Google: Lessons Learned from Programming Over Time is presented as a focused source page for quotations connected with this book, collection, transcript, or source record.

Browse quotes from Software Engineering at Google: Lessons Learned from Programming Over Time.

The quotes below use the same card format as the rest of the site, including topics, source notes, copy actions, image creation, and sharing controls.

Filter quotes by topic

All Software Engineering Bugs Honesty People Performance Management Project Management Relationship

Software Engineering at Google: Lessons Learned from Programming Over Time Quotes

“In short, performance ratings are indicative only of how a person is performing in their given role at the time they are being evaluated. Ratings, although an important way to measure performance during a specific period, are not predictive of future performance and should not be used to gauge readiness for a future role or qualify an internal candidate for a different team. (They can, however, be used to evaluate whether an employee is properly or improperly slotted on their current team; therefore, they can provide an opportunity to evaluate how to better support an internal candidate moving forward.)”

Software Engineering Performance Management

Book:Software Engineering at Google: Lessons Learned from Programming Over Time

Source: Software Engineering at Google: Lessons Learned from Programming Over Time