Beyond Network Neutrality, and TATT

Net neutrality is repealed, and while the long battle over it seems over, there’s still some hope for it.

There’s been folly in conversations related to Network Neutrality and Over The Top Services (OTT). It limits the conversation to be about who owns the infrastructure and who uses the infrastructure – which is a good place to start, but is at least a decade outdated. Even the global conversation has fallen behind reality; the wheels of bureaucracy turn much slower than technology and technology use evolves.

We live in a world where the infrastructure, while important, isn’t the only thing that can be used to be unfair. Amazon and Google are presently in a content war with each other; the latest blow being Alexa being unable to pay YouTube videos. In an age of ‘IoT’, or ‘Internet of Things’, devices unable to use services isn’t being determined by who owns the infrastructure – it’s about who owns the services as well.

Right now, getting information from the browser you’re reading this in will tell what sort of browser you’re using, what operating system and what version – amongst other things. It doesn’t say anything about you, personally – Luddites, come back! But anyone with a website or a service can see what sort of software you’re using to connect to them – just so that they know how to change the content, if necessary. They can also tell where you are with a level of knowledge that can be a bit disconcerting – where your computer, phone or tablet – or internet enabled refrigerator, for that matter – is communicating from.

And they can decide what you can see and what you can’t. I’m sure I’m not the only one who has found YouTube videos that I couldn’t watch because, ‘content is unavailable in your country’. Here I am, an Amazon Prime user, and I can’t watch certain content because… ‘content is unavailable in your country’. There are reasons for the latter – I think they are bad reasons, but there are reasons related to broadcast rights. And yet, it shows that infrastructure isn’t the only thing that can be used to make services incompatible.

This is nothing new. The Browser Wars were the first real issue – and if you ask a web developer of worth, they will tell you that they persist, even when only a Cold War. When an app only works on Android or Apple device, it’s the same thing. Which brings up what can go into the Apple Store or the Google Store – and how it’s approved and whether they can pull it or simply decide that they don’t want to carry it because it competes with their own service.  

This is the larger conversation that is being missed by just about everyone. When Network Neutrality conversations first started, this issue hadn’t evolved – and despite it’s name, the overall concept has been specialized when, in fact, it should be generalized.

When it comes to the hardware and infrastructure alone, the Carterfone laid the groundwork in the United States that ISPs like Digicel are against: that devices could be connected to infrastructure owned by a corporation as long as they did not damage the infrastructure. Moving that forward, the same should apply to services. It’s that simple, but the waters are muddied based on the misconception that it’s their network. From a legal standing, this may be true – but from a business perspective, it’s not as true: Without customers, the network has no value, and therefore the customers also have control of the network – assuming that there is competition, and assuming that the ISPs will not coordinate to assure that Law makes it possible for all ISPs to throttle communications as they see fit. Bad assumptions, really, if we take a look around just about anywhere in the world.

And on top of all of that, we have the lack of network neutrality in services being provided across these same networks.

TATT needs to step back and understand the underlying philosophy and not get drawn into the weeds. Does TATT stand for corporations, or does TATT stand for the citizens of Trinidad and Tobago?

That answer will dictate their policy. I expect that they’ll tell us soon enough.

Understanding Frankensystems

Solar systemWhen I was just a software engineer in the eyes of managers, I usually got tossed into undocumented complex systems that nobody could figure out easily, largely because they were… undocumented. What overwhelmed and/or intimidated others was exciting for me – exploring something new, understanding how it worked. I’d developed a toolset for exactly that, finding and fixing memory leaks in things I’d never touched before, finding the circumstances that created specific bugs – but the real joy for me was in understanding systems. This transcended computing systems, but here I’ll write about computing systems.

My motto, adapted from something my paternal grandfather would mutter now and then, was, ‘Man made you, man will solve you.‘ I also tried to teach this to others. I recall telling one young intern, just spreading her wings on a GIS system, that I knew that she was smarter than the code she was looking at. I was right, she was – brilliant young woman handpicked from UCF – but she was one of the few; too often I said it and was wrong, probably inadvertently destroying someone’s confidence in what they did for a living. That was probably for the better, I hope – if you can’t hack it, you can’t hack it and you need to find something else to do that better suits you.

Not everyone can think on a systems level. There’s no shame in that. Not everyone can put the puzzle pieces together, even with well written documentation. Not everyone can eat elephants, particularly when they are afraid to get close to one. There’s a few of us that can. And it gets down to details, the moving parts of systems, understanding the principles of operation, understanding what and why things were done that way. It’s forensics, it’s imagination, and it’s also being able to understand the developers who wrote the code and their different styles or lack thereof.

When it comes to multiple software packages working together, the intrinsics of each interacting system are more important than people who create silos think; the more complex the system, the more personality it has for lack of a better word. Some software is plain grumpy, some is pretty and shallow, a reflection of the development cycle. If you’ve been around long enough, you can see something that was pushed out into production too early and abused over the years – scars of undocumented patches cover the code, each done differently as maintainers came and went, their lack of time afforded shown in how deep the scars run in the code. Frankensystems, held together by scar tissue. Let the healing begin.

Almost every time, this requires talking to people who have been around long enough and listening not just about the requirements of the system, and how things evolved from their perspective, but also understanding the developers involved. The brilliant developer who wrote undocumented code that never made sense to anyone else, who snuck things in when they could without others knowing. The plodder, who took their time and was always behind schedule. So many personalities, and all of that feeds into the Frankensystem in ways that defy management silos. How many times did I get in trouble with managers for talking to people outside of the development area to understand the system? Too many. I have references. But I always delivered, which probably boggled them.

There’s more to these systems than code, and the more complex the systems involved, the greater the interactions, the more one needs to see it from different angles. The metaphor of eating an elephant is scalar, from only one perspective, but to truly get into a system you need to eat that elephant from as many directions as you can.

Knowing only the code of a Frankensystem is failure. Sure, there will be landmarks, sprints, whatever – but those ‘successes’ are just small things created by people who just want their pain to go away and have been sold on the idea that these systems are solved that way. If you truly want to understand the systems, you have to mine all the data – from social engineering to code, from network diagnostics to documentation, and what is lacking you have to create.

The power of understanding is in the interactions, the intersections, and cannot be taught.

Linux Journal Ends.

existenceWhen I got the news that Linux Journal has ceased publication, I had to take a moment. I’d been published through them a few times in the early naughts, had worked for the parent company at and, had met some of the coworkers over the distances and had hung out at Phil Hughes, the former publisher, in Estelli where I broke his carafe and had to get a new one… before I could speak Spanish well enough to know that carafe in Spanish is carafe.

2005 was a pretty good year for me, transformative in many ways. It was great to work with so many people rowing in the same direction; that I went off in my own direction again as I have done over the years speaks more to my own life. SSC is good people, and were the right team for a time for me.

It wasn’t that I expected Linux Journal to last forever. I’d visit the site now and again, but my own path had lead me into Drupal, back into C++, back into VB, into corporate .Net – or better, ugly stabs at using .Net for things that Linux would have been better at. Bills are bills. The down-turned economy (thank you, banks) had me doing things I didn’t like doing, where work was work to do.

I know people that I knew there had since moved on. My Costa Rican connection had gone on to Wisconsin, my Panamanian friends are half in Florida and half in parts unknown, last making biodiesel. It’s easy to wax nostalgic about there and then.

That’s the trouble with the digital age. Things change faster, and we have to change faster than them to stay afloat – and I know that LJ was trying to do just that while I was there (some of the stuff I worked on and advised the publisher on) just as we all do in our lives. And sometimes entropy catches up with us.

But there’s a glimmer of hope in there. Maybe they’ll find a way. It’s hard to say what will happen, but you don’t announce your own demise lightly.

Either way, it is the end of an era. It’s also the beginning of a new one, whatever it may be. That’s just writing and publishing in a digital age.