4 ms·

I'm sure many are going to hate on this, but a simple k8s setup (just container+deployment+ingress) is going to be good for preventing vendor lock in. Too bad

I'm sure many are going to hate on this, but a simple k8s setup (just container+deployment+ingress) is going to be good for preventing vendor lock in. Too bad it's US only, devops is actually a good role for full remote setups. If you can't make it work asynchronously across timezones you are doing it wrong :)

dvrp 1y ago
You deal with emergencies with international on call rotation?
- jen20 1y ago
  I actually can’t think of a better way to do so.
- progbits 1y ago
  Not just emergencies but good timezone coverage is nice for oncall, nobody likes getting woken up by a page at 3am. But I meant things like having good and automated tests, deploys etc so everyone can be productive on their own without multiple people getting involved ("hey can you please deploy X for me when you are here?").
- tgsovlerkhgsel 1y ago
  "Follow the sun" rotations are a common way to handle 24h oncall rotations. Three regular shifts (8 hours of work plus some lunch break that gives you time for a short overlap at the beginning/end of the shift) during that region's local daytime hours, in three different regions with time zones roughly 8 hours apart. That way nobody has to work nights and you still get 24/7 coverage.
  - Spivak 1y ago
    You have to get management to get over themselves and the stupid office policy to make it happen though. Synchronous collaboration isn't all it's cracked up to be.
orochimaaru 1y ago
Hiring and payroll can be a complete nightmare especially with publicly funded organizations and initiatives like arxiv. Also plenty of North Korean bad actors masquerading as US remote workers. I’m betting as European remote workers too. I like remote work but shit like that is why we can’t have good things. https://www.yahoo.com/news/thousands-north-korean-workers-infiltrated-110000417.html https://www.yahoo.com/news/thousands-north-korean-workers-in...

dvrp 1y ago

You deal with emergencies with international on call rotation?

jen20 1y ago
I actually can’t think of a better way to do so.
progbits 1y ago
Not just emergencies but good timezone coverage is nice for oncall, nobody likes getting woken up by a page at 3am. But I meant things like having good and automated tests, deploys etc so everyone can be productive on their own without multiple people getting involved ("hey can you please deploy X for me when you are here?").
tgsovlerkhgsel 1y ago
"Follow the sun" rotations are a common way to handle 24h oncall rotations. Three regular shifts (8 hours of work plus some lunch break that gives you time for a short overlap at the beginning/end of the shift) during that region's local daytime hours, in three different regions with time zones roughly 8 hours apart. That way nobody has to work nights and you still get 24/7 coverage.
- Spivak 1y ago
  You have to get management to get over themselves and the stupid office policy to make it happen though. Synchronous collaboration isn't all it's cracked up to be.

orochimaaru 1y ago

Hiring and payroll can be a complete nightmare especially with publicly funded organizations and initiatives like arxiv. Also plenty of North Korean bad actors masquerading as US remote workers. I’m betting as European remote workers too. I like remote work but shit like that is why we can’t have good things. https://www.yahoo.com/news/thousands-north-korean-workers-infiltrated-110000417.html https://www.yahoo.com/news/thousands-north-korean-workers-in...