サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
大そうじへの備え
www.industrialempathy.com
There is a phrase that is very frequently used at Google and other big tech companies. It’s a nice and short phrase. And the problem it describes is broadly applicable to modern software engineering. Yet it doesn’t seem to be used much outside of the Google diaspora, and there doesn’t seem to be an alternative naming for the concept either. The phrase is version skew or for short: skew. Version sk
On March 4th, 2022 was my last day at Google. It was an amazing 11+ years working with some of the most inspiring and talented colleagues one could imagine. As my final role, I was leading Google Search for Desktop computers. I still cannot believe they let me run the literal search engine. In fact, this was my first time leading a major consumer product after years of being focused on infrastruct
This is Malte Ubl's personal blog. I write very occasionally about large-scale software design, AI, and web development. New on the web Software design and architectureRefactoring podcast: How Vercel Works (refactoring.fm) 29 Jun 2024Malte Handbook 17 Jun 2024Why all software migrations should be incremental (vercel.com) 30 Aug 2023Frontend & Backend Defined 08 Aug 2023Version Skew 21 Jun 2023Prin
In this post I'll outline 8 image loading optimization techniques to minimize both the bandwidth used for loading images on the web and the CPU usage for image display. I'll present them in the form of an annotated HTML example to make it easy for folks to reproduce the results. Some of these techniques are more established, while others are somewhat novel. Ideally, your favorite mechanism for pub
I'm excited to announce the beta-release of eleventy-high-performance-blog–a high-performance blog template for 11ty based on this very website. The template itself is based on the awesome eleventy-base-blog adding features centered around performance, accessibility and some SEO. Sites based on this template achieve 100 points on Lighthouse in the categories Performance, Accessibility, Best Practi
One of the key elements of Google's software engineering culture is the use of design docs for defining software designs. These are relatively informal documents that the primary author or authors of a software system or application create before they embark on the coding project. The design doc documents the high level implementation strategy and key design decisions with emphasis on the trade-of
This is a mildly edited transcript of my JSConf Australia talk. Watch the whole talk on YouTube. A sequel to this post is available over here. Hello, I used to build very large JavaScript applications. I don’t really do that anymore, so I thought it was a good time to give a bit of a retrospective and share what I learned. Yesterday I was having a beer at the conference party and I was asked: “Hey
Design docs are a fundamental tool for communicating software design decisions–but communicating things is hard and so is writing design docs. Time for an overly detailed exploration into what would happen if one wrote a design doc for design docs. May 19th, 2015 Status: Draft Authors: Malte Ubl Note: While this post continues to be independently useful, I have published a more approachable write-
このページを最初にブックマークしてみませんか?
『Industrial Empathy』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く