I recently wen to a chain cinema instead of the independent one near my house. We were treated like cattle, given assigned seats (!?), and had to endure advertisements on the screen before the movie. I don't mind a printed add in a slideshow of movie trivia to show your stub for a free dessert at a nearby restaurant or something like that. These were like TV commercials with sound so loud you could not talk to your friends that lasted a minute or more with no redeeming content between them. Even if the movie had been really good the entire experience would be tainted.

With Netflix, Hulu, Amazon streaming, etc. you can wait and watch it at home cheaper. The reason to go to the movies is the experience. Improve the experience and people will come. Treat people like cattle and they will stay away. Our local cinema has a bar attached, real butter on the popcorn, and only shows previews before the movie. They actively try to create a community by showing classics at midnight on weekends, hosting movie trivia contests, and showing locally produced movies including a Q&A with the makers. They participate in film festivals. It isn't that hard.

Who says well behaved bitches don't make history? (tongue in cheek) The real story in my mind is that there wasn't even a plan to bring her back. What possible use is there to sending her up in the first place? To say you have done it? Why should anyone care? OK, it was a first, but it is a successful operation where the patient died. At least the humans volunteering to go to mars with no hope of return are volunteers.

I've learned two things that every large organization needs, identity management and IT asset management. Currently I am supporting an identity and access management solution. I'm using SSIS, PowerShell, Python, and C# to customize and add functionality. It isn't challenging and I hope to retire soon.

The article did not say, but I assume that the issue is primarily collision avoidance. This position data could be sent to AIS so that other ships know their position, speed, heading, DSC information, name for hailing purposes, etc.

If you crossed the Atlantic using celestial I am going to guess it was on a sailboat going well under 10 knots on a good day and you probably stayed out of major shipping lanes. A ship would see you soon enough to avoid collision (and vice versa though you would be the stand-on vessel). Two ships going 25 knots that would meet head-on would see each other on the horizon something like 3 minutes before the collision. That isn't much time, especially since these ships are not very maneuverable.

There isn't enough time for mentoring in a large group for three hours. By all means have a handout with sites/articles and books. There are some good suggestions like Code Complete, but you don't have time for that either. Start out by reading this: 201 Principles of Software Development and put together a narrative on how to develop requirements, how tests are based on requirements, what makes a good developer, etc.

My brain decides to store things I don't care about and refuses to store things I specifically study. I can remember many memory tricks, but using them does not help. I can rattle off the wives of Henry the VIIIth despite not taking history since high school, but not the names of people I just met and have tried to remember. I can tell you a lot about some random things I looked up once, but don't ask me my license plate number.

Think of the films made of Puppet Masters and Starship Troopers. Perhaps TV will be kinder. Never Thirst.

The Puma won't catch on for the same reason the Segway didn't. The major needs in transportation are speed, climate avoidance, and cargo carrying capacity. None of those is met by the Puma or Segway. Making it autonomous doesn't improve the utility much beyond not needing a parking spot.

Is this just for shock value to sell ads/papers or serious?

Not everyone can (or should) be a programmer. They need to promote themselves as a collaborative environment for everything and differentiate themselves from Google Drive. It is much easier to see who did what and when in git and any file type is possible. There is no good way to do file compare on some file types within GitHub, but that could be fixed. The loss of seeing the edits that other people make in near-real-time is probably no big deal.

They seem to be stuck in the Uranium/Plutonium paradigm. A conspiracy theorist could have a field day speculating why.

The needs of most people will be met by Google Apps in the near future. They aren't quite there yet. Already my issues with Google Docs are about the same as moving from LaTeX to MS Word back in the 90s. Ease of use will trump elegance and "extra" features as soon as most people have the features they NEED. People's expectations of output quality will adjust. The spreadsheets have a longer way to go to get to minimum necessary functionality, but not everyone uses them.

The 35 year old can make requirements. The 45 year old can see how to break down the business requirements into work flow that makes sense. The 45 year old can look at requirements and immediately point out exactly what won't work and why.