@shawnthroop Networking isn't too bad when it has been abstracted away enough that you can treat it as event-driven code. The truly frightening code for me is multi-threaded. I can think sequential. I can think events. But threads make my brain melt.
@shawnthroop There is one remaining bug that I haven't tracked down which is a memory leak. For some reason, deleting the packet data structure on the last stage of a handover was causing everything to crash. So I commented out the line for now...
@shawnthroop This implementation is all C. And I usually use Emacs as my editor. But it really doesn't matter which one. It isn't any more complicated than iOS code. In a lot of ways it is simpler because all the special cases are enumerated in the docs.
@shawnthroop It sounds a lot more glamorous when you aren't looking at complicated spaghetti C code you didn't write and trying to figure out where the actual bug is hidden among the memory leaks... :)
@shawnthroop In this case, the EPC is 'Evolved Packet Core', which is the backhaul protocol behind '4g LTE' systems. We've got some base stations hooked up via coax cable to some phones with an EPC to make a whole mini cell network as part of our testbed.
@shawnthroop Playing with a 3d printer, trying to track the blade in a horizontal bandsaw, squaring a CNC router, tracking down a race condition in a flawed implementation of the EPC protocol, and unbitrotting a python script. The Ale sounds more restful.