4 ms·

I'm interested in why you feel that way about Netflix. I've been digging into their source code and it's a complicated beast, with flags such as `isGreekAndSaf

by diob 6y ago

I'm interested in why you feel that way about Netflix. I've been digging into their source code and it's a complicated beast, with flags such as `isGreekAndSafari`. Beyond that, they have to deal with all the random business rules that each country has around content. It's given me a big appreciation for what they do, which others might boil down to something that's simpler than it actually is ("it's just streaming video, come on"). Reminds me of how people treat web developers in comparison to "real developers". I think perhaps it's just human nature to downplay the work or job of others. I don't disagree that some places might have too many engineers, but I also think you underestimate the complexities of running a product that operates in every corner of the globe. And wants to provide a damn good experience in every corner of the globe. So it's insane to me that you think their problems are "done" or "solved". That's how you end up falling behind and becoming an outdated business. These companies are trying to be proactive, not reactive!

DaiPlusPlus 6y ago
Those problems you describe are about implementing business rules - that’s not particularly interesting work provided the system has been well-designed. I imagine the glamorous work at Netflix for building out their scalable infrastructure for delivering terabytes of content every second largely ended years ago - of course that work is ongoing as new delivery systems and transports emerge and content consumption habits evolve (remember when people used to think you could only watch Netflix Streaming on a computer?) - but that needs far fewer people to accomplish, and it would be evolutionary work, not revolutionary. > I think perhaps it's just human nature to downplay the work or job of others. Of course it is! But as far as Netflix, and all other employers are concerned, they need to offer jobs that are either “interesting” or glamarous - otherwise there’s nothing to attract the best talent when they’re already paying top-tier Bay Area comps just to compete with Google and Facebook. (Why they don’t try to compete with PTO is beyond me - I told one recruiter I’d work for 20% less comp if they doubled their miserly 15 days PTO and they never got back to me - but that’s another story). Now in my case, the work I do for my day-job isn’t glamorous at all: it’s just a straightforward line-of-business SaaS application. I’m not looking to change my employer at all (for reasons I won’t go into - but I do get 45 days PTO), but if I was looking I wouldn’t accept a job at a big name if it’s just to do /routine/ work. I want to be able to blog about my work and have people at least say “oh hey, that’s cool”.
- diob 6y ago
  I agree that companies tend to over hire. My company certainly does, which leads to things taking much more time they would with less folks (and often more buggy). It's the age old problem of throwing engineers at things thinking it'll speed things up I guess. I disagree that there isn't exciting work to be done at these places. I think you're just as likely to be bored at any other job, you just get paid boatloads more. Most end up running off to do their own thing since they have the financial freedom to do so after a few years. For what it's worth, I think you'd be able to blog about your work at Netflix, Google, Facebook, etc. Plenty of their employees do so. EDIT (you added in some PTO details): Heck I wouldn't leave if I got 45 days PTO either! Yeah, I hope companies start competing more on hrs of work. I'd gladly take a hefty pay cut to work 20 hrs a week.
  - DaiPlusPlus 6y ago
    > I think you'd be able to blog about your work at Netflix, Google, Facebook, etc. Plenty of their employees do so. There’s two types of work-blog: the kind you have on your personal website - and the kind on the company’s own blog. Most companies prohibit what you can talk about on your own blog (rightfully so - competitive secrets, etc) but some companies like a Apple outright prohibit you talking about your work to others at all beyond generalities. Company-run blogs, for all their casual demeanour, are still ruled by management - and one’s blog articles become their copyright unless otherwise stipulated (as it’s a work stemming from your employment). When/if the company ceases to exist - so do your articles. I had my own blog on blogs.msdn.com when I was at Microsoft - I sometimes posted somewhat subversive articles (such as guides on how to tweak the appearance of components of Windows if you didn’t like the defaults using publicly available articles and documentation) - I was hoping it would still be online today but it seems most MSDN blogs that didn’t reach Raymond Chen-levels of popularity got axed when the “MSDN” brand was retired. Oh well...
Benjammer 6y ago
I think having flags like isGreekAndSafari could also possibly be a sign of too many engineers. I never really understand why large scope and/or scale business rules require more engineers. Why do companies program all this stuff directly into the app with crazy flags like that instead of building configuration systems so that lower cost employees can fill in and expand the business rules?
- memexy 6y ago
  What kind of language and configuration system do you suppose would be viable for doing this? What kind of system would let "lower cost employees" fill in and expand the business rules?

by diob 6y ago

DaiPlusPlus 6y ago

Those problems you describe are about implementing business rules - that’s not particularly interesting work provided the system has been well-designed. I imagine the glamorous work at Netflix for building out their scalable infrastructure for delivering terabytes of content every second largely ended years ago - of course that work is ongoing as new delivery systems and transports emerge and content consumption habits evolve (remember when people used to think you could only watch Netflix Streaming on a computer?) - but that needs far fewer people to accomplish, and it would be evolutionary work, not revolutionary. > I think perhaps it's just human nature to downplay the work or job of others. Of course it is! But as far as Netflix, and all other employers are concerned, they need to offer jobs that are either “interesting” or glamarous - otherwise there’s nothing to attract the best talent when they’re already paying top-tier Bay Area comps just to compete with Google and Facebook. (Why they don’t try to compete with PTO is beyond me - I told one recruiter I’d work for 20% less comp if they doubled their miserly 15 days PTO and they never got back to me - but that’s another story). Now in my case, the work I do for my day-job isn’t glamorous at all: it’s just a straightforward line-of-business SaaS application. I’m not looking to change my employer at all (for reasons I won’t go into - but I do get 45 days PTO), but if I was looking I wouldn’t accept a job at a big name if it’s just to do /routine/ work. I want to be able to blog about my work and have people at least say “oh hey, that’s cool”.

diob 6y ago
I agree that companies tend to over hire. My company certainly does, which leads to things taking much more time they would with less folks (and often more buggy). It's the age old problem of throwing engineers at things thinking it'll speed things up I guess. I disagree that there isn't exciting work to be done at these places. I think you're just as likely to be bored at any other job, you just get paid boatloads more. Most end up running off to do their own thing since they have the financial freedom to do so after a few years. For what it's worth, I think you'd be able to blog about your work at Netflix, Google, Facebook, etc. Plenty of their employees do so. EDIT (you added in some PTO details): Heck I wouldn't leave if I got 45 days PTO either! Yeah, I hope companies start competing more on hrs of work. I'd gladly take a hefty pay cut to work 20 hrs a week.
- DaiPlusPlus 6y ago
  > I think you'd be able to blog about your work at Netflix, Google, Facebook, etc. Plenty of their employees do so. There’s two types of work-blog: the kind you have on your personal website - and the kind on the company’s own blog. Most companies prohibit what you can talk about on your own blog (rightfully so - competitive secrets, etc) but some companies like a Apple outright prohibit you talking about your work to others at all beyond generalities. Company-run blogs, for all their casual demeanour, are still ruled by management - and one’s blog articles become their copyright unless otherwise stipulated (as it’s a work stemming from your employment). When/if the company ceases to exist - so do your articles. I had my own blog on blogs.msdn.com when I was at Microsoft - I sometimes posted somewhat subversive articles (such as guides on how to tweak the appearance of components of Windows if you didn’t like the defaults using publicly available articles and documentation) - I was hoping it would still be online today but it seems most MSDN blogs that didn’t reach Raymond Chen-levels of popularity got axed when the “MSDN” brand was retired. Oh well...

Benjammer 6y ago

I think having flags like isGreekAndSafari could also possibly be a sign of too many engineers. I never really understand why large scope and/or scale business rules require more engineers. Why do companies program all this stuff directly into the app with crazy flags like that instead of building configuration systems so that lower cost employees can fill in and expand the business rules?

memexy 6y ago
What kind of language and configuration system do you suppose would be viable for doing this? What kind of system would let "lower cost employees" fill in and expand the business rules?