Read Software Estimation by Steve McConnell and recommend it to your manager:
The person doing the work the one best suited to estimate it.
Also, start tracking estimated vs budgeted time in some searchable system.
Next time this comes up, look up how long it actually took to complete a similar task instead of thoughts and prayers.
If boss won’t track historical budget vs actual, track it yourself.
Asahi Linux completely supports all the M1 Mini hardware.
But it does look the prices on these went back up because people use them for OpenClaw. 🙄
I run Asahi Fedora Linux on this hardware. It was a straightforward install and has been problem-free since.
It’s nice that some resources are being directed in this area, but it’s far from a total solution.
For example, the passport-saml Node module is popular and security related and is already fielding a number of AI-assisted security vulns.
Even when they are contributed by “security experts”, they still have to be carefully vetted to confirm they are correct and not themselves malicious.
While the patches may be good, it appears to be generating more unpaid volunteer labor for the maintainers.
Thankfully there some other fund’s trying to help out maintainers of critical open source projects.
The Code Rabbit link is about software in general, not the Linux kernel in particular. In many ways the Linux kernel is an outlier among software projects. When it comes to LLMs, I don’t expect devs will be using lower standards for code reviews in quality, while some other teams definitely are doing light “LGTM” reviews of AI code.
The second link expresses a lot of concerns about plagiarism by AI. Certainly related care needs to taken for contributions to the Linux kernel. As far as I could tell, no specific cases of plagiarized code in the kernel were cited.
M1 Mac Mini is quiet, fast, low power consumption and reasonably-priced used.
The log volume is dependent on which services are running and how they are tuned.
Alexa, what are some baby names to avoid today?
The high-res version would make a challenging 1000-piece puzzle.
That pattern is also recommended in the book. Break down estimates into chunks of 5 hours or less.
With lots of smaller tasks, estimates tend to both be more accurate due to smaller scope, and some of the over/under inaccuracies will cancel out.