Does anyone know how much an operation like github cost to get off the ground before it was able to support itself (excluding founders time)?

If this is the intended meaning then I disagree. The problem is that the kind of code most of us write isn't pure implementations of algorithms backed by formal proofs. In that case the code is the documentation because it is an expression of a mathematical description of something.

The code most of us write is a hodgepodge of business logic, frontend code, and a bunch of glue to make it all work together. In the case of business logic context is highly important. Just looking at the code doesn't convey the whole story or the "why" this code does what it does. In this specific case comments are the difference between saying "we don't know why this works," and "according to BUG-#### we need to send the counterparty this field as a logon credential otherwise their system behavior is undefined."

HP also has their own implementation I believe

A caveat here as well is you also need to make sure your various clocks in the data center are synched. This is one of those common but overlooked scenarios which lead to hilarious discussions about latency when really there was just a clock synch problem. Additionally the fallacies of distributed computing come into play here (namely, transport cost is 0) so you need to take extra care when looking at measurements across different systems and machines. Even machines in the same data center. The pipe that you are communicating across could be oversubscribed for example.

Yes. But you get all those problems plus more, if you convert to local time first.

Logically it would seem that the company would provide counsel because at the time of the alleged incident you were conducting business for the company. This is all laymen speculation of course. Any lawyers around?

I agree. Anything that gets people interested in programming is good for the industry. Typically I try to steer people who are interested in trying out programming to scripting languages first. The benefit here is the learners get an expedient path to gratification. It's important that people experience the gratification that comes from building something before the ugly truth about how horribly complex these systems are sets in.

Caring about your job isn't solely the domain of engineers.

There are plenty of lazy engineers too.

Not saying that at all, and really not pleased about your interpretation as I was answering the posts question about why a subset of recruiters only search LinkedIn. The type of recruiter that only searches LinkedIn is probably doing the churn and not doing careful, considerate work.

I believe most professions have people who care deeply about the job they do and also have people who learn to churn.

Wouldn't the terms of service qualify? It explicitly gives Facebook permission to use your data.

Not for academic purposes they wouldn't, that doesn't really constitute informed consent. Most people don't read ToS and that is well known.

Wouldn't you be able to sue the business partner for that sort of behavior?

Muc cheaper to get the money back from the bank and let them sue him. It was their mistake and they have lawyers fur such things.

I believe a more formal definition of realtime is: When missing a deadline constitutes a system failure. Given this definition realtime systems are not bucketed in such a way that they invite a false dichotomy. For instance on one end of the spectrum you would have hard realtime systems (e.g. a pacemakers) where missing a deadline means death of the patient or serious financial loss. On the other end of the spectrum you would have soft realtime systems (e.g. facebook) where missing a deadline of say displaying a web page in under a second would constitute a system failure (revenue/engagement decrease), but still be valuable (people will put up with slow page loads, look at reddit).