yep. Or, I could have easily taken the pic then backed up and changed my choice. But, my neighbor who wants me to come turn on her computer after the power goes out may not realize that there are alternatives to posting her actual ballot (either from lack of know-how or fear of being caught).

Think of the emails we've been seeing that employers have sent to their workers. I think many of those employers would love to see how everyone votes. If showing your ballot becomes the norm, I'd expect "someone" at the business to start throwing a "we voted" party with a slideshow of everyone's ballot. You may want to keep yours secret, but "everyone does it" so make sure to send your pic to the party organizer to prepare the slideshow. And if you don't care about employers seeing votes, maybe you care about unions, churches, schools, bar owners, or neighborhood thug. Best to not allow proof of votes if we care about keeping them secret.

But I used a one-click payment button so I had to take it down.

I work at a company with many brands and MANY customer-facing websites. Some sites/services can be updated in minutes with little hassle or approval. Some need weeks with much paperwork. It depends on the risk. The apps are built in different ways (CMS or from scratch or with many proven components). The apps have different features (some can result in $million fines if there's a problem).

The tools are there to set up processes where every time I commit, it goes to production. You need a process that matches the risk you are willing to take.

It looks like a bed and I'll take it about 8 hours into the future just like I do most nights.

My huge company with many brands has 100s of web sites. We have a few classifications of sites, and each classification has it's own process. In some cases (e.g. credit cards involved), it MUST be deployed & operated by a 3rd party vendor (different than the developer). In other cases, a single (approved) developer can do everything him/herself, as long as it's coordinated with the brand manager and corporate PR and has no features corporate privacy or security teams would object to and is hosted at an approved provider.

In some cases, a seemingly simple new facebook page needs LOTS of input from LOTS of groups, and needs to follow a pretty complex process of who does what. In other cases, it's a trivial task that can be done in a morning with emails between 3 people.

The key is to think up front about the different classifications. What are the legal/privacy/security/pr risks? In our case, risks not just for the brand, but all brands in the company. What can/can't be done in the different classifications? What processes need to be followed for each? What common components/services can be used/deployed without a security or privacy risk? After that, each site can be managed with the quickest and cheapest process? We would have 1/2 the sites and 1/4 of the facebook presence if every site had to follow the same processes (or we'd have lots of privacy, security, and operations issues).

  While credit card sites are operated differently, all sites and facebook pages are operated by the same 2 vendors with the same SLAs. We worked very closely with the operations companies to come up with the different deployment processes so that we can have both the quick/cheap and more complex types of sites with the same 24x7 SLAs. We also worked with our legal, privacy, security, and PR teams to make sure they are all satisfied that the processes are acceptable.

It depends on premises and goals in many cases. And, why do we seem so hung up on proving people wrong. Why not use the title "Proponents of Apollo Program Proven Right" and cover predictions that opponents got wrong in the body? Also predictions opponents got right and opponents got wrong (if any) should be covered?

We should take an objective look at both sides and use what they got right and remember what they got wrong to not repeat it. If this had a great stimulative effect and created jobs, maybe proponents can work with the poverty program proponents to create a program that both gets us further into space and helps with poverty. Getting both groups working together is more likely to advance both causes than trying to "prove" that one is wrong in order to advance the other.

I have worked place where a few people spent 50% of their time in the break room, at lunch, in the bathroom, on the phone, "talking to HR", or any other excuse to leave their desk. There seemed to be a correlation between who did/didn't do this and who didn't/did get good end of year evaluations. But it's still not good for day-to-day moral.

The only time I've seen tracking used was when a contractor was let go for spending OVER 80% of his hours on the phone. In a job that required no phone (i.e. he worked only with us in the office and nobody outside the office). It was a pretty easy talk for the manager since he had the detailed phone usage report.

My company has faced fines of 100s of thousands and even millions of dollars in fines and even a threat of a 5 year ban on internet presence in a country. We've also had a $50K project cost 20x as much because of a "minor" bad decision by a developer.

I'm 80-90 words per minute with 2 hands. I had really bad carpel tunnel problems in the 90s and got to where I could type about 60 words per minute with either hand on a one-handed dvorak keyboard. It took about 2 months of coding every day to get to my max.

I went about 5 years changing hands every 3-4 months. There are left and right handed dvorak layouts.

Will they at least tell the non-volunteers that their vehicle has been modified? I hope medical scientists don't pick up this new way of increasing the size of your test group.

But don't forget the chain of custody requirements for evidence to be used in court. You need to physically store it securely. Provide an audit-able method for prosecutors (and others) to access it if they need. Provide a way to get it to court with a full report of custody/access. Any evidence costs much more to keep than you and I keeping the same paper or electronic data. And that's a good thing.

My fortune 100 company spends many 100x as much per GB to store customer data (web PII) than I spend to store my personal data. And that's just the direct $/GB/month, it doesn't include the process we have on top to use the data. I've argued a few times that it's overkill, but it's one area that I'm ok with the lawyer's replies when we disagree.

Everyone learns different but for me it was best to pay attention to the class (professor and/or discussions). I'd write a few keywords for topics I need to pay extra attentions to - either I didn't feel I fully understood or thought the professor put greater importance in them. As long as the professor follows the book or hands out notes this works. I knew some people who wrote pages of notes that parroted the book and yet couldn't tell you what the last class was about because they paid attention to writing their notes rather than the subject.

A lot may have changed in classrooms over 25 years, but I still do the same in business meetings. I write more since I don't have a book to refer to, but I don't waste any time making sure my work doc is formated correctly and passes spell check (which other people do often in meetings.) and write down in pen/paper the key details I need to take from the meeting and who to contact if I need more info about anything or forget.

The 80's really sucked when I worked on a Unix kernel. We had unit tests, integration tests, system tests, stress tests, performance tests, compatibility tests (AT&T, BSD, SunOS, DB, major apps, Orange Book/security tests, various CPUs & devices, with builds from both a commercial and gnu compilers), and others.

In addition to working on the kernel, I managed our testing. I had to manually start the tests each morning (after the automatic nightly builds that took 10 hours). Then I had to manually start emacs toward the end of the day and load the result files (which were fortunately analyzed in lisp) rather than looking at a desktop widget, then manually send an email to anyone who caused a problem.

And to make matters worse (as if it can get worse than 10-20 minutes of my time a day) I didn't have lots of people raving about my cool test setup (they all thought it was just a standard and trivial part of software development)

And don't make me go off on the pain of alpha and beta tests. I had to email an ftp location to our major customers using !-notation.

Cities, states, and countries are constantly competing to be the government to vouch for a business entity's credentials (i.e. incorporation services) or to provide other government services for a business (e.g. water, sewage, roads, police, courts to settle disputes).

For these services, sometimes the government wants direct taxes. Other times they are primarily concerned with jobs. These jobs provide residents with money to pay other types taxes (individual income, sales, gas, property, etc) as well as helping other businesses (e.g. restaurants, stores) and decreasing the need for public services (i.e. food stamps).

Sometimes there is corruption in the process. More often than not, the government has decided that having the business is an overall benefit. The government may be incompetent and make a poor decision that doesn't necessarily mean corruption is involved. In any case, you need to look at the total effect (direct + indirect taxes + services that increase + services that decrease) to see if it was a good deal.