wires

summary refs log tree commit diff
path: root/content
diff options
context:
space:
mode:
Diffstat (limited to 'content')
-rw-r--r--content/_index.md4
-rw-r--r--content/zosimos/workflow.md10
2 files changed, 7 insertions, 7 deletions
diff --git a/content/_index.md b/content/_index.md
index 0576859..e73a990 100644
--- a/content/_index.md
+++ b/content/_index.md
@@ -6,7 +6,5 @@ languages, and distributed systems. My favorite languages to work with are Zig,
 Rust, Erlang, and the venerable C. I want to build high performance and fault
 tolerant systems, and to help make the web a more free and decentralized place.
 
-<p style="text-align: left;">
 I'm currently looking for work. If you want to talk, you can reach me at
-<a href="mailto:wires@wires.systems"><code>wires@wires.systems</code></a>.
-</p>
+[`wires@wires.systems`](mailto:wires@wires.systems).
diff --git a/content/zosimos/workflow.md b/content/zosimos/workflow.md
index 114426f..24b2378 100644
--- a/content/zosimos/workflow.md
+++ b/content/zosimos/workflow.md
@@ -8,7 +8,7 @@ Programming my own OS has been a dream of mine for years, but my attempts always
 end up going the same way: writing some code that can run in a virtual machine,
 learning some interesting stuff about x86_64, and then giving up before I even
 reach userspace. Now I find myself called again by the siren song, but I'm
-determined to not go down the same road again ... so I'm doing it on an arm
+determined to not go down the same road again... so I'm doing it on an arm
 machine this time. I ended up settling on the Raspberry Pi 4B, since the price
 was reasonable and the large community makes it easy to find answers to any
 question I might have. But before I can set out to build the greatest OS ever,
@@ -25,9 +25,10 @@ itself, and while nothing in this post is particularly difficult, I have reason
 to believe it'll keep up even as the complexity increases.
 
 I won't go into detail about the actual code since 1\. it's extremely trivial
-and 2\. it's not the main focus of this post. All that matters is that it
-consists of some Zig code, an assembly stub, and a linker script to put it all
-together. In our `build.zig` file we therefore write:
+and 2\. it's not the main focus of this post, but you can find it [here][code].
+All that matters is that it consists of some Zig code, an assembly stub, and
+a linker script to put it all together. In our `build.zig` file we therefore
+write:
 
 ```zig
 const std = @import("std");
@@ -86,6 +87,7 @@ files ourselves, but we can do better!
     want a different filename.
 
 [1]: https://git.wires.systems/wires/zosimos/src/commit/8466e9b4d2fbca85d53d8dadc87914b4766c43de/src
+[code]: https://git.wires.systems/wires/zosimos/src/commit/b6b96f651f060ae6cff9e4e184799bb354ce6d07
 [7]: https://www.raspberrypi.com/documentation/computers/config_txt.html
 
 ## Fetching Firmware