I’m pretty sure that 5 is a feature because the button that moved is usually replaced with a clickable ad.

Sounds like SAP.

I think that there is always an implied design requirement of the program shouldn’t crash.

There’s a setting on the phone app to block notifications when you’re active on the desktop. It works well for me.

I don’t think that I get meeting notifications on my teams on desktop either so they just come up in outlook.

There are people in my org that always start with a “Hi” and then send each sentence as a new message. Very irritating.

The idea is that you can have more data online than you can fit on your computer.

It makes sense for SharePoint when there can easily be enough data to cause space problems on employee computers.

It doesn’t really make sense for it to be the default for personal OneDrives though.

I think that the main difference is that developers tend to test for success (i.e. does it work as defined) and that testers should also test that it doesn’t fail when a user gets hold of it.

I have worked with some excellent testers but I have also worked with a team that literally required us to write down the tests for them.

To be fair, that wasn’t their fault because they weren’t testers. They were finance people that had been seconded to testing because we didn’t have a real test team.

The current team is somewhere in between.

I wish our test team was like that. Ours would respond with something like “How would I test this?”

We don’t get that lag but we do frequently get it when the camera doesn’t work for somebody.

I really can’t understand the separation between teams, channels and chats. We almost never use anything other than group chats.

Microsoft SQL Server is most commonly set up as case insensitive in my (limited) experience (it does support case sensitivity too).

Maybe it’s not changed then because I was using it in the early 2000s. 😀

We used to use Redmine and it was a fantastic piece of software.

I’m not sure that’s the fault of XML though.

It’s more the fault of the implementation and documentation.

We have a WCF service with an odd configuration and nobody has been able to integrate with it that didn’t use Microsoft tools. It’s definitely not XML’s fault.

(That service has been replaced with a REST API now)

It seems that they intend Microsoft Loop to be the collaborative notes app now.

It’s replaced OneNote as the meeting notes app and it has more flexible access control.

Currently they also only have one version as it’s a progressive web app (that might change with time though).

I guess that that’s all that matters.

Did it take time to get used to or did it work straight away?

Hopefully, the UK is going to take a couple of steps to the left shortly.

If it does, it’s not because the country is moving left but because the right fucked up.

Is it saying that the PHP developers are kids and the C++ developer is acting as their parent?

I’m not sure.

If you want to fork the repo then you make a commit to the original repo giving yourself rights then you make the fork and you’re golden.

I don’t understand why people think that it’s acceptable.

As developers, we’ve had it drummed into us from day one that variable names are important and shouldn’t be one or two letters.

Yet developers deliberately alias an easy to read table name such as “customer” into “c” because that’s the first letter of the table. I’m sure that it’s more work to do that with auto completion meaning that you don’t even need to type out “customer”.