5 ms·

The author is a staff engineer at GitHub. I don't think they haven't worked at scale

• deleted 1y ago
  [deleted]
• pinoy420 1y ago
  [flagged]
  • rednafi 1y ago
    Man, who hurt you? I certainly don’t agree with everything Sean says and admit that “picking the most important work” is a naive thing to say in most scenarios. But writing Python in production is trivial. Why would anyone lie about that? C is different OTOH. But just because you do a single config change and get paid for that doesn’t mean it’s true for everyone. Also, staff at GitHub requires a certain bar of excellence. So I wouldn’t blindly dismiss everything just out of spite.
  • xerxes901 1y ago
    I personally know and have (tangentially) worked with the guy and none of what you’ve said is true. > Look at his CV. Tiny (but impactful) features ///building on existing infrastructure which has already provably scaled to millions and likely has never seen beneath what is a rest api and a react front end/// Off the top of my head he wrote the socket monitoring infrastructure for Zendesk’s unicorn workers, for example.
    • awesome_dude 1y ago
      [flagged]