You can't fight your own mind, you are your own mind. It's like a machine trying to fix itself. Depression leads to self-destructive behavior, including the irrational wish to be alone with terrible thoughts, which continue until you get exhausted enough to sleep, snap out of it, or ...

"we sometimes sight of our history" I see what you did there.

plugging it into a keyboard and display as necessary. What we need are devices which connect effortlessly to authenticated devices like keyboards, displays, mice, printers, and others which for ergonomic reasons can't be made part of the "hub". Current hardware is more than capable of this, but it would require vendors working much harder on interoperability.

Jeff, Larry: The plural of anecdote is not evidence. It seems every parent ever has discovered at least one panacea for misbehaving kids, and this one doesn't sound any better than most. The mobile guy was just venting, and it doesn't sound like he was about to start crying or hitting anyone until he got a better signal. Patronizing him that way would at best made him realize that he was pointlessly venting among strangers who couldn't help him (thus shaming him into shutting up), or at worst would have made him angry for treating him like a baby.

Anyone who makes salary, personal or other decisions about people who call themselves coders, hackers, programmers, developers or similar should learn to solve a real-life problem by programming and all that that process entails (encoding, i18n, lint, security, etc.). Given sufficient training, these people would gain a healthy respect for the seemingly enormous time it takes to solve problems which are simple to formulate (and which are only attempted because we're standing on the shoulders of giants), the complexity of existing programs, and just how much of a tossed-together mess 99.9% of all code is, including the reasons thereof.

While most meetings (especially "fluffy" ones) should be optional, what about smaller ones to synchronize the team on what's going on? There's the risk that someone who simply doesn't like meetings will happily slog on until it by accident becomes clear that she's working in the wrong direction or is hopelessly stuck?

The password could be selected by using a hash of some private information and some web site information (private / public keys come to mind). An issue with this approach is when things change - As they can and will. You also need to be able to shift between contexts on the client side to enable more than one account per web site.