Everybody on my team is required to do on-call once they have enough experience (except for the low budget offshore contractors who I wouldn’t trust to do it anyhow…)
We have 2 people on call at a time, 1 primary and one backup. You do a week on backup, then the next week you’re primary.
There’s no set time limits etc, but if you get sucked into some fire, people are reasonable about letting you take some time off the next day or whatever.
All in all, there are very rarely fires that happen inside or outside of normal working hours. Making the whole team be on call helps incentivize everyone to write more stable code since it’s your own ass on the line.
If I haven't played either RDR game, should I start here or play 2 first? It seems like 2 might be a better game and I don't have to worry too much about knowing the story from the first one?
The question is more about "how much" of PD they support right? Like PD has standards for charging at higher or lower currents.
My understanding of the current-gen MacBook Pro is that they support some kind of "fast charging", but only if you use their MagSafe port. You can still charge on the USB-C ports, but not as fast as you could with MagSafe. I'm not sure if that's a violation of the regulations, or if PD simply doesn't have support for the amount of power they're pushing through the MagSafe.
But I think the point is that they'll continue to look for ways to offer a better experience with their proprietary stuff, even if they're forced to support a standard in addition.
The real test on this one is going to be in how well those regulations support the eventual transition from USB-C to something else.
There's inevitably going to be a use case for new connectors that have some yet-unidentified advantage over USB-C for certain devices, and there's going to be hurdles convincing regulators to grant exceptions for those devices or to adopt one of them as the new standard for everybody.
There's plenty of examples of government regulations gone wrong trying to transition from an old technology to a new one. (i.e. the REAL ID format in the US, or the switch from analog to digital broadcast TV).
Could have just as easily said it would have been “much worse” without fossil fuels.
When soaring temperatures and demand for cooling led to a peak in Sicilian power demand on 24 July, nearly half of the excess demand - which totalled 1.3 GW - was covered by solar, Refinitiv data show.
So basically wherever the 1.3 GW of capacity came from (could be a bolt of lightning, or some Libyan plutonium, for example), it would have been much worse if they didn’t have it.
Yup. Nothing wrong with pushing up a draft PR and asking for feedback; but definitely need to be an active participant in fixing the issues, not just expect somebody else to do your work for you.
That does lead to some sticky inter-personal situations though. Like there's people on my team that I trust enough to just rubber-stamp a PR that looks good but doesn't have test coverage etc. Can generally trust those people will let me know if the failing tests uncover some substantial work that needs to be re-reviewed.
There's other people I don't trust and will insist their build passes before I review it. Once that person notices they're being held to a different standard, it can be difficult (but necessary) to have a conversation about what they need to change in order to earn that trust.
HairHeel @ HairHeel @programming.dev Posts 1Comments 105Joined 2 yr. ago 
Must be nice working at a place where that ticket doesn’t just get dropped into the dev backlog as-is.