betamike

This is what my last, 6 person, startup used, and it was really helpful. It lowered the barrier to having a quick discussion, since you could see if someone was at their "desk" or busy in a meeting.

Also you can see if other teammates are having a discussion or co-working in a common area, which made for some ad-hoc co-working sessions.

Author here, and yep! We eventually want to offer those kinds of enterprise features (SCIM, syncing group membership from Okta/other IdPs), so I kept that in mind throughout the process.

While I haven't gone too deep on that yet, I was thinking we'd take inspiration from how GitHub maps IdP groups to native GitHub teams. So first step here would be adding user groups/teams natively in the product.

I skimmed the paper, and it looks like they are looking for swearing _anywhere_ in the repos' code, not just comments.

I would be curious to see the ratio of swearing in comments vs code identifiers. I'd also be curious to see if the repos with swearing in their comments just have more comments in total. Perhaps the correlation is, "code with more comments is more likely to be higher quality".

Just a note for anyone checking it out, Simple Keyboard doesn't support spellcheck (which is why I use OpenBoard instead).

Just for some additional search terms, seitan is a form of prepared Vital Wheat Gluten.

When that option is enabled, audio will not continue to play in the background.

Alternatively you can go to Google+, right-click the search bar and select "Add As Search Engine..." You can then change the keyword to "+" or "plus", and do the same thing.

You can define a category within your implementation file (.m) and redeclare the property like this:

@interface MyClass (PrivateMethods)

@property(readwrite, retain) NSObject *myProperty;

@end

@implementation MyClass ...

Now only your implementation knows about the generated setter methods, and you don't have to implement them yourself.