3 ms·
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
by magarnicle 1y ago
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.
- pixelatedindex 1y agoThe 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
- magarnicle 1y agoI 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.
- anonymars 1y agoWhat about the rest of your team?
- magarnicle 1y agoI am the rest of my team. So yeah, not applicable to most people.
- d4v3 1y agobig brain dev say, "me add complexity. no problem." grug whisper: “problem come later.” grug see lone dev make clever code. grug light torch for future archaeologist.