diff --git a/src/blog/posts/2024/5/learning-go-day-2.md b/src/blog/posts/2024/5/learning-go-day-2.md index a55c87c..5ea7393 100644 --- a/src/blog/posts/2024/5/learning-go-day-2.md +++ b/src/blog/posts/2024/5/learning-go-day-2.md @@ -1,5 +1,5 @@ --- -title: "Learning Go: Day Two" +title: "Learning Go Day Two: Code organisation" date: 2024-05-02T08:00:00.0Z tags: - learning diff --git a/src/blog/posts/2024/5/learning-go-day-3.md b/src/blog/posts/2024/5/learning-go-day-3.md index c6dda9d..19c0aa6 100644 --- a/src/blog/posts/2024/5/learning-go-day-3.md +++ b/src/blog/posts/2024/5/learning-go-day-3.md @@ -1,5 +1,5 @@ --- -title: "Learning Go: Day Three" +title: "Learning Go Day Three: Controls" date: 2024-05-03T08:00:00.0Z tags: - learning diff --git a/src/blog/posts/2024/5/learning-go-day-4.md b/src/blog/posts/2024/5/learning-go-day-4.md index c14d3bf..45b066d 100644 --- a/src/blog/posts/2024/5/learning-go-day-4.md +++ b/src/blog/posts/2024/5/learning-go-day-4.md @@ -1,5 +1,5 @@ --- -title: "Learning Go: Day Four" +title: "Learning Go Day Four: Data structures" date: 2024-05-04T08:00:00.0Z tags: - learning diff --git a/src/blog/posts/2024/5/learning-go-day-5.md b/src/blog/posts/2024/5/learning-go-day-5.md index 29028b8..f7845f8 100644 --- a/src/blog/posts/2024/5/learning-go-day-5.md +++ b/src/blog/posts/2024/5/learning-go-day-5.md @@ -1,5 +1,5 @@ --- -title: "Learning Go: Day Five" +title: "Learning Go Day Five: Tests" date: 2024-05-05T08:00:00.0Z tags: - learning diff --git a/src/blog/posts/2024/5/learning-go-day-6.md b/src/blog/posts/2024/5/learning-go-day-6.md new file mode 100644 index 0000000..ea82429 --- /dev/null +++ b/src/blog/posts/2024/5/learning-go-day-6.md @@ -0,0 +1,22 @@ +--- +title: "Learning Go Day Six: Picking a project" +date: 2024-05-06T08:00:00.0Z +tags: + - learning + - go +excerpt: "It's finally time to decide on what project I'm going to build this month" +--- + +Okay I'm only six days into learning a new language, and I've barely scratched the surface[^1]. But I learn best by actually _doing_ things, so I've decided what I'm going to build. + +I'm going to make a simple uptime dashboard for my blog, in the same vein as [broke.lol](https://broke.lol). It should: + +* Monitor my website(s) for downtime +* Give some up/downtime statistics +* Display the current status, especially if things are broken + +And that's more-or-less it. If I get done early, I might stretch it out to do more analytics, so counting visitors, referers etc. That's a stretch though, because I'd want to do it in a way that's privacy respecting and fully anonymous. + +The repository for this project will be on my personal Git server, and I'll update this post with the repo URL once it's been created. + +[^1]: Seriously, I flicked through the [Tour of Go](https://go.dev/tour) to see how much I was actually skipping and there was a surprising amount of stuff in there \ No newline at end of file