danny_sf45

Do people actually do code reviews per commit? I know it's a thing, but in all my years of experience, I haven't met anyone who actually does this. The usual practice is to review all the changes at once (e.g., go to the "Files changed" tab of a PR in GitHub and start reviewing the changes). This, of course, means, that PR are "small". If a PR is too "big" then one politely asks the author to split the PR in many.

As a developer I prefer using systemd instead of containers to deploy Golang applications.

Without (Docker) containers it is:

- build Go binary and install it in production server

- write and enable the systemd unit file

With (Docker) containers it is:

- write Dockerfile

- install Docker in production server

- build Docker image and deploy container in production server

I get the appealing of containers when one production server is used for multiple applications (e.g., you have a Golang app and a redis cache), but the example above I think containers a bit of an overkill.

Personal opinion: The book "Refactoring" by Fowler is one of the worst (tech) books I have ever read. I would rather refer OP to the bible of OOP: Object-Oriented Software Construction by Bertrand Meyer.

Sure there are two types (or more?) of dependencies, but at the end of the day the AppSignal app requires those +13,000 dependencies in order to work properly (first to build it, and then to run it). That's horrendous.

Sure, if you can do more go for it. I just can't: my brain is tired, my eyes hurt, I cannot produce any productive output/outcome.

I agree that the socialization part is not actually "wasted" time and I would love to do it as much (or as little) as I want per week (ideally one or two days, instead of five days per week on a forced basis).

The only reason for me to not go back to the office is: fixed working hours. Sure, my contract says I have to work 40h/week, but I just can't. If I'm at the office, I would probably work (focused) around 4 or 5 hours. The rest is "wasted" with: chat with other coworkers (non-work related stuff), breaks... but I have to be there for 8 hours no matter what. At home, I can work those 4 or 5 hours (focused) and call it a day. I don't have to pretend I'm working, I just close the laptop.

Same outcome (for the company), less (wasted) hours for me. This is impossible to achieve if one has to go to the office. (can you imagine entering at 9am and leaving at 2pm while telling everybody: "hey, I cannot work anymore, I'm only able to work focused 5 hours per day. See you tomorrow!".)

Another personal anecdote: in my company nobody wants to go back to the office.

Problem with this book is: what to read after. The book is really good but leaves you with the feeling "there are some many topics I don't know yet... but all the other books out there suck". Any recommendation for someone that has already read DDIA?

Right. Street View would be a big loss, but YouTube has accumulated so much (garbage) content that it wouldn't matter if it disappears. Good content would find its way to be published somewhere else.

Only one tech giant? Not much, the other tech giants would take over.

Life without YouTube? It would take a week for most of us to recover. 99% of the content in YouTube is garbage, and for the 1% content of quality, people would find other platforms.

Not really. Sure, programmers that only know HTML, CSS and JS and that were/are making money by building restaurant websites are having a hard time because there exists Wix and the like. But the IT world evolves: Docker, Kubernetes, Go, Terraform, React etc., and developers are hired if and only if they know the new stuff. In 20 years probably all the stuff we usually do now (manually) will be automated, but again in 20 years we will probably program in $NEW_FRAMEWORK and $NEW_LANGUAGE, so Docker, Go, Kubernetes, VueJS will all look like plain HTML + CSS + JS today.