I would stay away from YAML (almost at all costs).

Please also consider posting to !challenges@programming.dev

Apart from the historical value, the most important part of this article now is the "Note of reflection" added 10 years after it's inception:

If your team is doing continuous delivery of software, I would suggest to adopt a much simpler workflow (like GitHub flow) instead of trying to shoehorn git-flow into your team.

I don't think this work flow is relevant any more even for teams that don't do CD, to be honest. It was a messy work flow to begin with and I haven't seen it applied successfully in practice.

Not sure I understand the use case and why something like VS Code's Git UI (or some other GUI) cannot solve the problem. Why does it need to be web-based, for example?

-1 is what you get back from fork() when it fails. Normally, it returns a pid_t which is positive if you're the parent, or zero if you're the child.

-1, when handed to kill() on Linux, means "target every process but myself and init". Therefore, when you take the return value from fork(), fail to check for an error, and later hand that value to kill(), you might just kill everything else on the machine.

Great story.

I think this may also be a problem with malicious clients. Currently the user enters the username and password via the client's login dialog. It's an effective way to collect credentials.

Not sure I got the question right, but it sounds like you can benefit from code reuse via shared projects or packaging different parts of the code into chunks.

I would definitely have the "Vital Contributor" badge if it existed.

You can change the captcha using the refresh button next to it. But Nd is not a problem. Its atomic number is 60. You need to add up to 200. Fm: 100, Zr: 40. I knew that memorizing atomic numbers would pay back some day :P

To me, there are two things that are valuable:

1. New developments in the language
2. Advanced techniques

That's why I follow these two channels:

• Zoran Horvat: In this channel, you will find advice on development and architecture in .NET and C#. He is really keen on functional programming and bends C# to fit into his preferences. Even though you are not so inclined, the way he uses the language really helps understanding some advanced features.

• Nick Chapsas: He explains language concepts in a comprehensible way. This is a good channel to follow new developments in the language.

No, it's not cheating (unless you are using it to do your homework, I guess). It's a tool and like any other we learn how to use it appropriately.

But one needs to be aware of other ethical concerns related to using AI generated code. The discussion revolves around companies (OpenAI, Github, etc.) training their models using the code written by people who have not consented use of their code as training data. In some cases, licensing is clear and allows for such use, but in some cases it's debatable (I'm not that much involved in those discussions, so I cannot provide more details).

When creating software, the value we bring is the understanding of a problem and the ability to ask the correct questions that will bring us to a good solution. In simple scenarios, even a machine can do what we do and we should definitely use the machine instead of spending time on that.

I think, in the short run, they are hoping some percentage of Rocky/Alma users will migrate to RHEL. I don't believe they are really thinking about the long term.