this is a an important article. It's a bit hard to grok and requires some experience to understand but after you end up with a messy system doing too much ghosty stuff you yearn for stability
Agreed. This is one of the few articles that I’ve read this month that is really caused me to reflect on my own systems.
The insight that
open(“foo.txt”)
is, from the perspective of component analysis, actually secretly
open(filesystem, access_level, “foo.txt”)
is worth its weight in gold. I feel like I understand more about system design, capability-based permissions, and my own code.
Realistically it won’t immediately change the way I program and I won’t be running to the terminal to refactor my current codebase, but it’s like I’ve been clued in to a whole new class of code smells.
The insight that
is, from the perspective of component analysis, actually secretly is worth its weight in gold. I feel like I understand more about system design, capability-based permissions, and my own code.Realistically it won’t immediately change the way I program and I won’t be running to the terminal to refactor my current codebase, but it’s like I’ve been clued in to a whole new class of code smells.