4 ms·

i did not dig through his comment history. i was directly participating in that thread i quoted! and it was a recent thread. please check it again. i agree tho

i did not dig through his comment history. i was directly participating in that thread i quoted! and it was a recent thread. please check it again. i agree though my comment could have been nicer. apologies. as to adding nothing to the thread: disagree. he literally dumped on AWS with false claims. how do you know i don't work at AWS? why is it ok for him to say stuff like that?

pubg 5y ago
Let these types live in their supreme know-it-all fantasy world, they're not worth a thought. Anyone with a little common sense will see through their shenannigans and proceed to ignore them the way you'd ignore an ant on the sidewalk as you go about your busy day. Don't take it personally, their ignorance has nothing to do with you.
shkkmo 5y ago
The issue isn't just a lack of "niceness" but also how this type of comment derails the conversation into an offtopic argument which should have been pursued only in the original context. If you disagree with the particular assertions here (that your are grossly oversimplifing without context), you should address it directly. Saying "it's fine because you do it too" isn't so much a lack of "niceness", but rather how this type of comment unproductively derails the conversation into an offtopic argument while adding zero constructive discussion.
- throwusawayus 5y ago
  > offtopic argument which should have been pursued only in the original context I would have gladly had that discussion in the original context! but he did not reply to me there, nor to any of the other 6 people who replied to that horrendously incorrect comment of his i would have let it go, but yet here he calls me out saying my own comment is grossly oversimplified, but he offered little explanation of his perspective. if i am understanding his brief argument it is: 1) github is old. 2) sharding is hard. ok so here is my response: it was a lot less old when he started working there in 2013. many other companies have sharded several years after launch. yes it is hard. i have directly worked on teams sharding larger DB's than github's, sharding legacy apps. and so forth. it can be done. it is really hard to justify github to be down this many times from the same root cause. year after year
  - deleted 5y ago
    [deleted]
  - shkkmo 5y ago
    > I would have gladly had that discussion in the original context! but he did not reply to me there, nor to any of the other 6 people who replied to that horrendously incorrect comment of his I think your response in that thread was sufficient. If you feel it was insufficient, that thread would be the correct place to continue the discussion or further clarify any misinformation where people may actually it. People rarely admit when they are wrong and you don't have a right to (or even a reasonble expectation of) any such admission in this context. Harassing them about it in other threads is not a positive contribution to the discussion or the community.
    - throwusawayus 5y ago
      he accused me of making a gross simplification. i responded, perhaps unkindly. but at no point have i "harassed" him. github's outages have made my life difficult. planetscale's pricing scheme has also burned me. i am not just attacking this guy at random. based on upvote points i can conclude many people do think i am contributing positively to this discussion. please refrain from tone-policing me. i don't see any technical comments from you in this discussion whatsoever so how exactly are your comments positively contributing?
      - shkkmo 5y ago
        I already explained that the issues was not your tone, but your attempt to revive an argument from a different, unrelated thread, in this one.
        throwusawayus 5y ago
        i did so because it is directly relevant to this topic! the person who for many years was directly responsible for github's databases, and later their overall infrastructure, recently made a horrendously inaccurate statement about the industry's most popular managed database offering this shows either a severe lack of technical understanding, or a willingness to make deliberate technical misstatements now github is down literally every single day due to database problems. it is very relevant! accountability is important!

pubg 5y ago

Let these types live in their supreme know-it-all fantasy world, they're not worth a thought. Anyone with a little common sense will see through their shenannigans and proceed to ignore them the way you'd ignore an ant on the sidewalk as you go about your busy day. Don't take it personally, their ignorance has nothing to do with you.

shkkmo 5y ago

The issue isn't just a lack of "niceness" but also how this type of comment derails the conversation into an offtopic argument which should have been pursued only in the original context. If you disagree with the particular assertions here (that your are grossly oversimplifing without context), you should address it directly. Saying "it's fine because you do it too" isn't so much a lack of "niceness", but rather how this type of comment unproductively derails the conversation into an offtopic argument while adding zero constructive discussion.

throwusawayus 5y ago
> offtopic argument which should have been pursued only in the original context I would have gladly had that discussion in the original context! but he did not reply to me there, nor to any of the other 6 people who replied to that horrendously incorrect comment of his i would have let it go, but yet here he calls me out saying my own comment is grossly oversimplified, but he offered little explanation of his perspective. if i am understanding his brief argument it is: 1) github is old. 2) sharding is hard. ok so here is my response: it was a lot less old when he started working there in 2013. many other companies have sharded several years after launch. yes it is hard. i have directly worked on teams sharding larger DB's than github's, sharding legacy apps. and so forth. it can be done. it is really hard to justify github to be down this many times from the same root cause. year after year
- deleted 5y ago
  [deleted]
- shkkmo 5y ago
  > I would have gladly had that discussion in the original context! but he did not reply to me there, nor to any of the other 6 people who replied to that horrendously incorrect comment of his I think your response in that thread was sufficient. If you feel it was insufficient, that thread would be the correct place to continue the discussion or further clarify any misinformation where people may actually it. People rarely admit when they are wrong and you don't have a right to (or even a reasonble expectation of) any such admission in this context. Harassing them about it in other threads is not a positive contribution to the discussion or the community.
  - throwusawayus 5y ago
    he accused me of making a gross simplification. i responded, perhaps unkindly. but at no point have i "harassed" him. github's outages have made my life difficult. planetscale's pricing scheme has also burned me. i am not just attacking this guy at random. based on upvote points i can conclude many people do think i am contributing positively to this discussion. please refrain from tone-policing me. i don't see any technical comments from you in this discussion whatsoever so how exactly are your comments positively contributing?
    - shkkmo 5y ago
      I already explained that the issues was not your tone, but your attempt to revive an argument from a different, unrelated thread, in this one.
      - throwusawayus 5y ago
        i did so because it is directly relevant to this topic! the person who for many years was directly responsible for github's databases, and later their overall infrastructure, recently made a horrendously inaccurate statement about the industry's most popular managed database offering this shows either a severe lack of technical understanding, or a willingness to make deliberate technical misstatements now github is down literally every single day due to database problems. it is very relevant! accountability is important!