←back to thread

The Grug Brained Developer (2022)

(grugbrain.dev)
1087 points smartmic | 1 comments | 17 Jun 25 20:24 UTC | HN request time: 0.211s | source
Show context
magarnicle ◴[17 Jun 25 23:01 UTC] No.44304941[source]▶
I know, I get it, but I've realised that I'm not actually grug-brained. The way my brain works, I remember things pretty well; I like to get into the details of systems. So if more complexity in the code means the app can do more or a task is automated away I'll make the change and know I'll be able to remember how it works in the future.

This doesn't mean OP is bad advice, just make a conscious decision about what to do with complexity and understand the implications.

replies(3): >>44305082 #>>44306076 #>>44310039 #
pixelatedindex ◴[17 Jun 25 23:29 UTC] No.44305082[source]▶
The knowing how it works in the future should really just be comments, right? And if it’s a bit more complex, perhaps a markdown file in a docs folder or stuffed in a README? When working with a large enough organization, tribal knowledge is an invisible t-rex
replies(1): >>44305655 #
1. magarnicle ◴[18 Jun 25 01:01 UTC] No.44305655[source]▶
I don't think comments can capture the complexity of everything - there's too much interaction between systems to explain it all. I'm probably unique here in that my tribe is just one person: I wouldn't recommend adopting a pet t-rex in a team.