Skip to content

Commit 5091ca9

Browse files
wmedranowmedrano
committed
Fix typos
1 parent 930c5bf commit 5091ca9

11 files changed

Lines changed: 55 additions & 54 deletions

File tree

‎content/about.org‎

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,18 @@
44

55
I'm me.
66

7+
A software engineer at Google on the Fonts team, where I work on font
8+
infrastructure and rendering in Rust. Before that, I spent nearly a decade
9+
wrangling big data on Search Analytics. Outside of work, I maintain a few Rust
10+
audio crates and tinker with programming language implementations.
11+
712
** Professional Work
813

914
*** Fonts @ Google
1015

1116
November 2025 - Present
1217

13-
I'll be working on fonts. I'm a fonts guy now.
18+
I've been working on fonts. I'm a fonts guy now.
1419

1520
*** Gigantic Data, Huge @ Google
1621

@@ -48,6 +53,6 @@ performance.
4853
* Contact
4954

5055
#+ATTR_HTML: :style width:auto;
51-
| @@html:<img src="https://github.githubassets.com/assets/GitHub-Mark-ea2971cee799.png" style="width:16px; height:16px; vertical-align: middle;">@@ | [[https://github.com/wmedrano][wmedrano]] |
52-
| @@html:<img src="https://joinmastodon.org/logos/logo-purple.svg" style="width:16px; height:16px; vertical-align: middle;">@@ | [[https://fosstodon.org/@wmedrano][@wmedrano]] |
53-
| 📧 | will at wmedrano.dev |
56+
| @@html:<img src="https://github.githubassets.com/assets/GitHub-Mark-ea2971cee799.png" style="width:16px; height:16px; vertical-align: middle;">@@ | [[https://github.com/wmedrano][wmedrano]] |
57+
| @@html:<img src="https://joinmastodon.org/logos/logo-purple.svg" style="width:16px; height:16px; vertical-align: middle;">@@ | [[https://fosstodon.org/@wmedrano][@wmedrano]] |
58+
| 📧 | will at wmedrano.dev |

‎content/index.org‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,9 @@
77

88
[[file:post/2026/03/31/function-ptrs.org][Functional Dispatch]] @@html:<span class="post-date">2026-03-31</span>@@
99

10-
[[file:post/2026/02/21/lisp-3.org][Building a Lisp Interpreter (with Rust) Part 3]] @@html:<span class="post-date">2026-02-21</span>@@
10+
[[file:post/2026/02/21/lisp-3.org][Building a Lisp Interpreter (in Rust) Part 3]] @@html:<span class="post-date">2026-02-21</span>@@
1111

12-
[[file:post/2026/01/25/lisp-2.org][Building a Lisp Interpreter (with Rust) Part 2]] @@html:<span class="post-date">2026-01-25</span>@@
12+
[[file:post/2026/01/25/lisp-2.org][Building a Lisp Interpreter (in Rust) Part 2]] @@html:<span class="post-date">2026-01-25</span>@@
1313

1414

1515
* Archive
@@ -18,7 +18,7 @@
1818

1919
[[file:post/2026/03/31/function-ptrs.org][Functional Dispatch]] @@html:<span class="post-date">2026-03-31</span>@@
2020

21-
[[file:post/2024/12/18/new-years-resolution-evaluation-reading.org][New Years Resolution Evaluation - Reading]] @@html:<span class="post-date">2024-12-18</span>@@
21+
[[file:post/2024/12/18/new-years-resolution-evaluation-reading.org][New Year's Resolution Evaluation - Reading]] @@html:<span class="post-date">2024-12-18</span>@@
2222

2323
[[file:post/2024/08/22/zigging-out.org][Zigging Out]] @@html:<span class="post-date">2024-08-22</span>@@
2424

@@ -34,8 +34,8 @@
3434

3535
** Tutorials
3636

37-
[[file:post/2025/11/15/lisp-1.org][Building a Lisp Interpreter (with Rust) Part 1]] @@html:<span class="post-date">2025-11-15</span>@@
37+
[[file:post/2025/11/15/lisp-1.org][Building a Lisp Interpreter (in Rust) Part 1 - Parsing S-expressions]] @@html:<span class="post-date">2025-11-15</span>@@
3838

39-
[[file:post/2026/01/25/lisp-2.org][Building a Lisp Interpreter (with Rust) Part 2]] @@html:<span class="post-date">2026-01-25</span>@@
39+
[[file:post/2026/01/25/lisp-2.org][Building a Lisp Interpreter (in Rust) Part 2 - Eval, variables, and if]] @@html:<span class="post-date">2026-01-25</span>@@
4040

41-
[[file:post/2026/02/21/lisp-3.org][Building a Lisp Interpreter (with Rust) Part 3]] @@html:<span class="post-date">2026-02-21</span>@@
41+
[[file:post/2026/02/21/lisp-3.org][Building a Lisp Interpreter (in Rust) Part 3 - Lambdas and closures]] @@html:<span class="post-date">2026-02-21</span>@@

‎content/post/2024/05/13/github-gitlab.org‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,10 +5,10 @@
55
* Introduction
66

77
GitHub and GitLab are code hosting platforms. After using both, I prefer to keep
8-
my solo developments needs on GitHub due to GitHub's larger community and faster
8+
my solo development needs on GitHub due to GitHub's larger community and faster
99
page loads.
1010

11-
* Basics
11+
* Basics
1212

1313
Although GitLab also sells itself as a DevOps platform, both GitLab and GitHub
1414
essentially have the same functionality. This is especially true for a
@@ -32,7 +32,7 @@ that GitLab takes ~2.5s~ to display code, while GitHub does so in ~1.0s~.
3232
Really, speed is the make or break feature for my usage. The latency GitLab
3333
introduces is enough time for me to get distracted. This is especially
3434
bothersome for the moments where I’m locked in and highly productive. Although
35-
I’m very sensitive to latency, others may not mind.
35+
I’m very sensitive to latency, others may not mind.
3636

3737
** Community
3838

@@ -43,7 +43,7 @@ happen. It’s even better when someone contributes back a feature or two.
4343

4444
GitHub’s community eclipses GitLab. Anecdotally, I’ve noticed most projects I
4545
use tend to be on GitHub. In terms of contributions, GitHub projects seem to be
46-
more lively as well.
46+
more lively as well.
4747

4848
*** Library Engagement Caveats
4949

@@ -52,7 +52,7 @@ GitLab. Libraries tend to attract at least a few users so it may be worth it for
5252
me to experiment by developing some libraries on GitLab to get a better sense of
5353
engagement. Unfortunately, my main job eats a lot of my time and energy leaving
5454
very little for my side projects. Despite this, it does feel like the libraries
55-
I find on GitHub tend to have more contributors than the ones on GitLab.
55+
I find on GitHub tend to have more contributors than the ones on GitLab.
5656

5757
*** CI
5858

@@ -72,7 +72,7 @@ lack of reusable actions, GitLab does have better artifacts support. Artifacts
7272
are files that are produced by the CI. These can include anything like the
7373
binary build, intermediate data, or, very nicely formatted HTML reports. In
7474
GitLab, I enjoyed setting up several reports. My CI would build and test and
75-
produce several neat artifacts like
75+
produce several neat artifacts like
7676

7777
- Code coverage report highlighting all lines that executed during the tests,
7878
bringing attention to those that had no coverage.

‎content/post/2024/07/08/month-of-ai.org‎

Lines changed: 8 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -23,16 +23,14 @@ contest platform. I even skimmed the top placement’s creative
2323
solutions. It was fun and all, but it was mostly the end of my machine
2424
learning explorations.
2525

26-
Round 2: Over the years I didn’t use much machine learning. If
27-
anything, I’ve been looking on how to reduce technological
28-
distractions around me. When GitHub Copilot came out for technical
29-
preview around Mid 2021, I signed up immediately. My expectations were
30-
low, but I was impressed by the technology and curious to see how well
31-
it would do. As expected, I was impressed with GitHub Copilot’s
32-
technical achievement. As a tool though, I found the code generation
33-
somewhat distracting (expected), but it was great and generating
34-
docstrings on all my public ~structs~ and ~functions~, an unexpected
35-
surprise.
26+
Round 2: Over the years I didn’t use much machine learning. If anything, I’ve
27+
been looking on how to reduce technological distractions around me. When GitHub
28+
Copilot came out for technical preview around Mid 2021, I signed up
29+
immediately. My expectations were low, but I was impressed by the technology and
30+
curious to see how well it would do. As expected, I was impressed with GitHub
31+
Copilot’s technical achievement. As a tool though, I found the code generation
32+
somewhat distracting (expected), but it was great at generating docstrings on
33+
all my public ~structs~ and ~functions~, an unexpected surprise.
3634

3735
** Round 3: What I Did
3836

‎content/post/2024/08/22/zigging-out.org‎

Lines changed: 18 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -8,27 +8,25 @@
88

99
*** Rust Background
1010

11-
As a Rust developer, I've had it. I've designed my last type system,
12-
hacked around my last borrow/ownership issue and will claim back some
13-
CPU cycles. Hyperbole aside, I've been developing with Rust since
14-
early 2016 and have mostly enjoyed it. The type system and ownership
15-
model has been good for my development as a programmer. It has made me
16-
aware of many common memory issues and race conditions. Prior to this,
17-
I was used to debugging segfaults and invalidated objects in C++ and
18-
sometimes Go. In the beginning, Rust lacked lots of library and had an
19-
ecosystem that was easily eclipsed by the more mature
20-
languages. However, at this point, I consider it to have one of the
21-
most polished ecosystem in certain niches. Some of my favorite
22-
libraries include:
11+
As a Rust developer, I've had it. I've designed my last type system, hacked
12+
around my last borrow/ownership issue and will claim back some CPU
13+
cycles. Hyperbole aside, I've been developing with Rust since early 2016 and
14+
have mostly enjoyed it. The type system and ownership model has been good for my
15+
development as a programmer. It has made me aware of many common memory issues
16+
and race conditions. Prior to this, I was used to debugging segfaults and
17+
invalidated objects in C++ and sometimes Go. In the beginning, Rust lacked
18+
library support and had an ecosystem that was easily eclipsed by the more mature
19+
languages. However, at this point, I consider it to have one of the most
20+
polished ecosystem in certain niches. Some of my favorite libraries include:
2321

2422
- [[https://ratatui.rs/][https://ratatui.rs/]] - TUI library.
2523
- [[https://rapier.rs/][https://rapier.rs/]] - Physics engine.
2624
- [[https://tree-sitter.github.io/tree-sitter/#language-bindings][https://tree-sitter.github.io/tree-sitter/#language-bindings]] - Parsing
2725
library built in C, but has a great Rust API.
2826

2927
Despite how good Rust is, I'm reaching for a new low level programming
30-
language. The main reason for this is to try something new, but there
31-
are some things about Rust I'm happy to take a break from like:
28+
language. The main reason for this is to try something new, but there are some
29+
things about Rust I'm happy to take a break from like:
3230

3331
- Large refactors. Rust's rigid type system (where lifetime is part of
3432
the type) often necessitates more rewrites than other programming
@@ -39,11 +37,10 @@ are some things about Rust I'm happy to take a break from like:
3937

4038
*** Why Zig
4139

42-
This is arbitrary. I've heard of Zig. I've listened to some random
43-
talks. The creator, Andrew Kelley seems like an enthusiastic guy. I
44-
was able to ~sudo dnf install zig~ and things worked without much
45-
friction. This is a great recipe to get started. For some real
46-
reasons, here are some things I like about Zig:
40+
This is arbitrary. I've heard of Zig. I've listened to some random talks. The
41+
creator, Andrew Kelley seems like an enthusiastic guy. I was able to ~sudo dnf
42+
install zig~ and things worked without much friction. This is a great recipe to
43+
get started. For some real reasons, here are some things I like about Zig:
4744

4845
- Good C interop story. If there's something that I don't want to
4946
write, I can probably reach for a C library.
@@ -71,14 +68,14 @@ compiling. The following still compiles!
7168
const Struct = struct {
7269
x: i64 = 0,
7370
pub fn badFunction(self: *Struct) void {
74-
return self.y;
71+
return self.y; // self does not have `y`.
7572
}
7673
};
7774

7875
pub fn main() void {
7976
const s = Struct{};
8077
if (false) {
81-
s.functionThatDoesNotExist();
78+
s.functionThatDoesNotExist(); // Function is not defined
8279
}
8380
}
8481
#+END_SRC

‎content/post/2024/12/18/new-years-resolution-evaluation-reading.org‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
#+title: New Years Resolution Evaluation - Reading
1+
#+title: New Year's Resolution Evaluation - Reading
22
#+author: Will Medrano
33
#+date: 2024-12-18
44

@@ -106,7 +106,8 @@ stolen way too much attention.
106106
So how did I do? I did pretty well in the past 2 months. Although I should've
107107
put more effort at the start of the year, I did read a lot and it was
108108
enjoyable. Next year I will focus on my Piano skills, but will probably continue
109-
to read[fn:post-blog-readings] and combat the urge to burn time on form content.
109+
to read[fn:post-blog-readings] and combat the urge to burn time on shortform
110+
content.
110111

111112
[fn:favorite-documentation] Some of my favorite documentation includes [[https://www.gnu.org/software/guile/manual/html_node/][The Guile Reference
112113
Manual]] and [[https://wiki.libsdl.org/SDL3/FrontPage][SDL Wiki]].

‎content/post/2025/11/15/lisp-1.org‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -291,7 +291,7 @@ When parsing the next token, the options are:
291291
that our interpreter will use to bind variables and function names.
292292
3. When a closing parenthesis is encountered, then its an ~ReadItem::EndExpr~. In a
293293
normal context this is syntax error.
294-
4. An opening parenthesis is encounterd, then we recursively call
294+
4. An opening parenthesis is encountered, then we recursively call
295295
~read_next_impl~ until a ~ReadItem::EndExpr~ is encountered.
296296

297297
#+BEGIN_SRC rust

‎content/post/2026/01/25/lisp-2.org‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ x ;; 12
7676

7777
* Data structures
7878

79-
We defined a basic datastructure in [[file:../../../2025/11/15/lisp-1.org][Lisp 1]]. Before continuing, they need a
79+
We defined a basic data structure in [[file:../../../2025/11/15/lisp-1.org][Lisp 1]]. Before continuing, they need a
8080
little more refinement. We want to support:
8181

8282
1. Functions - To be defined in native Rust at the moment.

‎content/post/2026/02/21/lisp-3.org‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ through a call to ~eval~. Within a lambda call, the arguments are part of the
8787
environment. However, so is the parent global environment. In the case of nested
8888
lambda, a lambda's lambda parent can also be in scope.
8989

90-
To do this, we will create a new ~Environment~ to store are arguments and local
90+
To do this, we will create a new ~Environment~ to store our arguments and local
9191
variables. However, the ~Environment~ can also fallback to a parent
9292
~Environment~ to retrieve variables.
9393

‎content/post/2026/03/31/function-ptrs.org‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -636,7 +636,7 @@ branch with many possible targets.
636636
Despite being a bit slower, it was actually easier to add specialized
637637
instructions when using functions. ~jump_if_local0_lt2_fn~ was easy to patch in
638638
without increasing complexity too much. To implement ~jump_if_local0_lt2_fn~ we
639-
had to implement the Rust function and the compiler optimziation pass. The pass
639+
had to implement the Rust function and the compiler optimization pass. The pass
640640
that introduces the function is rather simple:
641641

642642
#+BEGIN_SRC rust

0 commit comments

Comments
 (0)