Quotessence
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 · 5 quotes · Software Engineering, Bugs, Honesty

Filter quotes by topic

AllSoftware EngineeringBugsHonestyPeoplePerformance ManagementProject ManagementRelationship

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

“People are inherently imperfect - we like to say that humans are mostly a collection of intermittent bugs. But before you can understand the bugs in your coworkers, you need to understand the bugs in yourself. We’re going to ask you to think about your own reactions, behaviors, and attitudes - and in return, we hope you gain some real insight into how to become a more efficient and successful software engineer who spends less energy dealing with people-related problems and more time writing great code.”

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

“The moral is this: do not underestimate the power of playing the social game. It’s not about tricking or manipulating people; it’s about creating relationships to get things done. Relationships always outlast projects. When you’ve got richer relationships with your coworkers, they’ll be more willing to go the extra mile when you need them.”

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

“A boat without a captain is nothing more than a floating waiting room: unless someone grabs the rudder and starts the engine, it’s just going to drift along aimlessly with the current. A piece of software is just like that boat: if no one pilots it, you’re left with a group of engineers burning up valuable time, just sitting around waiting for something to happen (or worse, still writing code that you don’t need).”

Project ManagementSoftware Engineering
Book:Software Engineering at Google: Lessons Learned from Programming Over Time
Create image

“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 EngineeringPerformance Management
Book:Software Engineering at Google: Lessons Learned from Programming Over Time
Create image