As a manager? Coach your report on his soft skills. Software dev is about being a good team member as much as a good individual contributor. If the strongest guy is dominating meetings and dominating the team's direction with his opinion, that's something to work on.
He has to give others space to contribute by not jumping in. And his manager should be coaching this directly. As the EM, you want your whole team to be able to confidently do what he does. Functioning teams have multiple engineers concurrently owning your scope.
If your company isn't toxic, over-working would also be seen as a negative because of the precedent it sets. If this guy wants to be a leader and not a monkey, he has to appreciate that. And senior/staff counts as "leader" here.
It is warmer than -16C/3F at Chicago (O'Hare) for 99% of the time (i.e., except for 4 days a year), and warmer than -18.7C/-2F for 99.6% of the time (2 days).
ASHRAE are the folks that publish the heating/cooling standards that are used in building codes for estimate heating/cooling equipment capacities (Manual J) and selecting the right equipment (Manual S).
Here's a PDF with a lot of locations in the US and CA (and other countries further down), and if you look under the "Heating DB" column, you'll find very few US locations that have -30F under the 99% (or even 99.6%) sub-columns:
So unless you're in AK, MN, or ND, long runs of temperatures colder than -20F/-30C don't happen too often. Of course if you have a leaky house with little insulation, you're throwing money out the window/door, so the first consideration for a good ROI is better air sealing and insulation.
I think the comment was saying below 30F and below 10F. Much warmer than you're saying.
Also..
> It is warmer than -16C/3F at Chicago (O'Hare) for 99% of the time (i.e., except for 4 days a year), and warmer than -18.7C/-2F for 99.6% of the time (2 days).
If my heat doesn't work for those days, I'm kind of boned. Four days per year without a working heat pump? That's a mess.
At face value, then in the worst case that's just 4 days per year of using resistive heat to keep a home warm.
Which is, of course, very expensive to use -- but it's only expensive for those 4 days. Resistive heat can be avoided for the other 361.2425 days in a year.
In the US (as of August of 2025), the average price of residential electricity per delivered kWh is $0.1762 [1].
If using resistive heat averages 4kW during each of those 4 days (it's probably either more than that, or less than that, but ballparks are ballparks), then that's about $16.92 for each of those days. Or: $67.66, per year.
> At face value, then in the worst case that's just 4 days per year of using resistive heat to keep a home warm.
The design philosophy for using 1% is that you may end up having to run your heating (or cooling) 24/7 to keep up with temperature delta between outside and desired inside, but it will keep up with the demand.
The rest of the time (99%) the mechanicals only run intermittently. Also note that the 1% would not necessarily occur every year: it is just the historical average. The charts also have the 0.4% extremes if you want to be extra conservative, but most building codes specify 1% because that is what experience has shown is a good trade-off.
Part of the process (in the US) is to use what is called the Manual J to determine/estimate/calculate how much energy is needed to maintain a particular temperature (typically ≥70F/21C in winter, ≤75F/24C in summer):
> The Cooling Design Day is effectively the "worst case" day for your air conditioning loads. The "worst case" hour of this day determines equipment capacity, fan sizes, and subsequently duct sizes. This largely impacts first cost. The Design Hour also impacts peak KW demand which often has a huge impact on the utility bill.
The United States' way of government was revolutionary for its time, based on the cutting edge of human philosophy in many ways. The Bills of (negative) Rights in particular.
It is a shame that it is being destroyed at lightspeed the last year, and worse that many don't seem to care.
> The bank loans would be part of the Trump administration’s plan to backstop the finances of libertarian President Javier Milei’s government with a $40 billion package, including a $20 billion currency swap with the U.S. Treasury Department and the separate $20 billion bank-led debt facility.
Seeing all those SRFI's listed, etc, on that page (63 of them), is astounding. How long would I have to work with scheme to get to comprehend what each represents without looking them up Captain Wimby's Bird Atlas of Nomenclature? What percentage of the people who take the time to read that page, for example, if they are trying to learn if Chez Scheme might fit their needs for a language implementation, are going to get a good idea about anything by scrutinizing that list? Isn't that like a bookstore filling its advertising with a list of ISBNs? I have tried to do some stuff with scheme at times in years past, and when I saw such lists galore with no plain-language information attached while trying figure out which tool to grab, it gave me some idea that the scheme community was a somewhat isolated ethnocentric culture of its own.
Page doesn't seem to be all-inclusive in vein of awesome lists (such as github:schemedoc/awesome-scheme) but concentrated to author's own projects (Gauche and apps/libs). And maybe doesn't get updated beyond those (e.g. Bigloo homepage has been moved to https://www-sop.inria.fr/indes/fp/Bigloo/ years ago; probably before Chez became open which may be another reason it didn't made it to the list).
He has to give others space to contribute by not jumping in. And his manager should be coaching this directly. As the EM, you want your whole team to be able to confidently do what he does. Functioning teams have multiple engineers concurrently owning your scope.
If your company isn't toxic, over-working would also be seen as a negative because of the precedent it sets. If this guy wants to be a leader and not a monkey, he has to appreciate that. And senior/staff counts as "leader" here.
reply