はてなブックマーク

Over the past year, the Vue team has been working on the next major version of Vue.js, which we hope to release in the first half of 2020. (This work is ongoing at the time of writing.) The idea for a new major version of Vue took shape in late 2018, when the codebase of Vue 2 was about two-and-a-half years old. That may not sound like a long time in the life span of generic software, but the fron

This guide is a collaboration between:Katie Womersley, VP of engineering at Buffer. When I’m writing, you’ll see this: ● Juan Pablo Buriticá, VP of engineering at Splice. When I’m writing, you’ll see this: ▲ When we’re both writing, you’ll see this: ■ ▲ All teams past a certain size become distributed, whether across rooms, floors, buildings, cities, or continents. But tech is only starting to exp

A focus on small teams anchored the organization’s growth from three to 2,300. Amazon has an adage: If you can’t feed the team with two pizzas, the team is too big. At Twilio, a commitment to small teams is a cornerstone of how we operate. As we’ve grown from tens to thousands, our teams have remained independent units of no more than 10 people. At the center of our philosophy is autonomy. No matt

To discover the state of incident response across the tech industry, we surveyed over thirty industry leaders (including Amazon, Dropbox, Facebook, Google, and Netflix) about their incident response processes. When a software application or system breaks, changes in important metrics trigger an automated alert that something is going terribly wrong. The alert is routed to an engineer who is on-cal

This issue examines the ever-evolving practices of software planning—and how we can craft plans that enrich communication, alignment, and impact on engineering teams. More about this issue