Re: This is *NOT* how you do interfaces
Yep this will one of the very big problems of software systems in the future - there is a bunch of developers (developers! developers!) out there who do not know anything about how communication works.
I don't know how many examples I have seen: first they need to come up with their own protocol, or at least with their own version of a protocol. Then they will write some spaghetti code that works for a while - as long as bandwidth is not a problem. Then things get more complex, and at some point they start getting into problems with packet loss, bandwidth problems etc. Takes them a while to understand what the problem is (if they either get it at all), and then they will come up with often very weird solutions, which only will work by magic. In the best case, they will re-invent the wheel.
One of the examples, the company had a working product for years. Then suddenly, there was a real demand on the bandwidth. The first build of software could only cope with 5% of the traffic. They had some rather hectic months, but finally got it working. They proudly presented their solution to the rest of the company - it was a bit sliding window with size 2 (that was 20012, not 1953).