Technical debt is more than the cost of not adopting a new technology. Dr. Rachel Traylor points out that it can also be the cost of hastily adopting a new technology without considering how it will fit into your bigger strategy.
Merriam-Webster recently posted about the origins of the term “premises” that shows the word meaning IT folks so adamantly defend was created by an accepted understanding. The word came from the legal usage of the word “premise”, referring to prior parts of a contact that dealt with property specifics. Over time, this became accepted short hand for the property and location itself.
In this episode, the roundtable discusses the idea of technical debt. They look into why technical debt occurs, why it isn’t always a bad thing, and how to possibly optimize for when to incur it.
It’s no secret that network analytics is quickly becoming the […]
Preston de Guise recently wrote a thoughtful piece about what death means for digital identities. It reminded me of the struggle I had when my son came into the world, and the fact that our digital representations are now generational. This means that before and after we have agency we must deal with our digital selves.
In a recent post, Bob Plankers asserts that software is always broken. While the process of releasing software is often a chaotic one, is it accurate to say it is broken? If that is the case, what are the conditions by which it can be made whole?
Coinhive has been in the news recently, being used by The Pirate Bay and Showtime. The company provides a JavaScript crytocurrency miner that uses the idle CPU of anyone visiting a given web page. Can this provide an ad free path to monetization?
Maxta has offered a software-centric approach to hyperconverged infrastructure for a while. The company now support easy migrations in Red Hat to KVM, giving organizations more choice on how best to implement HCI for their needs.
On this episode, we’ll be talking about a hot topic in the networking space, automation. The panel discusses why organizations see automation as prohibitively complex, what exactly they mean by automation, and why it isn’t coming for their jobs.
Sometimes a company’s code name for projects in development can give you some insight into how they view it. The one that always stick in my mind is “Revolution”, Nintendo’s code name for what ultimately became the Wii. It showed how different the console was than anything in the company’s past, and reflected the impact Nintendo expected of it.
In the same way, Cisco’s Project Starship has now been launched as Intersight. The name loses some geek factor, but is probably much better for IP. Much like the codename implies, this is a project that is clearly linked to how Cisco sees the future of their business. Cisco has been working on this for a while, and it’s a natural extension of their Unified Computing Systems that they’ve had for almost a decade.
