Being an experienced network engineer, I can tell you that this graph is expected. TCP, by nature, uses all of the bandwidth it can due to its windowing mechanism. Since the FCC doesn't like carriers limiting people's use of applications like Bit Torrent, Youtube streaming, or the like, the pipe is naturally going to be full. There is nothing Comcast could do about it. Is it overloaded? Probably not. To show a "good" looking graph, you would have to have a pipe so large as to allow every communication to finish instantaneously, or very very quickly, thus not allowing TCP to expand to the full pipe in the time allotted. As you can see, the stream going out of Comcast is small-medium, because very few people probably host websites on the Comcast network. The transmissions are also reasonably small for requesting websites, and so, the transmissions complete quickly, thus allowing the graph to represent lower utilization. So, in the end, this is why Comcast is pro Internet prioritization, or QoS, really. To make something very clear, I am not affiliated with Comcast, so don't ask.

Agreed.

Of course. I'm mostly saying that teaching a robot to drive a car forward is different than teaching a car to drive, period. If the robot knows (via taught skill) how to drive, and similar to humans, how to react when given parameters don't work perfectly with planned decisions, I think it would be a lot more comprehensive.

I'm sorry for those of you that disagree, and I understand your side as I do applaud the many hours (assuming) of hard work it took to program this beast in to the functionality it has; but, why is this impressive? For the level of computations per second and the price of said computations available today, I feel like there should be a "general" programmatic sense about it. One should not have to program a car to park in parallel, but rather, do whatever it is asked to do. Some call this artificial intelligence, others call it autonomy, I call it the right way. Until things are done this right way, I'm sorry to say that I can't really be impressed. Tell a car, not programmatically, but rather verbally, to park in parallel, and it should do it using the best means it finds suitable. Whether it be to slide park, based on speed of the manoeuvre, or slowly park, based on precision, or perhaps a middle-ground low to medium speed slide park with real gravitational, physical, and real-world aspects taken in to account, it should be able to make the decision of how to do it, then do it, then un-do it just as easily.

Someone f*cked up somewhere, not your fault, tell the supervisors to hold off on the site. They fire you, oh well, find a better place to work. I think IT workers in general need to stand up to their supervisors. They need you or you wouldn't be there.

I think the real issue here is the lack of best practice by the IT people (and yes, I am an "IT person") to take the necessary steps and precautions to configure things the "right" way, or going with best practices. I understand that people have been turned down for budgets on upgrading items, but I also contribute this behavior to superior/supervisor misunderstanding. I think any wise IS/IT engineer should administer their systems to a point where they don't necessarily have to worry about day-to-day tasks. Many of these tasks can be resolved by looking in the root causes of issues instead of patching the issues or complaining about the issues without doing anything. Most issues are generally complicated more as they are patched by engineers to get immediate results. The more an engineer or supervisor can encourage less day to day tasks, the more successful and less busy the IT staff will be; therefore, allowing both more personnel training and less stress in the workplace. Information Technology, as an industry, is a very balanced field. You must be smart to be successful, and sometimes being smart involves getting off your a** and fixing the real problem. If you don't, it'll come back and bite you in the a** later on. TRUST ME. I understand that as an IT staff member you are asked to fix things when they break, be it in the middle of the week or night, but it's all part of the job.