#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.
Scandinavian layout (often called "ISO-nordic") is the exact same ISO/IEC 9995 standard as all other ISO keyboards. Same physical layout. Just a few keys/legends mapped differently.
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 think a solar system that also gives you independence from the grid is much more expensive, the program that we are using to get some subsidies do not include this extra features , so if power is out even if we have solar we still be out of power. Maybe in 10 years or realistically more a more advanced system would be worth it for my situation.
Yes indeed, even a small battery that allows you to shift the late afternoon usage of your house away from the grid will generate ROI by saving you electricity cost compared to a lower feed in tariff during the day.
#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.