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 commongoal: to enable developers to get their code out quickly and correctly to the people who use i
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 andprogramming language perspective. SCARF automaticallycreates changerequests that delete the dead code identified from the program analysis, minimizing developer costs. In our lastblo
Mark Zuckerbergjust shared the following with Metaemployees: Meta isbuilding the future of human connection, and today I want to share some updates on our Year of Efficiency that will help us do that. Thegoals of this work are: (1) to make us a bettertechnology company and (2) to improve our financial performance in a difficult environment so we can execute our long term vision. Our efficienc
Buck2 is a fast, hermetic, multi-languagebuild system, and a direct successor to the original Buckbuild system ("Buck1") — both designed by Meta. But what do those words really mean for abuild system — and why might they interest you? "But why Buck2?" you might ask, when so manybuild systems already exist? Fast.It doesn't matter whether a singlebuild command takes 60 seconds to complete, or
When Ijoined 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 atechnical background and could not code, I saw this as an opportunity tobuild products with people. In my veryearly 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
See the full post here: http://www.hakkalabs.co/articles/ecmascript-6-at-facebook Ben Newman (Engineer, Facebook) has spent many monthscreating Regenerator which brings support for ES6 style generators to your code. In this popular talk, Ben will talk about what led him tocreate Regenerator, show us whatit can do today, and talk about whereit'sgoing in the future. This talk was presented at
I left Facebook (Meta) in 2021 tojoin a small startup called Replit. Leaving wasn’t easy, and during the process I’ve talked to half a dozen friends who were in thesimilar 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
CSS + superpowers -bloat. How Stylexcreates a zero-cost abstraction that givesCSS 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
Concern trolls and power grabs: Inside BigTech’s angry, geeky, often petty war for yourprivacy Inside the World Wide Web Consortium, where the world'stop engineers battle over the future of your data. JamesRosewell could see his company's future was in jeopardy.It was January 2020, andGoogle hadjust announced key details ofits plan to increaseprivacy initsChrome browser by getting rid o
Facebook.com launched in 2004 as asimple, server-renderedPHP website. Over time, we’ve added layer upon layer of newtechnology to deliver more interactive features. Each of these new features andtechnologies incrementally slowed the site down and madeit harder to maintain. This madeit harder to introduce new experiences. Features like dark mode and saving your place in News Feed had no strai
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く