Rapid release at massive scale
Over time, the software industry has come up with several ways to deliver code faster, safer, and with better quality. Many of these efforts center on ideas such as continuous integration, continuous delivery, agile development, DevOps, and test-driven development. All these methodologies have one common goal: to enable developers to get their code out quickly and correctly to the people who use i
Automating dead code cleanup
Meta’s Systematic Code and Asset Removal Framework (SCARF) has a subsystem for identifying and removing dead code. SCARF combines static and dynamic analysis of programs to detect dead code from both a business and programming language perspective. SCARF automatically creates change requests that delete the dead code identified from the program analysis, minimizing developer costs. In our last blo
Update on Meta’s Year of Efficiency | Meta
Mark Zuckerberg just shared the following with Meta employees: Meta is building the future of human connection, and today I want to share some updates on our Year of Efficiency that will help us do that. The goals of this work are: (1) to make us a better technology company and (2) to improve our financial performance in a difficult environment so we can execute our long term vision. Our efficienc
GitHub - facebook/buck2: Build system, successor to Buck
Buck2 is a fast, hermetic, multi-language build system, and a direct successor to the original Buck build system ("Buck1") — both designed by Meta. But what do those words really mean for a build system — and why might they interest you? "But why Buck2?" you might ask, when so many build systems already exist? Fast. It doesn't matter whether a single build command takes 60 seconds to complete, or
“Naomi-isms”
When I joined Facebook (now Meta) almost 17 years ago, my dream job was to be a Product Manager (aka a “PM”). As someone who did not have a technical background and could not code, I saw this as an opportunity to build products with people. In my very early days, I did a lot of different jobs (like marketing, sales, project management, and more — as one does at a start-up!) before finally intervie
Regenerator, AST, and ES6 at Facebook (Tech Talk by Ben Newman)
See the full post here: http://www.hakkalabs.co/articles/ecmascript-6-at-facebook Ben Newman (Engineer, Facebook) has spent many months creating Regenerator which brings support for ES6 style generators to your code. In this popular talk, Ben will talk about what led him to create Regenerator, show us what it can do today, and talk about where it's going in the future. This talk was presented at
Certificate Transparency Monitoring - Facebook for Developers
このツールを使用すると、指定したドメインに発行された証明書を検索したり、新しい証明書に関するFacebookからのお知らせを購読することができます。
On Leaving Facebook
I left Facebook (Meta) in 2021 to join a small startup called Replit. Leaving wasn’t easy, and during the process I’ve talked to half a dozen friends who were in the similar situation. I hope this post would be useful to senior engineers who are looking to leave. Disclaimers: This post isn’t sponsored by Replit, Facebook (Meta), or any other company or product mentioned here. The advice might not
RF21 – Naman Goel – Rethinking CSS - Introducing Stylex
CSS + superpowers - bloat. How Stylex creates a zero-cost abstraction that gives CSS superpowers. If you like what we do please consider subscribing → https://bit.ly/3lowyCt --- This event would not take place without the support of our sponsors: ## Gold Sponsors * Gofore → https://gofore.com * Futurice → https://www.futurice.com * Smartly → https://www.smartly.io ## Silver Spo
The ugly, geeky war for web privacy is playing out in the W3C
Concern trolls and power grabs: Inside Big Tech’s angry, geeky, often petty war for your privacy Inside the World Wide Web Consortium, where the world's top engineers battle over the future of your data. James Rosewell could see his company's future was in jeopardy. It was January 2020, and Google had just announced key details of its plan to increase privacy in its Chrome browser by getting rid o
Rebuilding our tech stack for the new Facebook.com
Facebook.com launched in 2004 as a simple, server-rendered PHP website. Over time, we’ve added layer upon layer of new technology to deliver more interactive features. Each of these new features and technologies incrementally slowed the site down and made it harder to maintain. This made it harder to introduce new experiences. Features like dark mode and saving your place in News Feed had no strai
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Preventing Cross-site leaks on the web | Whitehatヘルプセンター
GitHub - facebookincubator/dhcplb: dhcplb is Facebook's implementation of a load balancer for DHCP.
GitHub - facebook/sapling: A Scalable, User-Friendly Source Control System.
Making the metaverse: What it is, how it will be built, and why it matters
GitHub - afrind/draft-rush
GitHub - facebookincubator/katran: A high performance layer 4 load balancer
“The Big Shift.” Internal Facebook Memo Tells Employees to Do Better on Privacy.
Is prepack dead? · Issue #2639 · facebookarchive/prepack
Never Send a Human to do a Machine’s Job: How Facebook uses bots to manage tests
