Location: Metro Vancouver, Canada
Remote: yes
Willing to relocate: no
Technologies: Ruby/Rails, Go, Docker/Kubernetes, Postgres, Kafka, etc
Résumé/CV: https://www.linkedin.com/in/vincehodges/ && https://github.com/vhodges
Email: vhodges@gmail.com
Just a note, if you do leetcode questions in your interviews (you might call them data structures and algorithms) I am not interested.
I do not do well on them. Case in point I just finished an interview where I ran out of time computing the mode of an array - something I was unfamiliar with. It's not that I couldn't have figured it out but the time pressure got to me and it went downhill from there - we ran out of time for the second part of the interview (I will also say we probably spent to long on the intros part making the time pressure even worse).
It doesn't mean I don't know how to write software, something I've been doing for almost 45 years!
It's purely personal, but my body really seems to prefer daylight savings. I always have very rough and fluctuating sleep schedules during the winter. They seem to go away after the spring ahead (it could just be the longer daylight hours that become more apparent during spring). Greetings from Mission!
Yeah, I would argue strongly it's just because you have more sunlight during daylight savings. Having the sun rise later in winter would just make your sleep worse.
If you wanted to test this, try setting your alarm one hour earlier for a few weeks in winter and see if it makes you feel better.
I would prefer you simply adjust your personal schedule (yes, it’s far more likely the shorter daylight and probably insufficient Vitamin D) than that we permanently turn the one hour offset from high noon of the sun…the very basis for time itself coupled to the natural phenomenon of earth’s rotation … into the standard now.
“Daddy, why is the sun at its highest point at 1300 and not noon like since the beginning of time?” … “because right before humans destroyed themselves they became idiots and lost their mind and started being confused about their genitals, time itself, whether they should be alive or not, and even tried convincing themselves that the Big Arch burger was not disgusting food-product slop; that’s why, my AI robot son, that’s why!”
If you read through the BBC post, it alludes to passing confidential trade documents to Epstein... but of course that's probably because he was being blackmailed by Epstein for f*cking under age girls.
Is that per person or for the 5 people? No if per person if the minimum commit is 30 days (300/Night is not too bad, but for a week to 10 days at a time, not the month). If for all 5 then yes, it might make sense for retreats.
I DO wish there a business focused resort with meeting rooms, workspaces, good connectivity and AV, etc. Suites with meeting space for smaller groups/after hours meetings and some amenities for after hours (eg pool, golf, gym, etc).
EDIT: My house is paid for, so I am not really the target demographic :)
* https://github.com/rqlite/rqlite Distributed, fault tolerant cluster
* https://litestream.io/ Replication to S3 (or compatible) - more disaster recovery than fail over
* https://fly.io/docs/litefs/ Same Author as litestream). Distributed replication. Requires writes to be redirected to the primary.
I am debating Postgres vs sqlite (probably with litestream) for a project right now.
And other than HW redundancy, I can get pretty far by scaling vertically on a single box. And for my app, I could probably (and my users!) live with some occasional downtime (as long as the data is replicated/backed up).
If I get 20-50K users, it'll be a successful venture so I don't need much these days and it will be cheaper and easier to run as well.
Yeah if you're comfortable scaling vertically and potentially a little downtime. Sqlite massively simplifies your ops, backups litestream is fantastic.
It's also as you mentioned dirt cheap (VPS or a hetzner box).
I do not do well on them. Case in point I just finished an interview where I ran out of time computing the mode of an array - something I was unfamiliar with. It's not that I couldn't have figured it out but the time pressure got to me and it went downhill from there - we ran out of time for the second part of the interview (I will also say we probably spent to long on the intros part making the time pressure even worse).
It doesn't mean I don't know how to write software, something I've been doing for almost 45 years!
reply