yizzerin

6 ms·

1. 1.▲
   by yizzerin 12y ago

   check out the Algorithm Design Manual by Steven Skiena. It's fun, accessible and very practical.
2. 2.▲
   by yizzerin 13y ago

   There is a CPU quota limit (and a disk limit) that you have to get approved to raise (and I think there's a limit to how many requests/second you can make to the GCE API), but if you get those approvals, you're good.
3. 3.▲
   by yizzerin 13y ago

   There's very little difference between the two (a few standard library differences at most + a little syntax). 3.4 (and Python 3 generally) is the future of Python. Learn it first and you'll be on good footing.
4. 4.▲
   by yizzerin 13y ago

   Docs are a good place to start. In the projects I've worked on, new contributors usually enter when they've found a bug/desired-feature and worked out a fix for themselves. Aside from that, good first commits are usually smal
5. 5.▲
   by yizzerin 13y ago

   Don't bother pointing out that you're new (that'll be clear from your resume). Say what you've done and tie previous work to that as well.
6. 6.▲
   by yizzerin 13y ago

   Do something exciting for you . More than anything, employers want to see you get excited and energized about something. So if there's some really cool problem that you want to work on and you create/help maintain an open source
7. 7.▲
   by yizzerin 13y ago

   If you don't have that much $$, get a Macbook Air. I did all my development on a 13" Macbook Air before my current job (and I still use it in my personal time) - I love how light it is and easy to carry around. If you're do