1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
|
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="description" content="Home for a73x" />
<meta name="author" content="a73x" />
<meta name="viewport"
content="user-scalable=no, initial-scale=1.0, maximum-scale=1.0, minimum-scale=1.0, width=device-width" />
<title>a73x</title>
<link rel="stylesheet" href="/static/styles.css">
<link rel="stylesheet" href="/static/syntax.css">
<link rel="icon" type="image/x-icon" href="/static/favicon.svg">
</head>
<body>
<main>
<div class="header">
<div class="header-title">
<h1>a73x</h1>
<sub>high effort, low reward</sub>
</div>
<nav class="nav">
<ul>
<li><a class="no-decorations" href="/">home</a></li>
<li><a class="no-decorations" href="/posts">posts</a></li>
<li><a class="no-decorations" href="/ethos">ethos</a></li>
</ul>
</nav>
</div>
<h1>home</h1>
<h2 id="about-me">about me</h2>
<p>I’m a backend software engineer. I primarily work in Kubernetes, writing microservices in Go.</p>
<h2 id="tidbits">tidbits</h2>
<p>Arbitrary bits of information I found useful</p>
<h3 id="go">go</h3>
<ul>
<li>layout packages by what they do, not by their abstract type</li>
<li>use channels sparingly: write synchronous methods and allow the caller to make it async</li>
<li><code>append</code> modifies the underlying slice, you’ll only make this mistake once</li>
<li>define interfaces where you use them</li>
<li><code>make([]int, 5)</code> has a length and capacity of 5. <code>([]int, 0,5)</code> has a length of 0 and capacity of 5.<br>
<code>append()</code> will only do what you want with the latter</li>
<li>don’t use <code>init()</code></li>
<li>TFBO (test, fix, benchmark, optimise)</li>
<li>more CPU != more performance<br>
more CPU == more contention</li>
</ul>
<h3 id="git">git</h3>
<ul>
<li><code>git reflog</code> will save you when you mess up</li>
<li>Keep your git history clean
<ul>
<li><code>git commit --fixup=<COMMITISH></code></li>
<li><code>git rebase origin/main --autosquash</code></li>
</ul></li>
</ul>
<h2 id="reading">Reading</h2>
<ul>
<li><p><a href="https://cs.opensource.google/go/go/+/refs/tags/go1.23.0:src/runtime/proc.go"><code>proc.go</code></a> - Go documentation is great, this describes the scheduler</p></li>
<li><p><a href="https://github.com/golang/go/issues/67120">proposal: runtime/metrics: define a recommended set of metrics</a></p></li>
<li><p><a href="https://calteches.library.caltech.edu/51/2/CargoCult.htm">Cargo Cult Science - Richard Feynman</a></p></li>
<li><p><a href="https://www.cs.virginia.edu/~robins/YouAndYourResearch.pdf">You and Your Research - Richard Hamming</a></p></li>
<li><p><a href="https://www.oreilly.com/library/view/designing-data-intensive-applications/9781491903063">Designing Data Intensive Applications - Martin Kleppmann</a></p></li>
<li><p><a href="https://www.oreilly.com/library/view/database-internals/9781492040330">Database Internals - Alex Petrov</a></p></li>
<li><p><a href="https://www.oreilly.com/library/view/efficient-go/9781098105709">Efficient Go - Bartlomeij Plotka</a></p></li>
<li><p><a href="https://press.stripe.com/the-art-of-doing-science-and-engineering">The Art of Doing Science and Engineering - Richard Hamming</a></p></li>
<li><p><a href="https://www.oreilly.com/library/view/the-art-of/9781492080688/">The Art of Agile Development - James Shore, Shane Warden</a></p></li>
</ul>
<footer>
<br />
<hr />
<br />
<p>see something you disagree with? email: <a href="mailto:[email protected]">[email protected]</a></p>
</footer>
</main>
</body>
</html>
|
