5 ms·

Good. I turned down a job this week because it became clear that the CEO couldn't handle any non-positive feedback and took it as a personal criticism. Hey du

Good. I turned down a job this week because it became clear that the CEO couldn't handle any non-positive feedback and took it as a personal criticism. Hey dude, if you have a redux reducer file that's over 11k+ lines long that doesn't mean that I'm "not smart enough to understand your code" it means you haven't bothered to keep basic code hygiene and break up your files. It was a shame too - cool industry and tech stack and an odious toxic suck-bro culture. /smh

gridlockd 7y ago
> Hey dude, if you have a redux reducer file that's over 11k+ lines long that doesn't mean that I'm "not smart enough to understand your code" it means you haven't bothered to keep basic code hygiene and break up your files. While I haven't seen the code, this belief that large files are bad "by default" to me is a clear sign of an developer who puts superficialities before more important work. In any event, any significantly evolved system has lots of sore spots that are nevertheless not the most pressing issue at any particular moment. This is the nature of things. Learning to accept that and still getting things done is valuable.
- patientplatypus 7y ago
  Nah man, I didn't make it black and white like that. It was more along the lines of "why is this reducer so big? it seems like that's a major red flag to me because that usually means its difficult to debug" and the guy went bananas. I almost never make bold "it must always be so" statements, as only the Sith deal in absolutes.