A place for developers to talk about building on Farcaster.

/dev

"The call order is the dependency graph."

If you are not managing your dependency graph explicitly, then you are likely breaking all rules of software engineering. And if everything goes, you might as well just write Javascript.

"The call order is the dependency graph."

If you are not managing your dependency graph explicitly, then you are likely breaking all rules of software engineering. And if everything goes, you might as well just write Javascript.

https://rednafi.com/go/di_frameworks_bleh

This is the alt account of Sister Hazel. Writings at https://powerlaw.systems. Curating https://protocol-particles.github.io.

I would add to your pattern that all of those possible side effects must be covered at program start. If you access global state in a local context at runtime, it's probably wrong.

I actually learned this the hard way back in my Angular JS days when dependency management was really garbage, especially in testing phases in browser contexts.

My go-to pattern is modularize everything unless I'm scripting is to explicitly make sure dependency, instantiation, and side-effects are each completely their own functions.