4 ms·

>I've seen a grown man, extremely well educated, data scientist make a fellow data scientist cry. I've. Seen. Things. Data scientists seem to be on a level of

>I've seen a grown man, extremely well educated, data scientist make a fellow data scientist cry. I've. Seen. Things. Data scientists seem to be on a level of their own when it comes to disrespecting colleagues. I've been surprised by this recently.

goatinaboat 5y ago
Data scientists seem to be on a level of their own when it comes to disrespecting colleagues. I've been surprised by this recently. Pretty much every developer, when brought in as a replacement, will bad-mouth their predecessor, say their code is junk and needs to be totally rewritten, etc. Managers love it and encourage it, to them it's a divide and conquer tactic. Data scientists just take it to the next level, that's all.
- rxhernandez 5y ago
  For swe, I've rarely seen it happen except with junior engineers and end-of-career engineers.
- Cthulhu_ 5y ago
  I do that too, but the code I work with is objectively shit - I can provide the daily WTF with months of wtfs. Maybe I should, but if the previous guy finds it I may be in trouble (I think he's still a shareholder?). The first thing my colleagues did after he left was replace all the code he wrote in the C codebase (I work on the front-end, there's a few years worth of work yet to rebuild it). I'm talking stuff like 15K LOC files with 4-5 times nested switch/case/if/else blocks; string concatenating XML to a global variable, then at the end converting it to JSON; string concatenating HTML with embedded JS and CSS in a JS function inside of a PHP file; using a semicolon-separated value in a database column instead of a simple foreign key (more fun when there's an extra value attached to it, separated with a colon). It's already not an easy domain or a simple application (thousands of fields across dozens of models), but the lack of coding practices only made it worse.
  - cyberpunk 5y ago
    My eyes! Kudos for sticking with it that sounds like a write off heh
- whywhywhywhy 5y ago
  I call it The Eternal Refactor. Gets completely absurd if you're at the same company over 5 years or so and have seen 3 or more groups of devs blame all the issues of the software on the previous tech choices and their preference will solve all the issues and a rewrite is the only way forward yet every time when the rewrite is done and the thing is maybe 10% better at best but has new issues from the rewrite the team begins to cycle out and the process begins again.

goatinaboat 5y ago

Data scientists seem to be on a level of their own when it comes to disrespecting colleagues. I've been surprised by this recently. Pretty much every developer, when brought in as a replacement, will bad-mouth their predecessor, say their code is junk and needs to be totally rewritten, etc. Managers love it and encourage it, to them it's a divide and conquer tactic. Data scientists just take it to the next level, that's all.

rxhernandez 5y ago
For swe, I've rarely seen it happen except with junior engineers and end-of-career engineers.
Cthulhu_ 5y ago
I do that too, but the code I work with is objectively shit - I can provide the daily WTF with months of wtfs. Maybe I should, but if the previous guy finds it I may be in trouble (I think he's still a shareholder?). The first thing my colleagues did after he left was replace all the code he wrote in the C codebase (I work on the front-end, there's a few years worth of work yet to rebuild it). I'm talking stuff like 15K LOC files with 4-5 times nested switch/case/if/else blocks; string concatenating XML to a global variable, then at the end converting it to JSON; string concatenating HTML with embedded JS and CSS in a JS function inside of a PHP file; using a semicolon-separated value in a database column instead of a simple foreign key (more fun when there's an extra value attached to it, separated with a colon). It's already not an easy domain or a simple application (thousands of fields across dozens of models), but the lack of coding practices only made it worse.
- cyberpunk 5y ago
  My eyes! Kudos for sticking with it that sounds like a write off heh
whywhywhywhy 5y ago
I call it The Eternal Refactor. Gets completely absurd if you're at the same company over 5 years or so and have seen 3 or more groups of devs blame all the issues of the software on the previous tech choices and their preference will solve all the issues and a rewrite is the only way forward yet every time when the rewrite is done and the thing is maybe 10% better at best but has new issues from the rewrite the team begins to cycle out and the process begins again.