Technology Commentary

But, in the non-ideal world we live in, most programmers need to know at least some SQL. On account of businesses insisting we stick most of

A website made with Typedream.

Wasm follows Java's the same broad principle of allowing developers to run the same code on any device, but at the same time Wasm fixes the fundamental issues that prevented the original vision of “Java on any device” from becoming reality.

DevOps and SRE Language: Discover the key differences between industry terms such as Postmortem vs Retrospective, RCA vs CFA, Disaster vs Incident

Download this SRE’s Golden Signals ebook and learn about four key metrics used to monitor the health of your service and underlying systems. You know about Latency, Traffic, Errors and Saturation - but what's next? In this eBook we explore SLO's, SLI's for a complete picture of reliability.

As organizations build up their own reliability practices, a good definition of reliability itself is the one that leads them to impactful priorities and consistent results.

THIS IS THE "EMBRACE" PART

David explains how “OpenAI” is just another example of Silicon Valley’s loophole arbitrage.

You’ve heard about the significant benefits that internal developer portals offer. IDPs can help your engineering teams increase velocity and

First post in a multi-part series on writing an operating system using components of other systems, such as MINIX. This post describes a small bootloader in detail and steps through debugging it on bare metal (QEMU). The sample code is hosted here.

Players: 1 or more Goal: Score the most points over 10 rounds Summary: Each round represents a year, and each die in a player's dice pool represents some some software capability that either generates annual recurring revenue, or a support...

The Web being full of “how to …” type of articles, I’ll start this one from the presumption that “what works for me, might not for you”…

I’m developing the Secret of Darkwoods an open-world procedural illustrated text-based RPG that allows players to interact with random…

Opensustain.tech has recently published a study providing the first analysis of the health and vibrancy of open source software in sustainability and climate technology.

Blue Badge Insights CEO Andrew Brust reaches deep into his rolodex to assemble a panel of experts to predict what 2023 will bring for data, analytics and AI.

New blockchains are springing up like mushrooms. So in the crypto field, you have to be careful because it’s easy to get scammed. But in this post, I’ll share some thoughts on a blockchain that, in my opinion, has some prospects and potential future.

We spent the last couple of months thinking that bringing HEYhome from the cloud was going to involve SUSE Rancher and Harvester. A combination of enterprisey software products that would give us a cloud-like experience on our own hardware, and require minimal changes to how HEY is already packaged and deployed. But we should have smel...

An essay on the impact of commodity software on Microsoft

I am always looking for ways to help teams fight the good fight when it comes to cultural change across API operations. The technology of APIs takes a lot of work, but it never requires as much work as the business and people side of API operations. Gathering stories from across the conversation I am having, sharing them here on the blog, and via the Postman blog is how I look to scale my advice and guidance for shifting enterprise behavior. Today I wanted to aggregate a handful of stories about outages and breaches, and explore what we can do to contribute to behavioral change across teams and amongst leadership after any type of API incident.

If you tune into my storytelling, you’ll hear me say this a lot—-APIs are hard to see. Any API, but more importantly, legacy APIs are just really hard to see. As a result, it is very difficult to quantify the technical debt that is accumulating across the enterprise. None of the enterprises I talk to know where all of their APIs are, and the older the API is, the higher the chance the API doesn’t have up-to–date documentation, artifacts, and other things that help us see the surface area of an API, let alone understand its state. While I am a big proponent of documentation of all APIs, I am also a big fan of investing the time to document legacy APIs to help better articulate the technical debt that exists across operations across teams and with leadership.

It takes A LOT of energy to get to the top, and even more energy to stay there. Damocles, a courtier in the court of Dionysius II in the Kingdom of

Three bills investing hundreds of billions into technological development could change the way we think about government’s role in growing prosperity.

For our 200th episode, I'm going to explain exactly what went wrong in the Japanese software industry.  I'll lay out the whole story, and also pinpoint the specific moment Japan lost its way. And by the end you'll also understand why everything might be about to change.  You see, the story of Japanese software is not really the story of software. It's the story of Japanese innovation itself.