<story><title>Eden</title><url>https://github.com/facebookexperimental/eden</url></story><parent_chain><item><author>jfengel</author><text>A lot of programmers would rather write tools for other programmers than for non-programmer end users. It&amp;#x27;s the target market that they know best, and it&amp;#x27;s most prestigious.&lt;p&gt;I wish more of those bright engineers would try to solve problems for other users rather than re-re-re-re-re-optimizing the life of their colleagues. But writing code for users involves, among other things, knowing something about users, which is more bogged down and less fun.</text></item><item><author>peppertree</author><text>After doing a round of onsite with fb tools team, I got the impression there were lots of bright engineers that wanted fb pay without having to touch fb products.</text></item><item><author>ctur</author><text>The SCM ecosystem at Facebook is tremendously powerful and the result of some of the best minds at Facebook working on those systems for many years.  From the scaling of the monorepos to the code review workflows, nothing really matches it.  The ergonomics of most of the tooling was simply top notch (which it needed to be... engineers, particularly at Meta, are an opinionated lot who don&amp;#x27;t tolerate poor tools).&lt;p&gt;It&amp;#x27;s great to see this out in the wild now.</text></item></parent_chain><comment><author>zem</author><text>I work on developer tools at google, and it&amp;#x27;s not even remotely one of the prestigious teams. it is however the most fun and interesting time I&amp;#x27;ve ever had in a job, and if I left it would only be for the same kind of work.&lt;p&gt;also you seem to have fallen for the same fallacy as the people who complain about open source devs not working on what they consider sufficiently important problems. trust me, there are no shortage of engineers willing and eager to work on end user problems, and the dev tools work enables them to deliver solutions to those problems faster, and makes those solutions work more reliably. it&amp;#x27;s a rising tide that lifts everyone&amp;#x27;s boats, not a zero sum game.</text></comment>
<story><title>Eden</title><url>https://github.com/facebookexperimental/eden</url></story><parent_chain><item><author>jfengel</author><text>A lot of programmers would rather write tools for other programmers than for non-programmer end users. It&amp;#x27;s the target market that they know best, and it&amp;#x27;s most prestigious.&lt;p&gt;I wish more of those bright engineers would try to solve problems for other users rather than re-re-re-re-re-optimizing the life of their colleagues. But writing code for users involves, among other things, knowing something about users, which is more bogged down and less fun.</text></item><item><author>peppertree</author><text>After doing a round of onsite with fb tools team, I got the impression there were lots of bright engineers that wanted fb pay without having to touch fb products.</text></item><item><author>ctur</author><text>The SCM ecosystem at Facebook is tremendously powerful and the result of some of the best minds at Facebook working on those systems for many years.  From the scaling of the monorepos to the code review workflows, nothing really matches it.  The ergonomics of most of the tooling was simply top notch (which it needed to be... engineers, particularly at Meta, are an opinionated lot who don&amp;#x27;t tolerate poor tools).&lt;p&gt;It&amp;#x27;s great to see this out in the wild now.</text></item></parent_chain><comment><author>mym1990</author><text>Their colleagues ARE users, they are just a different type, and a type that engineers understand more.&lt;p&gt;I would rather a good engineer put their skills towards helping others use their skills more effectively than put that same engineer in a place where they don&amp;#x27;t like the work and produce below par results.</text></comment>