The power of JAMstack and value-based development

Recently, I was introduced to the JAMStack. It changed my world. Rather than relying on developers to build a site, maintain it, deploy it, configure it, and monitor it. JAMStack development allows a developer to focus on content.

Today I decided to build this blog on the JAMstack to see if it was all I thought it could be.

The Jamstack

What is JAMStack? Simply, it is a site that doesn't depend on a server. Wait, what? No server? Right! build the content, push it to the edge of the web or a CDN. Make it fast to download, but no server.

Oh, and when I say "Push" to the edge of the web, that is nothing more than a "Push to your git repository. It does the rest. All of it.

[Pause for effect]

Building a blog

In my journey, I've come across a lot of partial truths, examples that almost worked, and tutorials that were difficult to adapt to my specific circumstances.

Partial truths, they are plentiful in all aspects of life. Just Google "how to lose weight". Or "who should I vote for?" Either way, you get a variety of examples.

So rather than rely on opinion, lets focus on data and facts.

It took me 60 minutes to get this site up and running. And about 45 of that was figuring out how to switch DNS servers from AWS to netlify and waiting for netlify to recognize they had been switched. 10 minutes was working on the code.

Now I'm just writing my blog.

Investment 1 hour.

And I have a blog environment. Oh, and I have a testbed where I can try out Vue techniques.

Seems reasonable.

What is value based development?

Have you ever been asked to build something with code, then spent time building it, have it ready deployed it, but no one used it? Or it had no business effect, even though everyone "thought" it would.

What if instead, we focused on building value, that was measurable. Then we measure it, adjust course and try it again.

I've had the privledge of building products people use. There have been mistakes on "Important features"