/Addy Osmani

Effective Engineering Teams tl;dr: The Google research team concluded that the following were pillars of team effectiveness. Addy discusses each in depth: (1) Psychological Safety: "On our team, making a mistake is seen as an opportunity to learn rather than a blunder to be penalized." (2) Dependability: "I can count on my teammates to deliver on their promises and commitments." (3) Structure and Clarity: "We have a clear and effective roadmap for decision-making within our team." (4) Meaning: "The work I contribute to the team holds personal significance for me." (5) Impact: "I can clearly see how our team's efforts make a difference to the broader goals of the organization."

featured in #465

Possibilities If You Don't Ask For What You Want Vs. If You Do tl;dr: Addy argues that by hesitating to ask for what one wants, you not only miss out on immediate opportunities but also deprive your future self and others of potential benefits. If you don’t ask for what you want, you: (1) Sell yourself short. By not expressing desires, one misses out on feedback and potential connections. (2) Limiting your own learning. Not all requests will be met with a 'yes', but each 'no' is a lesson that refines one's approach and understanding. (3) The Ripple Effect. Expressing desires provides clarity to others and can lead to unforeseen payoffs in the future. (4) Breaking free from hesitation. Defining one's goals, practicing articulation, and maintaining a positive yet realistic mindset, one can more confidently ask for what they want. 

featured in #446

An Effective Team Communicates Much Like Optimized Code: With Clarity, Modularity, And A Focus On Simplicity. tl;dr: “Just as we strive for optimized, clean code, our teams should aim for clear, modular, and simple communication.” Addy shares tips from his time at Google: (1) Optimize communication for the target audience. (2) Speak clearly and slowly. (3) Opt for concise messages rather than apologizing for long ones. (4) Use simple and common words. Remove unnecessary and unrelated words. (5) Avoid English idioms and slang phrases if working with a global team. (6) Use inclusive language that considers all educational backgrounds.

featured in #443

Optimizing Speed On eBay.com tl;dr: Optimizations include: (1) Search Results Optimization: By sending the first 10 item images along with the header, eBay ensures quicker downloads, reducing the download start time for search result images. (2) Edge Caching for autosuggestion data: suggestions in the search box are cached and served from a CDN, reducing network latency and server processing time. (3) Edge caching for unrecognized homepage users: Content for unrecognized users is cached on eBay's edge network, allowing first-time users to receive content from a nearby server, reducing network latency and server processing time.

featured in #439

Focus On High-Leverage Activities tl;dr: Leverage is impact produced divided by time invested. To increase your leverage, ask yourself the following before any activity: (1) What if this activity was simple? (decrease time cost). (2) What if this activity was huge? (increase value). (3) What else could I be doing? (opportunity cost).

featured in #370

Software Engineering - The Soft Parts tl;dr: "Today I'll share some of the software engineering soft skills I've learned from my first 10 years on Google Chrome, where I am a Senior Staff Engineering Manager." Addy covers topics such as learning new things, technical complexity, design docs, & more. 

featured in #326

Moving Towards A Faster Web tl;dr: The Chrome team are in development of "badging", a method of identifying sites that are built in "a way that makes them slow" by looking at historical load latencies. In the future, such information may be communicated to users. 

featured in #161

The Cost of Javascript in 2019 tl;dr: Download & execution time are primary bottlenecks for loading scripts in 2019. "Aim for a small bundle of synchronous (inline) scripts for your above-the-fold content with one or more deferred scripts for the rest of the page."

featured in #147

Speed At Scale - What's New In Web Performance? tl;dr: (1) Lighthouse supports Performance Budgeting (2) Native image and iframe lazy-loading comes to the web (3) Google Fonts now supports font-display as a query parameter.

featured in #143

Native Image Lazy-loading For The Web! tl;dr: New loading attribute for images and iframes helps content load quicker, reduces network data usage and reduces memory usage. It should be shipped as part of Chrome 75.

featured in #136