recentpopularlog in

kme : consideredharmful   22

How Slack Harms Projects – Silas Reinagel
Because of the ability to quickly follow up messages with other messages, and the natural disposition towards short messages, the natural tendency of most information works is to message first, think later.

Got a half-formulated question? Send a group message.
Don’t want to Google something? Send a group message.
Unsure if the software is working correctly? Send a group message with a bunch of @ tags.
Want to ask someone specific about something? Say “Hello” and wait for a bit before stating the real purpose of a message.

Real-time messaging encourages little thinking, and brings many people to waste time while staring at the “XYZ is typing a message…” indicator in the bottom-corner.

Both Emails and Tickets are a much more professional business communication medium, since they encourage providing all the information BEFORE clicking send rather than after.


From the comments:
Are you familiar with Marshal McLuhan's idea that "The Medium is the Message"?

If you are, then you will understand that real-time chat systems are, by their very nature, communicating that what is recent is the most important thing, and what isn't recent is unimportant and hardly worth seeing.

While people can build effective strategies to minimize the impact of a given medium (like my father, a very successful electrical engineer, did with television, by having only a 5-inch black and white television, and keeping it under the sink, when I was growing up), that doesn't change the way a given medium generally impacts people.

The problem is the tool itself. The urgency is a partial by-product of the tool.


See also: https://disqus.com/by/disqus_qfS4hiBdrC/
slack  chat  consideredharmful  workplace  productivity  collaboration  culture  immediacy  instantgratification  forthecomments 
october 2019 by kme
Some final notes about LMDB review - Ayende @ Rahien | https://ayende.com/
Given what I've seen about the common wisdom of good code, I'd say most of it is garbage. Good code is code that yields the correct result using the fewest resources. In particular, your notion about gotos:

http://www.u.arizona.edu/~rubinson/copyright_violations/Go_To_Considered_Harmful.html

It's an interesting argument, but it all comes crashing down in the very last sentence:

"In [2] Guiseppe Jacopini seems to have proved the (logical) superfluousness of the go to statement. The exercise to translate an arbitrary flow diagram more or less mechanically into a jump-less one, however, is not to be recommended. Then the resulting flow diagram cannot be expected to be more transparent than the original one. "

Fundamentally all of those structured programming constructs are just fancy dressing for gotos. When using them gives a compact representation, use them. When using them just complicates the apparent flow, use a goto. It's that simple.
lmdb  codereview  goto  consideredharmful  programming  forthecomments 
november 2017 by kme
Should I set LD_LIBRARY_PATH?
The short answer is never.
[Local mirror site's addendum: Usenet poster Dan Espen recommends, instead: "LDFLAGS='-L/my/strange/path/lib -Wl,-rpath /my/strange/path/lib'"

You might need to 'make distclean' and re-run './configure' after this, if you had previously exported 'LDFLAGS' before running it the first time.
unix  build  toolchain  ld.so  linker  libraries  consideredharmful  bestpractices  devel  reference  solution 
february 2016 by kme

Copy this bookmark:





to read