Well, this is a tech blog.

A few open-source blueprints for interesting scenarios/questions that we've been looking at.

The goals are simple - each 'blueprint' must be the answer to a question; the context of the question should help someone, somewhere. Other than that, the site has no other great agenda. It's a space for authors to jot down thoughts that might want to refer to later, thoughts that might help others.
We do not claim that the blueprints offered here are the 'best' answer to a problem. Where possible, we will look at other alternatives/options and will present a comparison. (The 'best' option in a certain context will obviously depend on the priorities you would assign, so if you happen to differ in your view on the option to use, its fine.)
If you found something here that helped you in anyway, do drop us a line, that's all we ask (it is not mandatory that you have to).

Blueprints (tagged with #cloud-native)

Incus for local K8S development

Incus for local K8S development

@rsaravanan, 2025-03-31

Setting up a local Kubernetes cluster for cloud-native development

#cloud-native #linux #incus

Photo by David Ramírez on Unsplash

1 of 1 online as of date, 2 in progress.

Quote of the day

Steve Jobs, Wired (1996)

"To design something really well you have to get it. You have to really grok what it's all about. It takes a passionate commitment to thoroughly understand something - chew it up, not just quickly swallow it. Most people don't take the time to do that. Creativity is just connecting things. When you ask a creative person how they did something, they may feel a little guilty because they didn't really do it, they just saw something. It seemed obvious to them after a while. That's because they were able to connect experiences they've had and synthesise new things. And the reason they were able to do that was that they've had more experiences or have thought more about their experiences than other people have. Unfortunately, that's too rare a commodity. A lot of people in our industry haven't had very diverse experiences. They don't have enough dots to connect, and they end up with very linear solutions, without a broad perspective on the problem. The broader one's understanding of the human experience, the better designs we will have."