3 ms·

It's not surprising. I don't have any data to prove it but it feels like they're shipping improvements and new features at a much faster rate.

• stupidcar 6y ago
  Or it could be some of the older employees decided to cash out after the acquisition, and they've lost some institutional knowledge about how to keep things running smoothly?
  • user5994461 6y ago
    The addition of interns and new members typically cause more outages, as they make a lot of changes and discover how things work or not. Retaining older employees has little effect to prevent that, because they typically don't/can't review much of what's happening from a new team, sometimes a whole department, who joined in on the project and has its own agenda.
• sammorrowdrums 6y ago
  I was just thinking that Github stayed fairly consistent and Bitbucket didn't really challenge it on features, and then Gitlab came in, shipped loads of popular features and lots of CI functionality, and Github has been delivering a lot of new features a lot faster ever since really, so I think Microsoft acquisition is quite possibly not a root cause of downtime changes. It's also worth noting that downtime and issues caused during updates in self-hosted Github are significant. I have experienced them, and I guess the main difference is actually that you can schedule the risk, rather than accept it arbitrarily which has positives but comes at significant cost too.
• mattigames 6y ago
  And not for the better, imo the new UI sucks, mostly my eyes have to travel much more than before for the same amount of info.
  • linkdd 6y ago
    that's called changing your habits. In 6 months when your eyes remember where are the pertinent information, you will say the same about the old UI. More information is displayed in a more concise way since the update.