3 files changed, 34 insertions, 0 deletions
diff --git a/blog/TLDR-rust-2020-09-19.markdown b/blog/TLDR-rust-2020-09-19.markdown
index 511f62d..ac0b1e5 100644
--- a/blog/TLDR-rust-2020-09-19.markdown
+++ b/blog/TLDR-rust-2020-09-19.markdown
@@ -1,6 +1,7 @@
 ---
 title: "TL;DR Rust"
 date: 2020-09-19
+series: rust-for-gophers
 tags:
   - rust
   - go
diff --git a/blog/rust-crates-go-stdlib-2020-09-27.markdown b/blog/rust-crates-go-stdlib-2020-09-27.markdown
index ac6f98e..a80bbb5 100644
--- a/blog/rust-crates-go-stdlib-2020-09-27.markdown
+++ b/blog/rust-crates-go-stdlib-2020-09-27.markdown
@@ -1,6 +1,7 @@
 ---
 title: Rust Crates that do What the Go Standard library Does
 date: 2020-09-27
+series: rust-for-gophers
 tags:
  - rust
 ---
diff --git a/blog/time-regex-testing-2020-10-04.markdown b/blog/time-regex-testing-2020-10-04.markdown
new file mode 100644
index 0000000..d24c1f2
--- /dev/null
+++ b/blog/time-regex-testing-2020-10-04.markdown
@@ -0,0 +1,32 @@
+---
+title: Time, Regexes and Testing
+date: 2020-10-04
+series: rust-for-gophers
+tags:
+ - rust
+---
+
+# Time, Regexes and Testing
+
+Previously on [Rust for Gophers](/blog/series/rust-for-gophers) (name is a work
+in progress, ideas would be lovely) we covered logging, templating and basic
+HTTP client/server operations. Go's standard library also has support from some
+other things too, such as time handling, regular expressions and unit testing.
+Today we are going to cover their analogs in Rust.
+
+## Testing
+
+Programs have a tendency to not do what you want when you write them. Sometimes
+it's worth trying to see what code actually does and make sure it's what you
+want it to do. This can help a lot when you are ensuring that types are
+converted, the right HTTP responses are returned and that any other effects are
+what you want.
+
+[We plan to go into much more detail about this in the future, however this is
+just enough about how testing in Rust works to help show these
+examples.](conversation://Mara/hacker)
+
+## Time
+
+## Regexes
+