Minimise the tentacles on the OctopOSS. Keep it simple
Our most recent two posts, from yesterday and Friday, have talked about one stunningly simple idea that helps to overcome one of OSS’ biggest challenges – data quality. Those posts have stimulated quite a bit of dialogue and it seems there is some consensus about the cleverness of the idea. I don’t know if the […]
Last Friday’s blog discussed how I’ve just been blown away by the most elegant OSS innovation I’ve seen in decades. You can read more detail via the link, but the three major factors in this simple, elegant solution to data quality problems (probably OSS’ biggest kryptonite) are: Being able to make connections that break standard […]
Looking back, I now consider myself extremely lucky to have worked with an amazing product on the first OSS project I worked on (all the way back in 2000). And I say amazing because the underlying data models and core product architecture are still better than any other I’ve worked with in the two decades […]
We introduced the concept of The Trickle-down Effect last year, an effect that sees the most minor changes trickling down through an OSS stack, with much bigger consequences than expected. “The trickle-down effect can be insidious, turning a nice open COTS solution into a beast that needs constant attention to cope with the most minor […]
There’s a crowded room of OSS experts, a room filled with serious intellectual horsepower. You might be a virtu-OSS-o, but you surely know that there’s still so much to be learnt from those around you. You have the chance to unlock the experiences and insights of your esteemed colleagues. But how? The answer might seem […]
Let me warn you. The following sentence is going to make many OSS experts cringe, maybe even feel slightly disgusted, but take the time to read the remainder of the post and ponder how it fits within your specific OSS context/s. “Our OSS need to help people spend money!” Notice the word is “help” and […]
Many different user journeys flow through our OSS every day. These include external / customer journeys, internal / operator journeys and possibly even machines-to-machine or system journeys. Unfortunately, not all of these journeys are correctly completed through to resolution. The incomplete or unsatisfactory journeys could include inter-system fall-outs, customer complaints, service quality issues, and many […]
Last Friday, we spoke about all wanting to develop trusted OSS supplier / customer relationships but rarely finding them and a contrarian factor for why trust is so hard to achieve in OSS – complexity. Trust is the glue that allows OSS projects to happen. Not only that, it becomes a catch-22 with complexity. If […]
Every OSS supplier wants to achieve “trusted” status with their customers. Each supplier wants to be the source trusted to provide the best vision of the future for each customer. Similarly, each OSS customer wants a supplier they can trust and seek guidance from. I’m an independent consultant, so I have been lucky enough to […]
Yesterday’s post discussed using smart contracts and Network as a Service (NaaS) to give a network the properties that will allow it to self-heal. It mentioned a couple of key challenges, one being that there will always be physical activities such as cable cuts fixes, faulty equipment replacement, physical equipment expansion / contraction / lifecycle-management. […]
A couple of interesting concepts have the ability to fundamentally change the way networks and services are maintained. If they can be harnessed, we could replace the term “network assurance” with “network healing.” The first concept is SON, which has been formulated specifically with mobile radio networks in mind, but has the potential to extend […]
A recent presentation just reminded me of “The Zen of Python.” It’s a collection of 20 (19?) software principles, particularly as they relate to the Python programming language. Since OSS is software-defined, (almost) all of the principles (not sure about the “Dutch” one) relate to OSS in a programming sense, but perhaps in a broader […]
The problem with OSS is that there are too many problems. We don’t have to look too hard to find a problem that needs solving. An inter-related issue is that we’re (almost always) constrained by resources and aren’t able to solve every problem we find. I have a theory – As much as you are […]
“When you start out in your career, you have a blank canvas, so you can paint anywhere that you want because the shit ain’t been painted on yet. And then your second album comes out, and you paint a little more and you paint a little more. By the time you get to your seventh […]
“Chains of habit are too light to be felt until they are too heavy to be broken.” Warren Buffett (although he attributed it to an unknown author, perhaps originating with Samuel Johnson). What if I were to replace the word “habit” in the quote above with “OSS integration” or “OSS customisation” or “feature releases?” The […]
Data quality is one of the biggest challenges we face in OSS. A product could be technically perfect, but if the data being pumped into it is poor, then the user experience of the product will be awful – the OSS becomes unusable, and that in itself generates a data quality death spiral. This becomes […]
There’s a concept that’s building a buzz across all digital industries – you may’ve heard of it – it’s a little thing called DevOps. Someone (most probably a tester) decided to extend it and now you might even hear the #DevTestOps moniker being mentioned. In the ultimate of undeserved acknowledgements, I even get a reference […]
Have you ever worked on an OSS where a COTS (Commercial Off-The-Shelf) solution has been so heavily customised that implementing the product’s next version upgrade has become a massive challenge? The solution has become so entangled that if the product was upgraded, it would break the customisations and/or integrations that are dependent upon that product. […]
This is the sixth and final post in a series about the four styles of RPA (Robotic Process Automation) in OSS. Over the last few days, we’ve looked into the following styles of RPA used in OSS, their implementation approaches, pros / cons and the types of automation they’re best suited to: Automating repeatable tasks […]
This is the fourth in a series about the four styles of RPA (Robotic Process Automation) in OSS. The third style is Decision Support. I refer to this style as the parrot on the shoulder because the parrot (RPA) guides the operator through their daily activities. It isn’t true automation but it can provide one […]
