terny

The problem is that it’s public. A private company could very well exist to sell to its users a good service. It being public means it’s beholden to the investor’s desire for constant growth.

The problem is that it’s public. A private company could very well exist to sell to its users a good service. It being public means it’s beholden to the investor’s desire for constant growth.

Gen X and Millennials are the only ones that really needed to go through the early stages of operating systems. Having to get anything done required you to learn a lot.

I think the more the car suits Verstappen the less it does Checo.

Damn, it’s so strange knowing that it’s so bad and yet people use it. Goes to show just how important the content is even with such terrible UX.

You usually want to prioritize changing the container’s build config instead of getting into them and modifying them. Much better to get into the mindset of them not being pets you have to nurture.

Separating the different services into containers is overall a good practice but having the DB in one can be a pain as it’s easier to work with stateless applications. The isolation aspect is very valuable as its easier to debug a problem. I would look into container orchestration if there isn’t already and making sure logs are centralized first.

The post itself is 3y old.

And can be automated easily.

Not just making but interpreting can be very good too. One can learn the basic chords and play almost any song.

I had problems posting comments on liftoff so I stopped contributing altogether.