sifer

- don't worry about code

- be friendly and focus on getting to know your coworkers a bit

- get all of your account credentials (tools, apps, etc)

- ask about benefits/hr stuff/etc

- set up your local environment (just setup)

- again, don't worry about code yet (no reason you should be dropping code - even tests - on day1)

It's my understanding that if you are a talented engineer who is socially competent and interviews well, no, you don't have to don't have to do this.

Note that my comment is in reference to Python3, since Python2 will not be maintained past 2020.

If you’re on a Mac, just use the brew installation (brew install). If you’re on some type of prod/containerized setup, use apt’s python (apt-get install).

I would not recommend building Python from source unless you _really_ know what you’re doing on that level, as you can unintentionally shoot yourself in the foot quite a bit. From there just using a virtualenv should be pretty straightforward.

In this way, you’re letting the package managers (written by much smarter people than you and I) do the heavy lifting.

If you have the app open, they’re clearly gonna have background tasks running to collect data/usage stats. That’s no surprise. 5000/hr is about 3.5/minute. Sounds perfectly normal for a tracking/advertising app like Snapchat. If you don’t like it just quit the app

This. I feel like anything else (given 2020 around the corner) is just sensationalist

Eh in that case I guess the MVP would be just a landing/signup page (as you mentioned), which could still be totally polished and cleaned up - so could still totally be a 10 :)

Money, engineering talent, and virtually infinite resources to continue research

I personally feel that Python engineers will always have jobs in some context. For backend webdev, obviously Python and Node are some web-app leaders. I've heard of a few Go jobs, but not too many. I wouldn't get too caught up in the frameworks part (Django, Flask, Hapi, React, etc). The framework is just the tool used to implement the concept, not the concept per se. Make sure you're familiar with the _concepts_ and any job worth having won't necessarily care _too_ much if you're a pro at the language/framework (that can easily be picked up in a few weeks on the job).

Will chime in and mention aiohttp[1]. It's lightweight, fun, and the API is very user-friendly for those willing to work on a slightly lower level. I use it to build speedy APIs, and coupled with a good ORM (peewee? [2]) it's pretty dope.

1. https://aiohttp.readthedocs.io/en/stable/

2. http://docs.peewee-orm.com/en/latest/