As a developer working at the intersection of cloud and "fullstack" - doing software often feels like an endless chain of stack overflow queries.
While this works, it also makes it hard to figure out how to "master" something when the ground feels like its constantly changing.
The compromise I've come up with is to focus on understanding the underlying concepts (things that don't change, eg. language paradigms, networking fundamentals, etc) and then develop an index to be able to quickly externalize and reference the specific implementation details (things that change, eg. js frontend frameworks).
The post here is the distillation of this in action (I'm the author). curious how other folks manage knowledge in this space and whether this resonates.
The compromise I've come up with is to focus on understanding the underlying concepts (things that don't change, eg. language paradigms, networking fundamentals, etc) and then develop an index to be able to quickly externalize and reference the specific implementation details (things that change, eg. js frontend frameworks).
The post here is the distillation of this in action (I'm the author). curious how other folks manage knowledge in this space and whether this resonates.