Docker is extremely popular these days. Too bad it’s not very good.

A note in advance: This is absolutely not about Docker being too "opinionated" for me, or other tools being more flexible. I believe that learning and using Docker is just plain more complicated than learning and using the tools I describe below. Docker is genuinely more complex and harder to use than the alternatives. These tools also happen to be more flexible than Docker, but that’s not why I’m recommending them: I’m recommending them because they are simpler to learn and use. If they are indeed more flexible in addition to being simpler to use, then that’s just due to an overall superior design.

I often read comments from people that are trying to come up with a clever, deeply-nested directory hierarchy to manage their personal files. You will frequently find discussions about these topics on this sub-reddit. I don’t recommend investing effort in complex directory structures and this is why and what to do instead.

Authors are strongly encouraged to view the div element as an element of last resort, for when no other element is suitable. Use of more appropriate elements instead of the div element leads to better accessibility for readers and easier maintainability for authors.

Lately, I’ve had a surprisingly large number of conversations about logs processing pipelines. I can find probably 10+ already-funded, seemingly successful startups processing logs, and the Big Name Cloud providers all have some kind of logs thingy, but still, people are not satisfied. It’s expensive and slow. And if you complain, you mostly get told that you shouldn’t be using unstructured logs anyway, you should be using event streams.

That advice is not wrong, but it’s incomplete.

Instead of doing a survey of the whole unhappy landscape, let’s just ignore what other people suffer with and talk about what does work. You can probably find, somewhere, something similar to each of the components I’m going to talk about, but you probably can’t find a single solution that combines it all with good performance and super-low latency for a reasonable price. At least, I haven’t found it. I was a little surprised by this, because I didn’t think we were doing anything all that innovative. Apparently I was incorrect.

Since their inception as little more than glorified shell scripts, continuous integration systems, or build servers as they were called, they have evolved from an exotic niche product to a central piece of any well-oiled software delivery project.

Along with the rise of agile methodologies and Continuous Delivery practices, the CI server has moved towards the center stage in your development lifecycle.

And while the market for CI servers is booming, it can be hard to tell the difference between them and choose which one to adopt. Should one choose Jenkins, GitLab CI, or maybe GitHub Actions? This blog post will guide you through the selection process and give you guidance for making the optimal choice.