#2 Are there related changes on the horizon for the code being refactored?
I think more qualifications than that probably miss times you should refactor.
#3 Has the code been changing recently OR have changes been delayed because modifying the unrefactored code is considered too difficult.
I've seen too many times where unrefactored code is considered too dangerous/difficult to modify even with total test coverage. Refactoring is a necessary step towards self documenting code in those cases.
Recommendation for eating spaghetti squash in the spaghetti style, use half actual spaghetti pasta. You get the taste of pasta you're craving in each bite but with half the benefits of substituting of a full plate of spaghetti squash.
Batteries are not cheap, but they are cost effective based on local conditions.
Time of use billing. The battery is generating ROI if it can arbitrage energy over the day.
Net metering + solar. If net metering is not available, or sufficiently discounted, and your energy usage is not high enough during the day to use all your solar power, then batteries generate ROI.
Grid stability. A battery effectively is insurance against outages of a few hours. With sufficient solar and rationing, that may extend to week long outages (think natural disasters).
I've often thought an authenticated proof of donation to a global charity could be a solution to these types of problems, scaled in price to the senders locale.
Not refundable, but at least a donation to UNICEF allows the receiver to impose a submission cost without the implication they are doing so out of greed.
One way to approach the engineering question of how to make solar cars for the mass market is to push the car body design to be extremely efficient. Aptera's three wheel, two seat, design seems more likely to deliver the type of daily range extension that will make solar cars a contender in the market.
There are some YouTube channels that specialize in landscaping. I could see digitally and entrepreneurially minded landscaping professionals being a good part of their audience. Might be worth sponsoring a video or two.
A 4 or even 3 percent withdrawal rate is more likely to be sustainable. Those are also rates I see suggested more commonly on retirement planning sites.
Test order should be random, so that the ability to run them in parallel and distribute them across multiple hosts is not lost by missing enforcement of test isolation.
#2 Are there related changes on the horizon for the code being refactored?
I think more qualifications than that probably miss times you should refactor.
#3 Has the code been changing recently OR have changes been delayed because modifying the unrefactored code is considered too difficult.
I've seen too many times where unrefactored code is considered too dangerous/difficult to modify even with total test coverage. Refactoring is a necessary step towards self documenting code in those cases.