Skip to content

Commit df4610c

Browse files
committed
Update threads
1 parent 994c7f6 commit df4610c

1 file changed

Lines changed: 71 additions & 0 deletions

File tree

pages/threads.md

Lines changed: 71 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,8 +9,79 @@ math: true
99

1010
Conversations, thoughts, half-ideas, things I am starting to explore.
1111

12+
## 04.05.2026
13+
14+
been thinking a lot about AI and software engineering.
15+
16+
not sure what software engineering even is anymore. \
17+
work has felt... empty lately ; \
18+
mostly prompting agents. describing what should exist instead of building it. it works. things get done. but it doesn't feel like *doing*.
19+
20+
had a discussion at work where we compared it to brewing beer.
21+
22+
you can buy beer. or you can brew it yourself. \
23+
the process is the point.
24+
25+
but with code it's different.
26+
27+
you don't just buy it. you don't even have to make it. \
28+
you can just… ask for it.
29+
30+
you can't prompt a beer into existence. \
31+
you still have to go through the process.
32+
33+
with code, the process is optional.
34+
35+
---
36+
37+
if i can describe a system and have it built, what part of it is mine? \
38+
if i don't write the code, do i still understand it?
39+
40+
and if i *do* write it, am i just choosing the slower path on purpose?
41+
42+
do i even need to understand it at all, if an AI can take the entire project, code, docs, discussions, git history, and pinpoint what matters?
43+
1244
---
1345

46+
AI can read everything. suggest fixes. propose optimizations. \
47+
so what is left for me to do?
48+
49+
is it enough to say "make it faster"? \
50+
but what does "faster" even mean?
51+
52+
---
53+
54+
I tried reducing engineering into a loop: \
55+
something feels slow → measure → fix → measure again
56+
57+
measure what? \
58+
fix based on which assumption? \
59+
what if the assumption is wrong?
60+
61+
---
62+
63+
AI gives answers. often good ones.
64+
65+
but what is an answer worth if it hasn't been tested?
66+
67+
if correctness only appears after something is run and observed, \
68+
is engineering just the act of confronting reality?
69+
70+
---
71+
72+
i still like writing code.
73+
74+
not sure why _exactly_.
75+
76+
maybe because it feels like real work? \
77+
maybe because it forces me to understand things? \
78+
maybe because i have more control over the process? \
79+
maybe because it is the actual act of creation, not just the idea of it? \
80+
maybe because it allows me to prove to myself that i understand something, not just claim it?
81+
maybe because it feels like a craft, something that requires skill and practice to get better at? But so does prompting, no? Why does it feel so different?
82+
83+
**if i remove that, what is left?**
84+
1485
## 23.04.2026
1586

1687
setting up nctl for local dev today and misread "goreleaser" as "gore leaser". couldn't unsee it after.

0 commit comments

Comments
 (0)