On video calls and in meatspace, you get to see peoples facial expressions, their smiles, they can move their hands and make gestures. I much prefer that to text.

As for the human contact, I do recommend having a social life outside work. Distributed or not distributed work.

You are correct but, personally, I think spending 8 hours a day without seeing faces is too much.

I am in this scenario every work day as a non-native speaker. I much prefer talking to people than trying to get the text correct.

The article also assumes every one is a native speaker who can write quickly and clearly in a chat -- in a lot of international projects this is not the case.

I find that there is less chance for misunderstanding and aggression if you disagree over a video call. Also, human contact and informal communication make life and working more enjoyable.

I have a Fairphone 2 as my main phone (released in 2015) and I am running Lineage based on Android 10.

Most cloud providers don't have this billing problem and so the analogy breaks. Its more like, why does this knife keep shooting me in the foot?

You are absolutely correct that running other peoples Ruby code is expensive. I would argue similarly for Java because of the high RAM requirements.

However, if you are a company developing your own software, if you use a more productive technology and it spares just 1 programmer then you have paid for a few hundred VMs and running costs become insignificant compared to labour costs.

This is an argument in favour for both Rails and the Java monsters.

https://medium.com/@sandya.sankarram/unlearning-toxic-behavi...

Its attitude to seals is not very progressive: https://www.humanesociety.org/resources/about-canadian-seal-...

Or the environment: https://www.nationalgeographic.com/environment/article/alber...

Declarative schemas, and a well-defined update process (that isn't human-written DDL), are essential at any sort of organizational scale.

Isn't this impossible because some schema changes require data migration? A data migration cannot be declaratively automated as far as I know.

Queue support

Why not use a dedicated and feature rich queue such as Rabbit MQ or, if you want to get really fancy, Kafka?

This way if you have to push back and say it wasn't you, you have much more impact because you have investigated the problem.

Edit: but I agree, that is no way to treat a colleague.

They were in pre-2020 for bad flu pandemics:

https://en.wikipedia.org/wiki/2009_swine_flu_pandemic_in_Mex...

I tried the Meson build of GStreamer last year. It didn't go well and I gave up because of time pressure.

I haven't looked at Meson since because CMake actually works.

http://www.samaritansusa.org/contact.php

I have no idea what they are like in the US but they are very helpful in the UK.

The standard library manages to pack a lot of functionality in little code. Its probably not easy to write simple concise code in Go but it is certainly possible.

- The Phoenix Project. An easy read that is a good introduction to modern Dev Ops culture [1].

- Designing Data Intensive Applications. A technical introduction to distributed systems.

[1] https://www.goodreads.com/book/show/17255186-the-phoenix-pro...

[2] https://www.goodreads.com/book/show/23463279-designing-data-...

[1] https://golangci-lint.run/

This is straightforward to spoof. A single programmer could do it if they cared enough. It is possible to change the GPS (GNSS?) HAL to send any information you want [1].

[1] https://www.pathpartnertech.com/all-you-need-to-know-about-g...