Agree, I have implemented a few provider and every time they implemented their own interpretation of the spec. In the end you end up checking each provider to make sure everything works as expected.
All 577 members of parliament are kicked and we will have to elect new regional representative (~equivalent to US congressman) on the 30th of June / 7 of July. They were initially elected one month after presidential election in 2022.
Under the line the president is asking something like: "Are you sure you want my politics to be far right?". If French people still elect a majority of far right congressman he will have (nothing mandatory) to build a government with far right minister.
I took it totally differently (it was humerous, with a hint of irony I'd expect a Brit[0] to appreciate): that due to Github's lack of resilience, the poster has had to become resilient in their own daily practice.
> You make it sound like you are better at running a system at this scale with so many users.
I don't care that the system scales to millions of people, my team is a dozen people, that's all I need something to do. And my downtime stats are far less that githubs, and they have never occurred during the working day.
Nobody denies scaling is hard, they simply deny scaling is necessary.
Presumably they intended to entertain. There are absolutely companies running much more complex services with more users than Github but better uptime, so it's absolutely fair to call Github out on their failures. Github has at least an order of magnitude fewer users than something like Google or Facebook.
If your attitude is reflective of the attitude of anyone at Github, calling people entitled who dare complain about the site's downtime rather than taking responsibility and working to better it, it's no surprise that Github has so much downtime.
You’re being really mean. Do you work for GitHub? Or do you just have a habit of taking things too personally? “i bet you can’t do better!” is not how an adult responds to someone expressing their displeasure at the fact that the performance of a service that they / their org is almost certainly paying for is below their needs / expectations.
Damn right I couldn’t do better. I’m also not the massive highly paid and talented workforce of GitHub. Next time you whinge about your mechanic not fixing your car or your plumber not fixing your toilet, I’ll be right there in your ear calling you a spoilt brat for not just doing it your damn self.
100% we rely on others for goods and services, regardless of our ability to perform said service we are able to (and should be able to) judge it. Otherwise everyone would need to be an expert in everything.
In other words, I don't need to be a banana farmer to say a banana is rotten.
I think a significant point in the 996 is also to ensure people are available, not only productive. Most probably are extremely productive few hours per day (let's assume 4) and few days per week (let's also assume 4). We could all be performing almost all our weekly tasks in about 16 - extremely targeted and focused - hours. SO it might be easy to think we should only be working 16 hours per week and that would be enough.
Yet, if people were only working 16 hour per week, the company would stop to a crawl. Because during my extremely productive, I might need a few non productive hours from you. Maybe it's answering a quick question, maybe is giving me a pointer to something, on inviting me to a document, enough that I can keep progressing without being blocked and getting those golden 16 hours interrupted and wasted.
The point is that, even tho these are not productive hours for you, they are creating a massive value for the company because you can be supporting other people productive hours. And maybe those are happening on a Saturday from 6 to 9 PM. In fact it might even be OK for the company to tire you a bit, to get that availability, even if that means you won't have 16 hours of quality work anymore.
This is not in defense on the 996, but it is to balance the whole point that people should only be working when they really are productive/focused/.... Availability, even non productive does matter as well.
