|
|
|
|
|
|
by s-video
1257 days ago
|
|
|
I think you if you have a particular goal with using the computer it gets easier to avoid hoarding. I'm trying to get better at writing code that's easy to read and change, which is admittedly too vague but it can still help me be real with myself and close tabs that don't have anything to do with it. For example, here's two tabs I opened recently: A Neat XOR Trick: https://www.mattkeeter.com/blog/2022-12-10-xor/ Code Only Says What it Does: https://brooker.co.za/blog/2020/06/23/code So that first one is about solving an advent of code problem cleverly. That second one makes some nice points about how code doesn't necessarily capture your intent or the reasons you wrote what you did. So if I had both of those open in my browser or in some queue for unread links, and I wanted to cut down, I'd delete the first one. I also find it helpful to ask if a link has any information that isn't already covered by some other resource in more depth. So if my goal was to learn more about compilers I might be tempted to save the blog post OP links to about writing a brainfuck compiler in Go with LLVM but there's already resources like Crafting Interpreters out there, so I'd probably only give that blog post a skim and not bother saving the link. (But if it was my goal to specifically write a brainfuck compiler, or write a compiler in Go, or write a compiler that uses LLVM, or some combination, I'd be more likely to save that particular post.) |
|
|
Ah but it's not just about that, it's also about figuring out what problems can be fit into bit twiddling, knowledge about bitwise operation (especially that xor is self-reversing so it handles set/unset as well as pairs), and the ability to reduce effective complexity.
I agree it's not useful if you're currently on a quest
> to get better at writing code that's easy to read and change
but thinking of it as "solving an advent of code problem cleverly" misses most of the information.