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.
Just wanted to point out that disabling SIP is not required to use most of yabai's window management features.
You do lose some features[0] but I've found the only ones I really care about is focusing spaces, and you can create keyboard shortcuts for that in System Settings.
I want to echo this as well. I use a 2nd tool to help me add additional i3-like keyboard shortcuts as well (I have the ability to "stack" windows with Alt-S and rotate through them with Alt-J and Alt-K).
Here it is. There is no visualization of the stack, which apparently Stackline in the other comment supports, but I don't tend to need that. Just being able to move between the windows is good enough for me.
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".
The jury is still out if I'm a good programmer, but I did one time need to use a hashmap that had to grow to about ~100gb in size. Because of that, I ended up calling it "bigassHashTable".
It makes me happy that it remained being called that for quite awhile.
I remember a day at a previous job when our CEO came in and told us we weren't an early stage startup anymore and had to start acting like it. Remove profanity and inside jokes from the code, and no more Quake during lunch breaks. Morale took a big hit that day.
if a CEO did that to me I'd just tell him to pull the stick out of his ass. none of it has anything to do with maturity.
but I'm relatively old.
you can Quake (or Overwatch or whatever the current game is) during lunch breaks at every FAANG, for christ's sake. (it's different if you're playing it during working hours.)
Yeah. Joking around helps build camaraderie, and makes people want to stay working there. I'm not sure who or where these hypothetical pearl clutchers, who can't handle a codebase with jokes or a bit of swearing, are, or why management care so much about them hypothetically encountering the codebase and getting upset. Sanitising everything and making it family friendly just makes workplaces even more soulless, rather than letting us have a bit of character in our work. At best it makes you look humourless, and at worst it can make people feel anxious about causing offence, if it's particularly strict policing
The best programmers I've worked with swore at their coworkers regularly, but never in their code.
They were not great people, and I'd happily kick them in the face if I would encounter no legal or professional repercussions, but, there definitely does seem to be some correlation (in my experience) between being abrasive and being a skilled programmer.
Swore at or swore while talking to? There's quite a big difference. I don't see profanity as inherently abrasive, and some of the biggest dickheads I've met in workplaces didn't swear much at all (some were of the Professor Umbridge type, so kept up an air of perfect professionalism)
literally right there in the comment. "swore at regularly".
Anyways, I definitely agree that swearing isn't the same as abrasive, but swearing at people is definitely an abrasive trait. Also agree that some of the biggest dickheads around keep up an air of professionalism.
RIP. Likely the Platonic Ideal of an abrasive programmer.
I'd put mid 00s Linus Torvalds as the apotheosis. Despite being an incredibly abrasive person, he has left a mark on history.
I just saw this earlier this week: Proton just added Calendar search to the beta Android app[1], and it looks like they are working to bring it to other platforms.
"In 1951, David A. Huffman and his MIT information theory classmates were given the choice of a term paper or a final exam. The professor, Robert M. Fano, assigned a term paper on the problem of finding the most efficient binary code. Huffman, unable to prove any codes were the most efficient, was about to give up and start studying for the final when he hit upon the idea of using a frequency-sorted binary tree and quickly proved this method the most efficient.[5]
In doing so, Huffman outdid Fano, who had worked with Claude Shannon to develop a similar code. Building the tree from the bottom up guaranteed optimality, unlike the top-down approach of Shannon–Fano coding."
I took Huffman's class at UCSC and he said he had actually thrown the solution in the garbage before realizing it worked and retrieving it.
When we started grad school, one of the professors introduced themself and said they thought it was interesting that adaptive optics was being used in astronomy and maybe the same idea could be used to improve microscopy and 7 years later a new phd was born doing exactly that!
Very cool. If you have a recent enough version of Redis, you may want to move away from doing the lookup using KEYS and move to SCAN (http://redis.io/commands/scan). KEYS will work for a while, but with a large enough DB it can become a very slow operation so it's not typically recommended for a production system.
Also, just curious, I see that the original url is encoded in the key, so the key is "<short>||<original>". Since the key is already a hash, it seems that you could eliminate having to scan over every key in Redis by making each key be only "<short>" and having an additional field in the hash for "original". Then a lookup becomes simply an HGETALL (if you need to get the "count" field, otherwise just an HGET for the "original" field). I might be missing something though! </armchair programming>
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.