Profile

Cover photo
Addy Osmani
Works at Google
Attended University of Warwick
Lives in California, USA
39,178 followers|30,535,115 views
AboutPostsReviews
People
In his circles
818 people
Have him in circles
39,178 people
Dan Brosco's profile photo
djema ismael's profile photo
Shpetim Islami's profile photo
J MingoV's profile photo
Charles Filipponi's profile photo
Ivan K. (divout)'s profile photo
Chea Sinath's profile photo
Balazs Nagy's profile photo
Joshua Kelly's profile photo
Communities
4 communities
Education
  • University of Warwick
  • Oxford University
  • University of Sheffield
Basic Information
Gender
Male
Other names
Adnan Osmani
Story
Tagline
Staff Developer Platform Engineer at Google, Husband
Introduction
Whoa. What are you doing on my profile page? Stalker! ; )

I'm an engineering working with the Chrome and Polymer teams at Google focusing on creating tools to help empower developers to build compelling web apps more easily. My current focus is Polymer - a sugaring library for composable web-apps based on Web Components.

In my spare time, I enjoy contributing free talks, articles and open source projects to the development community.

I'm the author of two books - "Learning JavaScript Design Patterns" and "Developing Backbone.js Applications", have contributed chapters to several Smashing books and have also created/contributed to projects such as TodoMVC, Yeoman and Web Starter Kit.

For the latest on my takes on whats going on in the world of web development, feel free to check out my blog at addyosmani.com.
Work
Occupation
Staff Developer Programs Engineer
Skills
JavaScript & Front-end engineering, Developer Tooling, Web Components
Employment
  • Google
    Staff Developer Platforms Engineer, 2014 - present
    TL for web engineering in Developer Platforms/Chrome
  • Google
    Senior Developer Programs Engineer, 2012 - 2013
    Improving developer tooling and productivity for the Chrome team.
  • Google Chrome
    Developer Programs Engineer, 2011 - 2012
Places
Map of the places this user has livedMap of the places this user has livedMap of the places this user has lived
Currently
California, USA
Previously
Mullingar, Ireland - Mullingar, Ireland - Coventry, England - London, England
Links
Contributor to

Stream

Addy Osmani

Shared publicly  - 
 
CPU throttling is now enabled by default in Chrome DevTools 👌 for simulating perf of low-end mobile devices 🔥
85
14
Daniel Hickman's profile photoRob Becker's profile photoJames Tucker's profile photoMichał Nykiel's profile photo
4 comments
 
In dev channel or canary?

Add a comment...

Addy Osmani

Shared publicly  - 
 
[New] Offline Storage for Progressive Web Apps: https://medium.com/@addyosmani/offline-storage-for-progressive-web-apps-70d52695513c#.498iyd6g3 tl;dr - use Cache API for URL addressable resources, IndexedDB for rest 🔥
2016 will hopefully be the year we build for network resilience.
48
12
Add a comment...

Addy Osmani

Shared publicly  - 
 
Key moments in web page load timings ⚡️

📹 Totally Tooling Tips https://www.youtube.com/watch?v=wFwogd4CdwY
62
23
Dor Kleiman (configurator)'s profile photoLester Quisto's profile photoJacob “kurtextrem” G's profile photo
3 comments
 
+Dor Kleiman great that we have scroll anchoring soonTM
Add a comment...

Addy Osmani

Shared publicly  - 
 
 
We collected a few questions from news publishers related to HTTP to HTTPS site moves, but some of the answers are relevant to all webmasters who are considering going secure.
If you have more questions you'd like to see answered, we're listening!

Q: Should I move my site all at once to HTTPS, or bit by bit?
A: We recommend initially moving just a piece of the site to test any effects on traffic and search indexing. After that you can move the rest of your site all at once or in chunks.
When choosing the initial test section of the site, pick a section that changes less frequently and isn't significantly affected by frequent or unpredictable events.
Also keep in mind that while moving just one section is a great way to test your move, it's not necessarily representative of a whole site move when it comes to search. The more pages that you move, the more likely you'll encounter additional problems to solve. Careful planning can minimize problems.

Q: How long should I run my trial?
A: Plan for a few weeks to allow for crawling and indexing to pick up changes, plus time to monitor traffic.

Q: Even though we are starting with only a section, we plan to make the entire site available on HTTPS. To avoid indexing of the HTTPS content early, should we use redirects or rel=canonicals?
A: With redirects in place, you won't be able to test those pages from a technical point of view, so we'd recommend using rel=canonical.

Q: We reference our HTTP sitemaps in robots.txt. Should we update the robots.txt to include our new HTTPS sitemaps?
A: We recommend separate robots.txt files for HTTP and HTTPS, pointing to separate sitemap files for HTTP and HTTPS. We also recommend listing a specific URL in only one sitemap file.

Q: Which sitemap should map the section in the HTTPS trial?
A: You can create a separate sitemap just for the updated section of your site. This will enable you to track indexing of the trial section more precisely. Be sure not to duplicate these URLs in any other sitemaps, though.

Q: Are there any other specific things we need to add to the robots.txt for the HTTPS version?
A: No.

Q: Our HTTPS site redirects non-migrated pages back to HTTP. What should our sitemaps list? Should we list in our sitemaps both the HTTP and HTTPS URLs? What if in the test section the HTTP URLs redirect to HTTPS?
A: List all HTTP URLs in your HTTP sitemap, and all HTTPS URLs in your HTTPS sitemap, regardless of redirects when the user visits the page. Having pages listed in your sitemap regardless of redirects will help search engines discover the new URLs faster.

Q: If we set includeSubDomains in our HSTS header, which domains will that affect?
A: After you migrate your entire site to HTTPS, you can support HSTS preloading for extra security. To enable this, you must set the includeSubDomains directive in the HSTS header.
If the site www.example.com serves an HSTS header with includeSubdomains set, then it will apply to www.example.com and foo.www.example.com, but not example.com or foo.example.com.
Keep in mind however that HSTS adds complexity to your rollback strategy. Our recommendation is this:
1. Roll out HTTPS without HSTS first.
2. Start sending HSTS headers with a short max-age. Monitor your traffic both from users and other clients, and also dependants' performance, such as ads.
3. Slowly increase the HSTS max-age.
If HSTS doesn't affect your users and search engines negatively, you can, if you wish, ask your site to be added to the Chrome HSTS preload list (https://hstspreload.appspot.com/).

Q: We use a single Google News sitemap for our entire site. What do we do if we're migrating our site piece by piece?
A: If you want to use a Google News sitemap for the new HTTPS section, you will have to contact the News team (https://support.google.com/news/publisher/contact/update_domain) to let them know about the protocol change, and then in your HTTPS property in Search Console you can submit a new Google News sitemap (https://support.google.com/news/publisher/answer/74288) for each migrated HTTPS section of the site.

Q: Are there any specific recommendations for Google News Publisher Center (https://partnerdash.google.com/) with HTTPS migration?
A: Google News Publisher Center handles the HTTP->HTTPS moves transparently. In general you don't have to do anything from Google News perspective, unless you're also making use of News sitemaps. In that case, please get in touch with the News team and let them know about the change, https://support.google.com/news/publisher/contact/update_domain. You can also let the team know about changing sections, for example in case you're moving to HTTPS, you can specify that you're moving http://example.com/section to https://example.com/section .
5 comments on original post
11
4
Add a comment...

Addy Osmani

Shared publicly  - 
 
Reclaim GBs of space by deleting node_modules you don't need 🔥

find . -name node_modules -type d -exec rm -rf {} +
65
19
Robert Khayat's profile photo
 
Nice!! Would love to see an atom plugin that deletes it on close!
Add a comment...

Addy Osmani

Shared publicly  - 
 
Preview of async/await working in Chrome. 👍 for code that looks sync on the surface but is async under the hood 🔥

Try it in Chrome 54 with experimental JS features turned on in about:flags.
108
37
Emmanuel Krebs's profile photoAdão Junior's profile photo0ca0a's profile photoPoongodi Mano's profile photo
5 comments
 
.k8i
Add a comment...

Communities

4 communities

Addy Osmani

Shared publicly  - 
 
JavaScript module bundling, Webpack, Browserify & more in a new Totally Tooling Tips: https://www.youtube.com/watch?v=OhPUaEuEaXk 📦💪🔥
45
14
tushar shete's profile photo
 
nice
Add a comment...

Addy Osmani

Shared publicly  - 
 
 
Great introduction to using Facebook Flow type checking.
Flow is a static type checker for JavaScript designed to make you more productive by providing feedback as you write code. Flow provides…
View original post
21
11
Add a comment...

Addy Osmani

Shared publicly  - 
 
 
Let's make sure ALL web components can be accessed with a screen reader!
4 comments on original post
12
5
Add a comment...

Addy Osmani

Shared publicly  - 
 
Accessible UI components for the web: https://medium.com/@addyosmani/accessible-ui-components-for-the-web-39e727101a67#.pffsev5qu guidance and tooling for inclusive web experiences 🛠⚡️
To be accessible, UI components need to work across multiple devices with varying screen-sizes and different kinds of input. Moreover…
22
8
Add a comment...

Addy Osmani

Shared publicly  - 
 
V8 JavaScript perf improvements 🔥

Promises 20-40% faster on Bluebird benchmark
Startup perf 7%
Framework code 14%

http://v8project.blogspot.com/2016/07/v8-release-53.html
Roughly every six weeks, we create a new branch of V8 as part of our release process. Each version is branched from V8’s git master immediately before Chrome branches for a Chrome Beta milestone. Today we’re pleased to announ...
43
7
Ramzi Youssef's profile photo
 
Will NodeJS use it ?
Add a comment...
After having spent so much on other barristers, with little results, I was amazed at how Paul Richmond (of Richmond Canter Immigration Barristers) handled our immigration case with such care, making the process as painless as possible. As other reviewers have mentioned, his reputation simply excels. Trying to immigrate means a mountain of paperwork and several personal details. Mr. Richmond gave us step by step instructions through the immigration procedure, and whenever we had questions, he was always quick to respond with great detail. Thoroughly going through all of our documents, Mr. Richmond made sure that everything was in order, so that the process went as smoothly as possible. If anyone I knew was looking for an Immigration Barrister, I would definitely recommend Paul Richmond. Mr. Richmond is fair, efficient, and very professional. We will certainly be recommended this firm to our colleagues and friends.
• • •
Public - 4 years ago
reviewed 4 years ago
1 review
Map
Map
Map