Network design, architecture, thinking, working. Tech.
I’ve been working on making some predictions about 2012 and networking. I like to do this in the year of 2012 (not 2011 like everyone else) and I like to go further than anyone else and predict what WILL NOT be big in 2012.
I’ve been considering a small but vital problem in naming conventions in Networking. Namely, the use of underscores and hyphens in object names and devices. It’s a hot topic for argument when the time comes for corporate standards (and when Network Engineers have beverages in a public house). Now, I figure that there are three possible grammar options for making names – hyphens, underscore and CamelCase.
In which I look at CARP vs VRRP, the nature of open standards and closed source fibre optic connectors that you pay royalties on, but you probably don’t know about.
The thing about merchant silicon is how far it has penetrated the network vendors. In fact, it’s getting difficult switches that don’t have the same Network Processor inside as any other vendor. Networking hardware is looking like servers hardware – glue some chips and then market the heck out of your pretty colours.
Pondering on data ownership, and whether governements could legally steal data from offshore organisations
I’m responding to Brad Hedlund’s post “On optimizing traffic for network virtualization” where he seems to missed a key point. It’s about cost of ownership in terms of ability to troubleshoot.
I’m sitting on Santa’s knee, and telling him how good I’ve and been and what I would like for Christmas.
When you say it like that, it’s kind of creepy.
I was reading this research paper “European Research on Future Internet Design” and was struck by this diagram….
A reader wrote asking about whether share options are a good bet. Answer: Only if you think winning the lottery is realistically possible.
One of the problems of working with the PRINCE2 practitioners is that the people tend to get highly focussed on definitions in the Scope of Works. A Scope of Works defines what the deliverables the customer is to received.
The problem with a Scope of Works is that it is usually prepared before the work is started and/or fully understood. maybe you have a Gap Analysis, or a Consulting Reports or a Requirements Document to setup the initial engagement (every company has their own name of the same thing).
