From 8358c0765be412b1616aa978667f5d582e9e4901 Mon Sep 17 00:00:00 2001 From: a73x Date: Sun, 1 Dec 2024 13:27:00 +0000 Subject: feat(css): centered content --- public/posts/2024-08-25-01.html | 53 ++++++++++++++++++++++------------------- public/posts/2024-08-25-02.html | 53 ++++++++++++++++++++++------------------- public/posts/2024-08-25-03.html | 53 ++++++++++++++++++++++------------------- public/posts/2024-08-26-01.html | 53 ++++++++++++++++++++++------------------- public/posts/2024-08-31-01.html | 53 ++++++++++++++++++++++------------------- public/posts/2024-09-04-01.html | 53 ++++++++++++++++++++++------------------- public/posts/2024-09-08-01.html | 53 ++++++++++++++++++++++------------------- public/posts/2024-11-09-01.html | 53 ++++++++++++++++++++++------------------- 8 files changed, 224 insertions(+), 200 deletions(-) (limited to 'public/posts') diff --git a/public/posts/2024-08-25-01.html b/public/posts/2024-08-25-01.html index 4bd4371..91f5a84 100644 --- a/public/posts/2024-08-25-01.html +++ b/public/posts/2024-08-25-01.html @@ -14,26 +14,27 @@ -

a73x

- _{high effort, low reward} - - +

a73x

+ _{high effort, low reward} + +

Go Benchmarking

diff --git a/public/posts/2024-08-25-02.html b/public/posts/2024-08-25-02.html index 81e8f77..541697b 100644 --- a/public/posts/2024-08-25-02.html +++ b/public/posts/2024-08-25-02.html @@ -14,26 +14,27 @@ -

a73x

- _{high effort, low reward} - - +

a73x

+ _{high effort, low reward} + +

Go Project Layouts

Do you lay awake at night and consider how to optimally layout your Go project? No…? what about recommending Windows to a friend or colleague?? @@ -142,11 +143,13 @@ I can’t be bothered rewriting my example, so here’s a random one I f

My vague summary is that clean code gives you a north star to follow, an idea of how you want to separate and reason about the packages you create. You don’t need to create the entities of abstraction that are also presented. Think about what things do or relate to and create packages for them. You should allow your project to grow organically but don’t expect architecture to appear without following a north star.

- + +

diff --git a/public/posts/2024-08-25-03.html b/public/posts/2024-08-25-03.html index 07e48a0..d3fa17c 100644 --- a/public/posts/2024-08-25-03.html +++ b/public/posts/2024-08-25-03.html @@ -14,26 +14,27 @@ -

a73x

- _{high effort, low reward} - - +

a73x

+ _{high effort, low reward} + +

Levels of Optimisation

@@ -67,11 +68,13 @@ Also, if you have long-running calls that are chained together, a 30-second snap It’s also just lowkey fun to look at the exposed data and understand what your system is doing.

- + +

diff --git a/public/posts/2024-08-26-01.html b/public/posts/2024-08-26-01.html index acf51a6..547e86c 100644 --- a/public/posts/2024-08-26-01.html +++ b/public/posts/2024-08-26-01.html @@ -14,26 +14,27 @@ -

a73x

- _{high effort, low reward} - - +

a73x

+ _{high effort, low reward} + +

Writing HTTP Handlers

I’m sharing how I write handlers in Go.

@@ -269,11 +270,13 @@ The handler functions accept a context param and their expected str

You can extend this to all the other request types. If you have query or path parameters, you could either pass in the request, write a custom struct tag parser, or find someone else who has already done it: https://github.com/gorilla/schema.

- + +

diff --git a/public/posts/2024-08-31-01.html b/public/posts/2024-08-31-01.html index 68d8563..955c4d0 100644 --- a/public/posts/2024-08-31-01.html +++ b/public/posts/2024-08-31-01.html @@ -14,26 +14,27 @@ -

a73x

- _{high effort, low reward} - - +

a73x

+ _{high effort, low reward} + +

Go's unique pkg

https://pkg.go.dev/unique

@@ -85,11 +86,13 @@ - + +

diff --git a/public/posts/2024-09-04-01.html b/public/posts/2024-09-04-01.html index 2e1abae..248ec34 100644 --- a/public/posts/2024-09-04-01.html +++ b/public/posts/2024-09-04-01.html @@ -14,26 +14,27 @@ -

a73x

- _{high effort, low reward} - - +

a73x

+ _{high effort, low reward} + +

Kubernetes Intro

@@ -154,11 +155,13 @@ You’re welcome.

The typical workflow involves a user creating a PersistentVolumeClaim to request storage. The CSI controller picks up this request and, based on the associated Storage Class, dynamically provisions a PersistentVolume that meets the user’s specifications. This PersistentVolume is then bound to the PersistentVolumeClaim, making the storage available to the Pod that needs it.

- + +

diff --git a/public/posts/2024-09-08-01.html b/public/posts/2024-09-08-01.html index 72cde61..ade7fdf 100644 --- a/public/posts/2024-09-08-01.html +++ b/public/posts/2024-09-08-01.html @@ -14,26 +14,27 @@ -

a73x

- _{high effort, low reward} - - +

a73x

+ _{high effort, low reward} + +

Building a Static Site with Hugo and Docker

diff --git a/public/posts/2024-11-09-01.html b/public/posts/2024-11-09-01.html index e825118..a79f7e4 100644 --- a/public/posts/2024-11-09-01.html +++ b/public/posts/2024-11-09-01.html @@ -14,26 +14,27 @@ -

a73x

- _{high effort, low reward} - - +

a73x

+ _{high effort, low reward} + +

Refactoring

@@ -75,11 +76,13 @@

Refactoring done right is a powerful way to keep your codebase healthy. It reduces complexity, mitigates technical debt, and prepares your code for future change. It may not be glamorous, but it’s one of the most impactful ways to ensure that your codebase is something you—and others—can work with for the long haul.

- + +

-- cgit v1.2.3