article thumbnail

Trade-offs under pressure: heuristics and observations of teams resolving internet service outages (Part 1)

The Morning Paper

In the next post we’ll look at the detailed analysis of how a team at Etsy handled a particular incident on December 4th 2014, to see what we can learn from it. In summary, software engineers find themselves in a very unenviable position when attempting to resolve an outage with their service. Why is this even a thing?

article thumbnail

Apple Is Not Defending Browser Engine Choice

Alex Russell

On OS es with browser competition, sites can recommend browsers with engines that cost less to support or unlock crucial capabilities. However, developers are loathe to do this; turning away users isn't a winning growth strategy, and prompting visitors to switch is passé. Safari, in particular, is wildly profitable.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

World’s Top Web Performance Leaders To Watch

Rigor

Rick is a software engineer on the Google Chrome team, “leading an effort to make the web just work for developers.” Patrick is a London-based software developer who specializes in web performance and who describes himself as enjoying “working the entire stack, back-end to front-end, CDN to server.”

article thumbnail

Content Management Systems of the Future: Headless, JAMstack, ADN and Functions at the Edge

Abhishek Tiwari

Any organisation pursuing microservices strategy will find hard to fit a traditional CMS in their ecosystem. They often get blindsided by vendor’s pitch and end-up making decision based on some fancy demos (see my post from 2014 on Adobe AEM ). Circa 2014, I was working with a big Japanese automotive brand in Australia.

Systems 63