I am curious about what will happen next month. Will Mythos find 500-1000 new bugs or will Mozilla have fixed every bug pattern Mythos knows and they will get few if any additional bugs? Will Mythos start hallucinating bugs or suggesting exploits that require an impossible coincidence to occur?

How many Linux distros include micro in their minimal image? Vim, emacs, and nano are good because I can connect to just about any container or Linux VM and expect to have all of them available.

Let's say I have a test that always passes on my machine but fails in CI. If I can get a terminal on the test runner, I can open up my test code in vim, add extra logging and error handling, and rerun the test to check my fix.

I am not going to install additional editors in a VM that will be recreated next time I push a code change. If I am setting up a development environment for long term use, I will install my favorite IDE and configuring all the bells and whistles.

I agree. The article the article assumes that junior developers are tasked with doing tasks that senior devs will not (such as writing buggy boilerplate or something). That has not been the case with companies I worked at. When we hired a junior developer, we expected them to write the same code as everyone else, just that they would ask for help more often and would get more nit-picky code reviews. An AI could probably outdo a junior developer with a month or two of experience, but with a (junior) developer, the expectation is that if you take the time to explain to them why their code is wrong, they will never make the same mistake again.

I agree with you that it comes down to the state of the economy. Ten years ago, I was at a company that could not hire senior devs fast enough so we had to hire junior devs and mold them into the coders we needed.

Now I am at a company that has had a hiring freeze for several years. All new hires we are getting are back-fill: when we have someone quit, we can request a replacement. Anyone we hire needs to be able to hit the ground running and take over the previous employees responsibilities as soon as possible.

I have used Alpine Linux at work and I don't like the fact that they only have one version of each package in their repo. First of all, that creates a risk that a given version is bad and I cannot go back to a known good version. Also, some times I explicitly want to use an old version of a package. New versions change and remove features.

Yes, but perfectly reliable hardware is impossible and every small gain in reliability drastically increases the price. Luckily, most hardware can be "fixed" by replacing the malfunctioning part. The only part that is not easy to replace is hard drives. For data disks, I have guides giving me step by step institutions on how to rebuild off of replicas. With the OS disk, I am depending on hopes and taking notes while installing.

Broken software is tricker to replace. I can uninstall and reinstall it, but I have to be careful to avoid catastrophic data loss. Also, broken software generally means a bad release, so I have to revert and periodically upgrade/revert to check if the issue has been resolved. And running old versions of one part of the system can cause incompatibility in other parts.

The reason that I was favoring Greyhole over ZFS is that I want to assemble a large, redundant storage volume out of a bunch of mismatched old disks and swap them out as they fill up or fail. I know it is very possible to do it with ZFS, but it seemed to not be the general use case and complicated.

No idea, but I am not sure your family member is qualified. I would estimate that a coding LLM can code as well as a fresh CS grad. The big advantage that fresh grads have is that after you give them a piece of advice once or twice, they stop making that same mistake.

No idea, but I am not sure your family member is qualified. I would estimate that a coding LLM can code as well as a fresh CS grad. The big advantage that fresh grads have is that after you give them a piece of advice once or twice, they stop making that same mistake.

…and Python, Java, and GoLang.

At least with Java, many of the cornerstone packages have a corporate sponsor maintaining them.

What language is that? That does not conform to duck typing.

Most people turn 18 during the last year of high school, which means that there is a very significant chance that the dev in question is still covered under child labor laws.

Maybe it is because I grew up in the North East United States, but when I was in high school, my classmates only worked seasonal or afternoon jobs.

Not sure what distributed/micro service stack you have, but Go is used a lot for Kubernetes and Terraform utilities, so the client libraries are well supported and there is a lot of sample code. Our main application is in Java, but we have a Kubernetes operator for SaaS instances and a Terraform provider to install it, both written in GoLang.