For decades, computers have been growing in power at a meteoric pace, and the army of programmers writing software for them is now twenty-eight million strong. So why does it feel like the applications we use every day—not even the brand new, bleeding-edge stuff, just basic things we’ve had forever, like word processors and e-mail clients—are slower and clunkier than ever?
Google has always been the gateway to content visibility on the internet, making optimization for Google Search a golden rule in content creation. But today, Artificial Intelligence is changing the game, and it’s time for Google, and all of us, to sit up and take note.
IPFS, the InterPlanetary File System, might evoke grand images of cosmic networking, but its true significance lies in ignoring topological boundaries altogether and making them irrelevant. While the name might come off as grandiose, it emphasizes IPFS’s capability to create a global, decentralized network where data can be stored, accessed, and shared completely independently of considerations about physical location. The underlying technology becomes secondary, as content-addressable storage takes center stage in ensuring the sanctity and robustness of the system.
IPFS (InterPlanetary File System) is a decentralized, peer-to-peer protocol that redefines how we handle data on the internet, enabling us to break free from reliance upon tech giants like Google and Amazon for hosting our data. By adopting a content-addressed storage approach and eliminating the traditional server-client model, IPFS offers a more independent and resilient solution for storing, sharing, and accessing information online.
I run a dedicated node for the InterPlanetary FileSystem, and you should too.
You use all sorts of online services. I know, because you’re using one right now to read this post. You also very likely use third-party applications of some kind to enhance your experience of those services: a browser extension, an alternative to the official mobile app, an AI news bot you follow. To come to life, these applications need some means of interacting with their target service in particular ways.
Legacy projects are where development teams go to die.
Feature flags: your worst nightmare or a secret weapon? It’s funny how clients react when we first pitch them on feature flags. It’s like they’ve seen a monster, but soon, they’ll realize it’s just a friendly giant. Let’s unpack this.
To date, most enterprise systems targeted at specific industries have been designed as centralized systems, rather than those with open protocols and a federated model. Adopting a federated model for a systems architecture is typically deemed to have too much complexity and risk. This has, since the advent of computing, funneled organizations into buying proprietary software from controlled silos which do not afford flexibility and portability for their critical data, and which inherently ultimately undermines their autonomy. If an industry is particularly fertile ground for IT system innovation, they may see multiple competing vendors carving out kingdoms of clients; this is the current scenario of least harm, and usually the only options in front of a procurement officer tasked with buying software for their enterprise. How can you retain your autonomy as a business, and still exchange and interact with others in your industry network? The answer is: Federation.
I first tried the open source DJ software Mixxx in the early 2000s. At a time when most DJs were still spinning vinyl and the CDJ-1000 was the new hotness, I was an accidental PC pioneer.
Threat modeling, a proven process for identifying potential system vulnerabilities, often needs to receive more attention in strategic cybersecurity conversations. Given the rising cyber threats such as ransomware, the need for threat modeling is more pronounced than ever. By anticipating such threats, threat modeling paves the way to enhanced resilience.