Meta developer tools: Working at scale
I think Meta&#x27;s tooling is inferior to industry standard. I actually took a survey while I was there, and that wasn&#x27;t the majority opinion, but frankly I think most outsiders would absolutely agree.<p>Things like Eden were a great idea, but tools had all sorts of issues they gloss over (a virtual file system can be really slow if you have a ton of small files), dev environments would randomly fail a lot, really the only tool they had that nobody disliked was their log-searching thing (can&#x27;t remember what it&#x27;s called) but it was still lightyears behind something likes splunk.<p>It was my conclusion that &quot;Wow you have 15 people working on a dev-tool compared to a public company with 100 building the industry-standard version over 10 years with actual product managers and UI experts, no wonder ours looks like crap... wouldn&#x27;t it be cheaper just to take .01% of your salary and buy standard dev tools&quot;<p>I guess &quot;Clunky&quot; is the word I&#x27;m looking for. &quot;Blow it away and make a new one&quot; was a phrase that happened with some regularity for dev-envs, repo-checkouts, etc. And iirc restarting your dev box took like &gt;30min.<p>---<p>Side note - the other strangest thing was some of these tools people agreed were terrible (restart takes 30min). So you&#x27;d expect thousands of engineers to be swarming any system with any UI bug, edge-case, or whatever. But it just didn&#x27;t work that way.