Knowing of mortality; my daughter was murdered, my father died to cancer and my wife was recently diagnosed with cancer. The thought that comes to mind - and as a geek you might see it: What was done on Terminator. Record everything you can. Show her that - you were there for her as much as you can. There was a movie -- I watched as a child where a lady found out that had cancer, and wasn't going to live. She made tape recordings for her daughter (I wish I could remember the name)

You might also consider gifts and/or recordings for her -- example 16th birthday, 18th birthday, graduation and so on. Start now, learn to become comfortable with your recordings. The recordings might be video, audio both ... what you feel comfortable with. What little I have of my father are songs that he had song to my mother, and very little of photographs.

As you make the recordings -- I believe that you will think more in terms of what legacy you can provide her. Telling her that she seems to have the same geek that you have, that you were hoping to guild her when she got older. Tell her about going out and getting her that gift for her 16th birthday, how hard it is for you now, and wishing that you were there with her. Much good advise is here on /.

... and management failed to implement policies and practices in place to prevent development from having direct access to production DB's (without oversight). (It did appear that backups were maintained)

Even some thing as simple as "database cleanup" can be a problem when not properly tested. In once instance I was testing a server/database migration/upgrade. In the Test Plan, I called out that permission issues could not be tested (security wouldn't allow it) and failure to test could result in data loss. As predicted - there was a problem that came to permissions that I was disallowed from testing -- that resulted in data loss (Self defense: I tested as best as I could around the known permission issue).

Some highlights:
o Worked for large co; found several "Sev 1" bugs on a product was was proposed to be released soon. I was put on inventorying computers; product became one of the larges failures in company's history due to -- bugs.
o Same co, later: needed to make a code drop to another business. My job: To make sure that the code worked as expected, and could compile. (they got a "special" version of the code.) I told the PM that we shouldn't have the code on a given storage server -- it (the code) could accidentally be "compiled" causing problems. PM said that would not happen. A few days later, someone compiled the coded on the storage server. PM required that I had to find a way to 'fix it'. At the same time I looked into 'who' compiled the code: The same PM. (This PM was also was responsible for a lawsuit that cost the company millions... and was promoted.) o Worked for a local utility. Was told that we were going to use a copy of "live customer data" for dev/testing. Objected, was told that "test" customer data could NEVER be visible to "real world". Two weeks into testing: Customer Service contact us -- customer billings were off. Sure enough: "test" was crossed over with "production". (My contract was suddenly "ended" shortly after I reported the security error - that was EXACTLY as I had predicted). About six months later, the state Attorney General was looking into the utility for using ... live customer data for testing.
o Worked for an aerospace co. Spend a week creating a detailed functional spec on a report needed by the business department. The developed report (delivered a month late) looked NOTHING like the spec. The totals didn't add up to anything, the columns were out of sequence, the colors were wild (not random -- just not anywhere near the spec.) Three days later, my contract suddenly ended.
o Worked for a company that managed big data. Found out that they had single point of failure ("fail-over"), and I had experience with fail-over situations. Was told that the data center could never be down for very long, and that this risk was minimal. About three months later, the data center suffered a catastrophic failure that took over a week to get minimal power restored. People involved with the failure were promoted.

So many, many, many more times: Like when development released product to production without consulting testing and caused customer data errors, like development removing all permissions on a SQL table to get their dev work done (when the permissions were re-applied, the code didn't work any more)

A good QA / Tester need to know all of the jobs: Development, PM, customer service and Testing to get the job done. Unfortunately QA never gets paid the level of knowledge that it has, the risk that it assumes, and - it's not unusual for bad management to (FREQUENTLY) have QA reporting to development; for bad management frequently blame the messenger. Interesting all the years that I've worked in QA -- I've never seen bad management get the blame.

At least this article admits to a level of "programmer error". However --- like most "computer error" news articles, this one misses a key point: This (like many others) is actually management error. Management failed to oversee programmers. Management failed implement test. Management failed.
I just wonder how much longer before software testing will get the respect it deserves.

The primary source has tidbits of info, however all of the links to 2nd sources are conferences (most are just now ending). Would like to see some meaningful info on this topic.

If you don't like it don't watch it.
If you really love TNG -- then start your own kickstarter. Please don't put down us that enjoy TOS -- when there is obviously enough to say that this is worth while.

for the fun of it... started looking at the first item. It is used to get/send data to other parties (usatoday) appears to be looking for news to display.

Suggestion: Take this info (including what /. won't let you display) and post it. Take some key items, with the original posting -- shake/stir and re-post.
I realize that some data is encrypted, but (as noted above) some is not.
I WOULD like to see this posted on /. -- with as much detail can be generated for the article.
Definite /. fail.. can't have list(s) of URL's in the posting.

Though this article does not have an "link" article, NetAlien -- using Wireshark has the means to view the data being shared. NetAlien does not indicate what that data was/is. Also - a list of what (exactly) URL's are being accessed (including the IP addresses) would be helpful form a complete article. All this info would be of interest for a complete posting here for consideration. Good start, needs a LOT more info before it is /. ready.