recentpopularlog in

kme : communication   86

« earlier  
Zuckerberg Plans to Integrate WhatsApp, Instagram and Facebook Messenger - The New York Times
Knitting together Facebook’s apps is a stark reversal of Mr. Zuckerberg’s previous stance toward WhatsApp and Instagram, which were independent companies that Facebook acquired. At the time of the acquisitions, Mr. Zuckerberg promised WhatsApp and Instagram plenty of autonomy from their new parent company. (Facebook Messenger is a homegrown service spun off the main Facebook app in 2014.)

WhatsApp and Instagram have grown tremendously since then, prompting Mr. Zuckerberg to change his thinking, one of the people said. He now believes integrating the services more tightly will benefit Facebook’s entire “family of apps” in the long term by making them more useful, the person said. Mr. Zuckerberg floated the idea for months and began to promote it to employees more heavily toward the end of 2018, the people said.

The effort has caused strife within Facebook. Instagram’s founders, Kevin Systrom and Mike Krieger, left the company abruptly last fall after Mr. Zuckerberg began weighing in more. WhatsApp’s founders, Jan Koum and Brian Acton, departed for similar reasons. More recently, dozens of WhatsApp employees clashed with Mr. Zuckerberg over the integration plan on internal message boards and during a contentious staff meeting in December, according to four people who attended or were briefed on the event.

For Facebook, the move also offers avenues for making money from Instagram and WhatsApp. WhatsApp currently generates little revenue; Instagram produces ad revenue but none from its messaging. Mr. Zuckerberg does not yet have specific plans for how to profit from integrating the services, said two of the people involved in the matter. A more engaged audience could result in new forms of advertising or other services for which Facebook could charge a fee, they said.
facebook  instagram  whatsapp  messaging  communication  mergers 
july 2019 by kme
Keybase is not softer than TOFU
In cryptography, the term TOFU ("Trust on first use") describes taking a gamble the first time 2 parties talk. Rather than meeting in person, you just trust a party in the middle to vouch for each side...and then, after the initial introduction, each side carefully tracks the keys to make sure nothing has changed. If a key has changed, each side sounds the alarm.

Similarly, in SSH, if a remote host's key changes, it doesn't "just work," it gets downright belligerent:

Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
Please contact your system administrator.
Add correct host key in /Users/rmueller/.ssh/known_hosts to get rid of this message.
Offending RSA key in /Users/rmueller/.ssh/known_hosts:12
RSA host key for has changed and you have requested strict checking.
Host key verification failed.</code>

This is the right answer. And make no mistake: TOFU isn't TOFU if it lets you keep going with a cute little shield that flows by. You should be seeing a giant skull and crossbones.
crypto  security  tofu  privacy  communication  chatapps 
june 2019 by kme
To Pair or Not to Pair: Pair Programming - YouTube |
Lady's from ThoughtWorks (, and if that's sounds familiar, that's because they're the Selenium and GoCD people.

Benefits mentioned in the video:
1. knowledge sharing (1 + 1 > 2)
2. combines two modes of thinking: tactical (driver: local optimization), strategic (navigator: big picture)
3. reflection (on the story, value-added, effectiveness vs. # of LOC)
4. helps coder / team focus; discipline around structure of code, strategy, explain and justify choices, avoid rabbit holes
5. "I get more programming productivity" out of reducing time that I'm stuck than from increasing my speed when I'm not stuck."
6. helps practice "true" CI--code review on-the-go; more collective code ownership; >> trunk-based development

1. don't do it for 8 hours a day
2. take breaks; it's exhausting
3. even skill levels
4. share feedback (I don't like it when ...), exchange READMEs
5. "the shame of pair programming"; requires vulnerability

Homogeneous teams feel easier, but easy is bad for performance. (ref:

The authors are saying that this idea goes against many people's intuition, and often if there's something counter-intuitive, there's a cognitive bias hidden away somewhere, right?

And the one that they're mentioning here is the "fluency heuristic," which says that we prefer information that is more easily processed, and if it's easily-processed, we think that it's more true, more right, more beautiful, and that serves us very well in a lot of situations in software development. We want readable code, easily-processable things. But I don't think that it serves us well if we think that's why we're not doing pair programming.

So, pairing feels hard, but that doesn't mean that it's not good for performance, and also it doesn't have to stay hard.

Ways to make it easier (reduce friction, conflict, anxiety):
1. get the talking going
2. active listening
3. friendly feedback
4. answer why

See also:
agile  cs  programming  pairing  pairprogramming  teamwork  collaboration  communication  conference  talk  video 
december 2018 by kme
The War on Developer Productivity (And How I Intend to Win It) -
Chat is a greedy mode of communication.

* It doesn’t care if you are deep in flow.
* It begs you to incessantly clear its notification badges.
* It buries important conversations among idle chatter when you snooze it.
* It must be used with restraint or it becomes toxic.
workplace  productivity  chatapps  slack  distraction  chat  collaboration  communication 
june 2018 by kme
Write clean code and avoid the distractions of emerging technology |
The coding hours you put in with more stable tech mean better verification of correctness due to the great amount of literature and experts in these areas and more chances to master the act of writing code for the consumption of other humans. Practical software development has always borrowed from multiple paradigms and you will find it possible to move between them when natural glide paths arise. Forcing this out of fear of being left behind is not helpful.
devel  programming  communication  forhumans  advice 
april 2018 by kme
Google's Unwritten Rule for Team Collaboration |
That social code was tacitly agreed upon, and usually instituted by the managers: the most collaborative teams, even if they have a single leader or moderator, were ones where everyone spoke equally.

This fact wasn’t written down anywhere, or decided upon by management. The teams themselves didn’t even notice they were doing it. But researchers recognized that less successful teams were the ones where a manager spoke 80% of the time or more. In successful collaborative teams, everyone engaged in “conversational turn-taking”—one of the most human things we do— whether it was through a daily standup or a monthly check-in.

Since the conversation wasn’t monopolized by one person, they were able to ask clarifying questions and give their input. In situations where only one person speaks, team members didn’t feel comfortable voicing their ideas, chiming in on other peoples’, or correcting their more vocal team members’ mistakes. Imbalanced communication, in short, defeated the purpose of collaborating in the first place.
teamwork  collaboration  communication  bestpractices 
november 2017 by kme
Slack re-invents the extranet and shared Notes databases with cross-company teams • The Register |
Sounds good, eh? And doubtless it also sounded good in the mid-1990s when Lotus/IBM/Notes/Domino allowed shared databases and applications that could include users from across different organisations. In those far-off days your correspondent worked with clients who insisted on that arrangement, deeming emails a blunt instrument and forcing us to acquire some Notes licences that IT really wasn't very keen on.

Not many years later, vendors who caught the Intranet bug took things a step further by cottoning on to the idea of an “Extranet” that could be accessed by third parties outside the firewall. That idea was even layered on top of SharePoint a decade ago.

Slack probably doesn't care that it's not entirely original, because its business is built on taking collaboration ideas that never evolved and making them more usable. The company's core group chat functionality has been around for decades but never evolved to take advantage of modern PCs' powers, or made it easy to play with images and links.
slack  communication  lotusnotes  whatsoldisnewagain 
november 2017 by kme
Why I am not going to buy a cellphone | Aeon Ideas
The decisive reason, however, for me to refuse a cellphone is the opposite of everyone else’s reason for having one: I do not want the omnipresent ability to communicate with anyone who is absent. Cellphones put their users constantly on call, constantly available, and as much as that can be liberating or convenient, it can also be an overwhelming burden. The burden comes in the form of feeling an obligation to individuals and events that are physically elsewhere. Anyone who has checked their phone during a face-to-face conversation understands the temptation. And anyone who has been talking to someone who has checked their phone understands what is wrong with it.
humans  cellphone  communication  consumerism 
march 2017 by kme
What communicating only in emoji taught me about language in the digital age — Quartz
“When people interact, 60-70% of meaning is derived from non-verbal cues—gestures and facial expressions,” said Vyvyan Evans, a professor of linguistics at Bangor University. (This is also why, by the way, that ending correspondence without a smiley can seem curt.)
communication  emoji  language  email  chat 
september 2016 by kme
Jan Chipchase: The anthropology of mobile phones | Talk Video | TED -
Meh. But I thought the part about Sente ("money," to send money as airtime) was interesting.
money  africa  mobile  communication  cellular  anthropology  memory  video  ted 
march 2014 by kme
Lync Server settings when using Pidgin instead of Microsoft Lync chat client - IM, meetings and conferencing - Office 365 - Microsoft Office 365 Community
Pidgin now has semi-experimental support for connecting to Office 365. You will need Pidgin v2.10.1 or greater as well as the SIPE plugin v1.13.0 or greater. There is an FAQ for the SIPE plugin listing the required configuration settings and solutions to common issues. Good luck everyone!

P.S. if does not work for you, try
microsoft  lync  sip  chat  pidgin  communication  openstandards 
august 2013 by kme
Ross Barkman's GPRS/UMTS Info Page
T-Mobile (non-contract)
guest / guest
cellular  mac  mobile  osx  phone  reference  communication  solution 
july 2013 by kme
« earlier      
per page:    204080120160

Copy this bookmark:

to read