Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Python at Netflix

medium.com

Post reply on HN
Print view View original

171–180 of 250 posts

Re: Python at Netflix

#171

Post by sametmax »

winter_blue wrote: post #91
sametmax wrote: post #77

Earlier quoted context omitted.

I know at least 3 french persons that managed to make it work. They don't even work for a FAANGs, and only of of them is technically better than I am. I'm an optimist :)

Could you ask them on what visa they moved to the U.S.? I know a few French people in New York. But they're on J-1 visas -- which are very short in duration (~1 year), and truly temporary -- you are required to have plans to return to your "home country" after that period. It offers no practical path towards permanent residence. The only visas that don't prohibit immigrant intent (i.e. desire to immigrate + company a…

I'll check with them if I work in their team again.

Re: Python at Netflix

#173

Post by mirceal »

tsss wrote: post #99
chadash wrote: post #7

Earlier quoted context omitted.

I didn't downvote the parent, but I think that doing so is justified because the comment doesn't add much to the conversation, whether you agree with it or not. To be a substantive comment, it should explain _why_ typed languages would be a better choice for these particular use cases.

At this point it should be common sense, there are arguments about this in practically every thread that mentions Python or JS. As much as I hate dynamic typing, there are use-cases where I don't care about it much. What makes Python truly an awful experience in any case is the completely asinine dependency management.

haha. if you think dependency management is bad in python you should take a look at go :O

Re: Python at Netflix

#174

Post by 2trill2spill »

drewg123 wrote: post #19
sametmax wrote: post #11

Do you know what the Netflix culture is regarding remote work ? I've been looking for a job for the first time in 10 years of Python, and Netflix is one of the rare big companies that I still have respect for. https://jobs.netflix.com/ has several offers I would be a good fit for, but I'm not ready to relocate to the US.

We do have an office in Paris: https://jobs.netflix.com/locations/paris-france Netflix is generally opposed to remote work, but some teams may make case by case exceptions (especially in Open Connect, the organization which manages the CDN). I'd encourage you to speak to a recruiter.

How come the Open connect team is more receptive to remote work? Harder to find people to work on FreeBSD and low level C code?

Re: Python at Netflix

#175

Post by ApolloFortyNine »

gvd wrote: post #111

I fail to understand the use of python in a distributed environment while the language has such poor concurrency support (on top of the lack of a type system). You can make your application HA, but they are obviously not trying to squeeze out every CPU cycle.

To make a distributed application, you need some sort of orchestration. For example, a Redis job queue.

And at that point, you can just code your application as a single thread, and run one per core on the machine.

And the Python lack of types "issue" has always been a bit overblown in my opinion. If it's not immediately obvious what something is, then you need to either comment more, or come up with better variable names. And if you really, really feel the need for a type system, Python natively supports that now.

Re: Python at Netflix

#176

Post by btkramer9 »

heleninboodler wrote: post #74
theshrike79 wrote: post #48

Earlier quoted context omitted.

Communication between team members is a huge issue in remote work. It works if everyone is on site. It also works if everyone is remote. But when some are at the office and some aren't, communication and information sharing becomes a lot harder. Mostly it's a process and tool issue, but still humans will rather just turn around and ask the team than spend a minute writing their issue on Slack/whatever.

It's true. I worked at a company that was 100% remote when it started and kept the remote culture as it grew from 4 to 25 people, but one city in particular ended up having enough people that they decided to rent space in a big shared office, coworking-style. Ultimately, people who worked in that space ended up being more connected to what's going on, due to physical proximity. You wander past a hallway conversation…

doist?

Re: Python at Netflix

#177

Post by jwandborg »

2trill2spill wrote: post #174
drewg123 wrote: post #19

Earlier quoted context omitted.

We do have an office in Paris: https://jobs.netflix.com/locations/paris-france Netflix is generally opposed to remote work, but some teams may make case by case exceptions (especially in Open Connect, the organization which manages the CDN). I'd encourage you to speak to a recruiter.

How come the Open connect team is more receptive to remote work? Harder to find people to work on FreeBSD and low level C code?

Maybe because their hardware architecture is distributed.

Re: Python at Netflix

#178

Post by Macha »

heleninboodler wrote: post #74
theshrike79 wrote: post #48

Earlier quoted context omitted.

Communication between team members is a huge issue in remote work. It works if everyone is on site. It also works if everyone is remote. But when some are at the office and some aren't, communication and information sharing becomes a lot harder. Mostly it's a process and tool issue, but still humans will rather just turn around and ask the team than spend a minute writing their issue on Slack/whatever.

It's true. I worked at a company that was 100% remote when it started and kept the remote culture as it grew from 4 to 25 people, but one city in particular ended up having enough people that they decided to rent space in a big shared office, coworking-style. Ultimately, people who worked in that space ended up being more connected to what's going on, due to physical proximity. You wander past a hallway conversation…

It's not even remote vs non-remote. My employer had many medium sized offices of 100-200 people, and we merged with a company that had one single 5000+ person campus. That was a major culture clash for sure in terms of documentation and processes

Re: Python at Netflix

#179

Post by madsushi »

2trill2spill wrote: post #174
drewg123 wrote: post #19

Earlier quoted context omitted.

We do have an office in Paris: https://jobs.netflix.com/locations/paris-france Netflix is generally opposed to remote work, but some teams may make case by case exceptions (especially in Open Connect, the organization which manages the CDN). I'd encourage you to speak to a recruiter.

How come the Open connect team is more receptive to remote work? Harder to find people to work on FreeBSD and low level C code?

They're also working with a ton of remote and disparate organizations (ISPs), so locality is probably not as important.

Re: Python at Netflix

#180

Post by jimmaswell »

IanCal wrote: post #102
jimmaswell wrote: post #41

Earlier quoted context omitted.

As someone who has worked on fully remote game dev volunteer projects for nearly 10 years, it's unbelievable how much the cultural inertia of physical presence has prevented companies from making the rational move of eliminating all possible office space in favor of remote work and skype meetings. So much money wasted on rent, security, and upkeep and so much time (and even lives) lost to commuting when there isn't a…

> So much money wasted on rent, Although this now translates to a cost on me needing an extra room in the house for an office.

I do fine using my normal desk. Open AWS and Skype at the start of the day, do work, close them at 5, that's it. Bring a laptop to a different corner of the house or a library/coffee shop if you can't adapt to using your personal space for work. Working outside is nice when the weather permits.
Post reply on HN