Nothing for me: I use it as a Docker Desktop replacement at the moment. There aren't so many complex docker-compose setups I have to deal with, but everything works about as expected.
(Although honestly most of the time I'm using Podman it's on native Linux, so I don't use 99% of the stuff that's there anyway.)
That depends on what you need. For most people and use cases you can replace it with something like Rancher Desktop [1]. But, there are use cases and situations where you needed Docker Desktop.
When I was running Docker Desktop on Windows, I never used the GUI. Instead I always ran commands (docker or docker-compose) on the command line. In that case, the major benefit to Docker Desktop was having it set up the Linux VM that you run Docker on. That is a huge benefit.
Lazydocker is awesome, though. Thanks for introducing it to me. I just installed it and I'm loving it. I've used Portainer in the past, but didn't like it enough to leave it running continuously.
The person you're responding to is responding to a comment asking what is missing from Podman Desktop it to replace Docker Desktop. It is missing nothing for them per their message.
I write mostly about engineering management and software engineering, in general. My most famous post was "Disasters I've seen in a microservices world" [1]
“Is this Hackernews material?” <= This is the question I ask when reviewing posts from colleagues and peers. It’s not a formula to get to the Hackernews’ front page no matter what. It’s about setting the bar high for one self.
In this post:
1. Why we should care about Hackernews and putting our work out there (in this case, in a written form)
2. How, as an Eng Manager, you can help set that culture and end the excuses (“I have no time”)
3. How to make your content appealing, and a mental framework I use to tell a story
---
I'm also offering a short and free guide on writing and distributing "Hackernews material", for Eng Managers and Software Engineers [1]
This reminds me that no matter who you are, solving problems in big companies requires an insane amount of persuasion work. Storytelling and aligning people on why something is essential becomes the job rather than the vision to solve it.
Corollary: if people don't agree on the problem to solve and its importance, solutions heavily tend to fail.
Why can't you create PR chunks without the build failing?
Usually, I strive for "vertical slices". That means that, sometimes, a PR just contains "useless" code in isolation, but that makes sense as I keep merging them (stacked diffs). My flow is usually:
1. Does this code have tests? What's the minimum chunk I need to write tests for it?
2. Write tests and the smallest refactor I can think of (it may be to create one function, p.e.)
3. Commit
4. Return to 1. until the full refactor is done
5. Throw 3-10 stacked diffs that can be merged with the build passing.
So the difference is... local workflow? Whether you branch locally or not as you do work? Am I missing something?
You could do the same thing working on branches and rebasing as fixes on master come in. I just don't get the big deal here
It's great to see more competition in this space. Generally speaking, what I miss in these "incident management" products is also an integrated, flawless way to handle incidents when they're happening. I'm talking about:
1. Quickly creating a proper chat
2. Quickly creating an incident document where you can pin chat messages and use it in the post-mortem. Ideally, pinning some graphs that you'd extract from your observability solutions
3. Having a status page to put a small description for non-technical stakeholders.
PagerDuty covers some of this. Monzo's Response [1] and now incident.io [2] try to cover it too. I'd like to have this experience end-to-end.
Monzo's solution does not seem to be actively maintained, is it?
+100 on the creation of incident chat rooms and pinning data to re-use in incident docs. There is nothing worse than copying the timeline events from one tool to a Google Doc.
This is one thing I really like about PagerDuty's incident response, I can pull incidents and Slack messages right into the Incident timeline. I usually end up copy and pasting it into a.. _sigh_ Jira ticket.
https://medium.com/adevinta-tech-blog/unpacking-the-complexi...