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.
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.
bashmount
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.
Congrats on inventing what high school students figured out a year ago to skirt AI homework detectors.
Systemd does about 60 different things now. Which ones did you want a GUI for?