4 ms·

If you check the issue[1] he reported the crash on November 7th and reported the issue is related to gcc and the kernel on November 8th. At least he was very qu

by sanbor 2y ago

If you check the issue[1] he reported the crash on November 7th and reported the issue is related to gcc and the kernel on November 8th. At least he was very quick going through the rabbit hole. [1]: https://github.com/prometheus/node_exporter/issues/730 https://github.com/prometheus/node_exporter/issues/730

randomdata 2y ago
[flagged]
- prerok 2y ago
  Emm, 10x developer is a myth. The real 10x developer is the one that creates such an infrastructure/libraries/culture that enables 10 other engineers to move fast. The 10x developer is not the person that is 10x faster than other developers on the code base simply because they can hold the spaghetti code they wrote in their head.
- deleted 2y ago
  [deleted]
- gouggoug 2y ago
  > means that a 1x developer will take around 10 hours to get to the same place A "workaround" isn't an adequate substitute for actual the understanding and fixing of the root cause of a bug. What you think is a 10x developer is, in fact, a short-term 10x developer, medium-term 1x developer, long-term -10x developer. Their work while seemingly great at first is just accrued debt with an incredibly high interest rate. But they're rarely the ones fixing it. Now, like everything, a balance needs to be struck between spending hours fixing a bug _the right way_, or, finding a temporary workaround. The real 10x developer is incredibly good at finding this balance.
  - randomdata 2y ago
    > A "workaround" isn't an adequate substitute for actual the understanding and fixing of the root cause of a bug. Right, hence why we recognize that a 10x developer is a weaker developer. Was there something that implied that a weak developer is a substitute for a talented developer for you to say this, or are you just pulling words out of thin air?
    - gouggoug 2y ago
      Merely arguing about your _definition_ of 10x engineer and 1x engineer. Your original comment at the top of the thread implies the engineer who wrote the blog post is a 1x engineer because they spent so much time finding and fixing this bug.
      - randomdata 2y ago
        Yes, and as the comment before it asserts, most engineers would never take that kind of time. They'd bang out some workaround as quickly as possible and move on with life. But my original comment at the top also praised the value of the 1x engineer; noting that the rest of us could learn a thing or two from them. There is no denying that 1x developers are the better developers. The question remains outstanding: Where did you pick up the suggestion that the quick fix is a suitable replacement for the talented engineers who can fully understand a problem that prompted the rebuttal?
        gouggoug 2y ago
        Guess I misinterpreted your comment ¯\_(ツ)_/¯, relax.
    - kragen 2y ago
      'a weaker developer' is the opposite of the standard definition of 'a 10x developer'. if you are going to use phrases to mean the opposite of their conventional meaning you should warn people so they can avoid arguing with you on the assumption that you're using them to mean what everyone else uses them to mean
      - randomdata 2y ago
        Why should I do that? An "argument" about nothing is hilarious.
        samatman 2y ago
        > Why should I do that? Because what you chose to do instead is exceptionally obnoxious behavior, which degrades the quality of discourse on this site.
BobbyJo 2y ago
From the outside looking in, that's mind blowing.

by sanbor 2y ago

randomdata 2y ago

[flagged]

prerok 2y ago
Emm, 10x developer is a myth. The real 10x developer is the one that creates such an infrastructure/libraries/culture that enables 10 other engineers to move fast. The 10x developer is not the person that is 10x faster than other developers on the code base simply because they can hold the spaghetti code they wrote in their head.
deleted 2y ago
[deleted]
gouggoug 2y ago
> means that a 1x developer will take around 10 hours to get to the same place A "workaround" isn't an adequate substitute for actual the understanding and fixing of the root cause of a bug. What you think is a 10x developer is, in fact, a short-term 10x developer, medium-term 1x developer, long-term -10x developer. Their work while seemingly great at first is just accrued debt with an incredibly high interest rate. But they're rarely the ones fixing it. Now, like everything, a balance needs to be struck between spending hours fixing a bug _the right way_, or, finding a temporary workaround. The real 10x developer is incredibly good at finding this balance.
- randomdata 2y ago
  > A "workaround" isn't an adequate substitute for actual the understanding and fixing of the root cause of a bug. Right, hence why we recognize that a 10x developer is a weaker developer. Was there something that implied that a weak developer is a substitute for a talented developer for you to say this, or are you just pulling words out of thin air?
  - gouggoug 2y ago
    Merely arguing about your _definition_ of 10x engineer and 1x engineer. Your original comment at the top of the thread implies the engineer who wrote the blog post is a 1x engineer because they spent so much time finding and fixing this bug.
    - randomdata 2y ago
      Yes, and as the comment before it asserts, most engineers would never take that kind of time. They'd bang out some workaround as quickly as possible and move on with life. But my original comment at the top also praised the value of the 1x engineer; noting that the rest of us could learn a thing or two from them. There is no denying that 1x developers are the better developers. The question remains outstanding: Where did you pick up the suggestion that the quick fix is a suitable replacement for the talented engineers who can fully understand a problem that prompted the rebuttal?
      - gouggoug 2y ago
        Guess I misinterpreted your comment ¯\_(ツ)_/¯, relax.
  - kragen 2y ago
    'a weaker developer' is the opposite of the standard definition of 'a 10x developer'. if you are going to use phrases to mean the opposite of their conventional meaning you should warn people so they can avoid arguing with you on the assumption that you're using them to mean what everyone else uses them to mean
    - randomdata 2y ago
      Why should I do that? An "argument" about nothing is hilarious.
      - samatman 2y ago
        > Why should I do that? Because what you chose to do instead is exceptionally obnoxious behavior, which degrades the quality of discourse on this site.

BobbyJo 2y ago

From the outside looking in, that's mind blowing.