- Got about 5 sentry errors last night, same thing about db connections failing when the server threads restart.
- The psycopg errors are all downstream. The actual error is that uwsgi is getting workers killed (sig 9) and trying to respawn. In looking through the digital ocean resource plots, it’s under heavy load.
- I believe the OOM killer is doing this deliberately. No error in the application itself. This will resolve once I self-host with a much better machine. No action for now.
- This also makes sense because it happens regularly ~sunday, 4 days after the application is restarted every wed for banner/lines.
- After a fantastic month, ZYME has dropped quite a bit over the past week.
- 30m with Citadel. (hi Jack!)
- Main is asset management, other business is market making (citadel securities).
- SRE positions open in securities, NY and Chicago.
- Umesh CTO: https://www.citadel.com/leadership/umesh-subramanian/.
- Finance is starting to pull a lot of people from big tech: google and such, not just jpmorgan and goldman sachs anymore. Not necessarily an 80-hr workweek industry anymore (although that’s what I’m used to).
- Comp is close to most parallel software positions. ~200 base and maybe 200 more target bonus (rather than equity).
- Work content is still finance, not quite the same purpose as spacex, but excitement from the challenge/community of tech colleagues.
- 20m with Google.
- Could do onsites in LA, even if the position is in the bay.
- Can expedite the interview process, skipping phones and moving straight to onsites.
- Process is basically the same as 2017. Refresh on algorithms and data structures.
- Type multiple times to remember. Most sorts are nlogn. Most searches are logn. Direct data structure operations on a hash table are usually constant. Space complexity for structures/searches are n. Space complexities for sorts are n, logn for quicksort, constant for bubble sort.
- For logn, each iteration is going to reduce the total by ~half. This is like binary search.
- For nlogn, it’s like quadratic, but instead of n*n, you still have to iterate over the whole thing once but each step reduces the remainder by half. This is like quicksort, mergesort, etc.
- 30m with Amazon.
- Hiring is usually isolated to a product (prime video in this case), but lateral movement is very possible within.
- 3 positions: software development engineer (mostly backend), frontend, webdev.
- You interview in general, then pick team after offer (same as google).
- Locations: santa monica and seattle. The recruiter called me from a 650 number!
- Java, python, react, js, aws.
- Prepare this week, tech phone interview next week (basic coding assessment, culture fit), onsites first week of jan (ds&a, system design, leadership).
- Tried a vlog recording with my raw laptop. Not great.
- The cam is at the bottom of the screen, not the top, so the keys/fingers are in frame unless the laptop is open well over 90deg. Mounting it would be weird.
- Resolution was pretty bad. Mic was quiet. Would definitely need to buy decent hardware for both.
- Recorded 2m raw, was 17MB (.webm). Goes to ~/Videos/Webcam
- Bought the logitech c920. Should have much better video and audio. Reviews say it should be fine with ubuntu. $58. Will test when it arrives wed.
- Tons of financial research. Instead of keeping here, added all to a new doc in my notes. Removed the old, elementary ones.
- DJIA, ETFs, SPY, MMMFs, hedging, futures, options, sharpe and other ratios.
- A Netflix recruiter reached out today as well. Set up phone call for tomorrow.